SSYYSSTTEEMMSS EENNGGIINNEEEERRIINNGG DDEESSIIGGNN PPRROOJJEECCTT EENNPPMM 664433,, FFaallll 22000066 Instructor Authors ENPM643 Dr. M Austin Atul Mehta & Felipe Leite Fall 2006ENPM 643 – Fall ’06 Parking Lot Occupancy Tracking System 2 TABLE OF CONTENTS Section Page 1 OVERVIEW OF THE PROJECT....................................................................................... 3 1.1 PURPOSE........................................................................................................................... 3 1.2 ROLES AND RESPONSIBILITIES.......................................................................................... 3 1.3 INTRODUCTION.................................................................................................................. 3 1.4 DEFINITIONS...................................................................................................................... 4 1.5 ASSUMPTIONS AND LIMITATIONS...................................................................................... 4 1.6 REFERENCE MATERIAL..................................................................................................... 4 2 UML MODELS...................................................................................................................... 5 2.1 DEPLOYMENT DIAGRAM................................................................................................... 5 2.2 USE CASE SUMMARY........................................................................................................ 6 2.3 CAR ARRIVING.................................................................................................................. 7 2.4 CAR LEAVING................................................................................................................. 10 2.5 DISPLAY PARKING SPACE AVAILABILITY........................................................................ 12 2.6 SYSTEM PRIVILEGES/UTILITIES....................................................................................... 13 2.7 UPDATE/NEW USER DATABASE....................................................................................... 15 2.8 GENERATE REPORT......................................................................................................... 17 3 REQUIREMENTS/ GOALS & SCENARIOS.................................................................. 19 4 DESIGN ANALYSIS & VALIDATION ........................................................................... 25 5 CONCLUSION .................................................................................................................... 29ENPM 643 – Fall ’06 Parking Lot Occupancy Tracking System 3 1 OVERVIEW OF THE PROJECT 1.1 Purpose The goal of this project was to take a parking lot control system from requirement generation, through model generation and validation. This document describes the process taken a presents the resulting data. 1.2 Roles and Responsibilities The project team is formed by the following students: Atul Mehta and Felipe Leite. Since all team members have the same experience and expertise designing systems, the work was divided equally and assigned arbitrarily. 1.3 Introduction For our project, we have decided to design a system that can be deployed in existing parking structures which would provide information about available parking spaces to drivers trying to access the facility. The system will include software, sensors and the networking components. The installation of permanent sensors in each parking space will provide lot owners with constant and accurate information on parking lot occupancy. This allows them to keep the lot at full capacity and serve customers better. Figure 1 shows the building parking lot that we will be designing for. It has 72 parking spaces where 8 are handicap, 4 are for the building staff and the remaining 60 are available for regular lot users. In addition, a list of members provided to the system by the building owner will be used to grant or not access to the facility. Figure 1 - Parking Lot LayoutENPM 643 – Fall ’06 Parking Lot Occupancy Tracking System 4 The system will make use of electronic signs to give drivers, information regarding parking availability before they enter the facility. Once inside, color coded LED displays will lead motorists to the vacant spaces. Parking spaces can be made unavailable by the building manager bypassing the sensors. This and other configuration options will be made available through a GUI interface. 1.4 Definitions 1.4.1 Parking Lot The parking lot consists of one entrance and 1 exit. There are 72 parking spaces with 8 being handicap and 4 being reserved for building staff. 1.4.2 Entrance The entrance consists of a gate, a display showing the precise number of available parking spaces, a tag reader. The tag reader is activated as soon as the car is within range. 1.4.3 Exit The exit consists of a gate and an induction loop that is behind the gate to detect when a car approaches the gate. 1.5 Assumptions and Limitations  Every parking space can be reached from any entrance.  Every exit can be reached from each parking space.  No entrances are convertible to exits and vice versa.  Building manager assigns a unique tag to each authorized car.  Tag number and vehicle information is stored in a database maintained by the building manager.  Emergency situations (e.g. fire) will not be considered here. 1.6 Reference Material [1] J Magee and J Kramer, “Concurrency State Models and JAVA Programming,” John Wiley & Sons Ltd., 2nd Edition, 2006ENPM 643 – Fall ’06 Parking Lot Occupancy Tracking System 5 2 UML MODELS 2.1 Deployment Diagram The Parking Lot Occupancy Tracking system can be divided into sub-components as seen in the deployment diagram shown above. The Parking Lot Occupancy Tracking system consists of a parking gate interface, manager interface, parking lot controller system interface, parking sensor system interface, display interface and network interface. Parking Gate Interface This subsystem is triggered as soon as a commuter/car arrives near the parking