Embedded Files
Deployment Diagram
The deployment diagram shows where each part of the system resides while there is only one central sever, there can be many sets of garage equipment (one for each garage in the system) the current number of garages planned for is eight. However there can be as many employee devices or customer devices in the system as needed.
Implementation Model and Packages
Implementation Packages Diagram shows how the original class diagram has been repackaged into smaller parts for deployment and where those parts reside on the implementation for more details on each package view below.
Garage Computer Software
Garage Computer Software does not include sensor interface, this happens internally on the PC and sends signals to the software classes directly, it is not shown on this model explicitly because it occurs inside of the local controller class
Web servers and Website Classes
The image on the left shows the class implementation for the guest webpage consisting of map (default) and detailed views.
The image on the right shows the class implementation for the web server (can receive any of the different types of packets and pass them out again unmodified to the correct recipients.
Class diagram for the employee webpage: This has pages for map (home), login (default), account tab, scheduler of events, detailed view, and parking garage metrics.
Processing Server Rack
Processing Server Rack, this is most likely located in the same server room as the web server, with direct hardwired connections. This part of the software is designed to handle the interface in-between the web server which contains outside accesses as well as the responsive webpages, the controllers (internal and garage equipment) and the internal model and logs.
Google Sites
Report abuse