Use Cases

Use Case: DetailSkyViewAndSkyviewGuest

• ID: 002
• Brief Description: Mobile and web application displays detailed information about the status of a specific garage or status of general status
• Primary Actor: Guest
• Secondary Actors: None
• Precondition: Guest Must have web browser and internet connection
• Main Flow:
  1. Use case begins when the employee selects “Details”
  2. The application sends a request to the Smart Park web servers for current availability information about garages.
  3. The smart park server then accesses the Garage Controller
  4. The Garage Controller accesses the garage class, which then fetches all status information.
  5. This data is then returned to the Smart Park web server
  6. The server then sends the information back to the user device which is then displayed on the Garage Map GUI or Detailed
  7. The use case ends when the GUI displays details in the "Detail" tab displaying garage details
• Post Condition: Detail GUI apperars on the Employee device
• Alternative Flow: Employee may select refresh the home screen which retrieves data in the same manor, but shows a map with with a simplified table of data
• Post Alternative: updated Home GUI Appears on user device

Use Case: SchedulerAddEvent

• ID: 004
• Brief Description: Employee enters scheduled parking information
• Primary Actor: Employee
• Secondary Actors: None
• Precondition: Employee is logged in to the Home screen of the Application
• Main Flow:
  1. The Use case begins when the user selects “Scheduler” from the Interface GUI
  2. The application displays the Scheduler GUI which displays current schedule as well as Add Event button
  3. The user selects Add Event and the Scheduler GUI displays the add event form and prompts the User to enter scheduling information such as, type of event, date, time range, price, garage status
  4. The employee clicks submit.
  5. Once the event has been submitted the Scheduler GUI sends the information to the Smart Park server.
  6. The Server then passes the information to the event controller which then creates an object of type event and passes that event to the garage class
  7. Lastly the garage class sends the updated event information to be logged.
  8. The use case ends when a confirmation is displayed to the employee
• PostCondition: Confirmation is displayed and information is logged into the system
• Alternative Flow: The user may select and event to bring up details as well as the edit and remove options

Use Case: AccessibleParkingSensor

• ID: 005
• Brief Description: Sends parking vacancy information to Smart Park Servers and updates garages display
• Primary Actor: Guest
• Secondary None
• Precondition: Sensor must be properly installed at Accessible parking space
• Main Flow:
  1. The use case begins when the sensor detects a change in occupancy.
  2. The device sends the data indicating the change in status to the Local Controller.
  3. The local controller sends the data to the web server which is then processed in the garage controller
  4. the local controller updates the garage's display with appropriate information
  5. the use case ends when the local controller updates the garage's display panel.
• Post Condition: The server has real time updates on accessible parking availability, and assibilty information displayed on grages display panel
• Alternative Flow: none

Use Case: EntryExitSensor

• ID: 006
• Brief Description: Sends information to local controller of a Vehicle entering or leaving the system. and updates garage display
• Primary Actor: Guest
• Secondary Actors: None
• Precondition: Sensor must be properly installed at entry or exit point
• Main Flow:
  1. The use case begins when the sensor detects a car entering or leaving.
  2. The device sends the data indicating the passing of a vehicle.
  3. The local controller adds the total amount of vehicles that have passed the sensor. It calculates the number of cars that are in the garage at any given point
  4. The Local controller then sends a status update to Smart park Servers which is then processed in the garage controller
  5. the use case ends when the local controller updates the garage's display panel.
• Post Condition:
• The server has real time updates on parking availability and metrics
• Alternative Flow: No Response from server, send error message