The purpose of this project is to utilize the UML process to design and analyze a multi-phase project in which we will implement real-time space occupancy sensors for accessible parking spaces, these sensors will be responsible for collecting real-time availability data on accessible parking spaces. Additionally, general garage availability will be measured by utilization of Entry/ exit sensors. The system will ultimately be able to display availability information on LED display boards and also display informational messages such as event parking or parking availability statuses. This information will also be made available to the general public by means of a web based application. In order to manage the operation of the system employees will have a web based portal that can be accessed to manage system information and ultimately make financial decisions with the information provided.

Below are the functional and technical requirements for the system, additionally, the proceeding pages of this website will cover in detail the necessary components of the UML process to accurately illustrate the design, implementation and deployment of the SmartPark UA system.

Employee & User GUI Tabs

In the tabs above you will notice the Employee and User GUI links. These links will direct you to pages that show the Various GUI interfaces that make up the boundary views of our SmartPark UA system. They provide in depth details on What GUI's are available how they appear on system boundary views and how they interact with different components of the system.

Class & Activity Diagram Tabs

In addition to the Employee and user tabs, you will be able to access class and activity diagrams that comprise the system. The Class diagram was constantly changing throughout the life cycle of the design process, it served as a guide to illuminate class interactions and provided clarity as to how our definition of the system determined what our system could and could not do. The activity diagrams are graphical representations of how different components of the system interact and execute specific use cases. The activity diagrams help to visualize how the various functions of our system work. The state diagrams are also included in this section as they indicate the various changing states of our components as the system executes the various functionalities.

Deployment & Implementation Tab

The deployment diagram is shown under this tab and provides a graphical representation of the organizational architecture or our system components. The implementation model is a graphical representation of the organizational architecture of the different software components of the system. You will also see detailed class diagrams embedded within this model.

Use Case Specifications Tab

We utilized use case specifications as a means to begin the design phase of the overall system. We tailored our Specifications around the system requirements and built the first iterations around these specifications. As the project evolved, relied less on use case specifications and utilized model view controller diagrams more frequently. This enabled us to more accurately design and model the system. There is also a link for use case realizations which graphically show the use case specifications that we have outlined on this website.

Project Source Document Tab

The tab contains an embedded PDF file of the original Project outline