to my design classes:
Recall that the green items are my «interface» classes, the red items are my «controller» classes and the purple items are my «entity» classes.
As is usual with analysis classes, they don’t necessarily represent the way the real software will be organized.
In this case, the «interface» classes are too numerous, an so I’ve merged the five analysis classes Registration, ServiceCustomer, SeeQueueLength, TakeANumberNotification, and TakeANumber into three Python modules registration.py, service.py, and customer.py.
All the «controller» analysis classes, I’ve merged into a single module. The RegistrationStatus «entity» is a little too small for a class on its own, and the Queue has its own module.
As you may recall, the architecture I chose included a web server and a database.
Missing: Web Server
Also missing is what sort of a web server I’m going to be using. Previously, I mentioned IIS or Apache. However, again Python has a simple implementation of a web server that means I won’t have to bother with either of those.
The next step is to write the code. To do this, I’m going to be using the PyCharm CE IDE from Jetbrains, because I liked the IntelliJ-like interface and I’m going to use the test-driven development approach because I like having test coverage of my code.