Report > Discussions > Deriving the requirements model

 

7.1. Deriving the requirements model

Original requirements received from client

  1. Software to find parking slot, displayed with LCD touch screen

  2. Display options of places where the vehicle could go, after selection provide the nearest vacant parking lot to the desired destination

  3. ERP auto reduction from the cash card

  4. Capture license plate number

  5. Entry and exit time logged. The amount to be charged is to be time dependant

  6. Reserve parking spaces for seasonal parking

  7. Multiple entrances -  season parkers get priority (Up to 4 entry and exits)

  8. Detection of full car park and methods of disallowing entry when the car park is full

  9. Cash card contingencies - normal method will be available to the drivers when ERP machine spoils or when the cash card is empty

  10. Check vacancies via SMS and Internet using WAP

  11. Can search from a kiosk made available for forgetful people. The system will be able to show where the car is parked after the driver enters the license plate number

  12. Different rates based on the size of the Vehicles

  13. Show the lorry parking lots for lorries

  14. Check if the vehicle is stolen with Police Database

  15. Ability to give priority to vehicles with emergency status, i.e. police, ambulance etc

 

Based on these requirements given by the client we have made the following points

  1. Car park will be divided into zones (ex: zone A for tower A etc)

  2. User choice input is destination zone (ex user input tower A, tower B etc)

  3. After input system will access database and display zone map with available parking slot in the zone

  4. The system will not restrict the user in to only 1 assigned parking slot as we found no effective method to ensure the usage of the assigned slot by user

  5. On exit, a sensor will check if cash card has sufficient value

  6. If on exit the cash card has sufficient value it will exit by the normal exit gate and the ERP will deduct the cash card

  7. If on exit the cash card has insufficient value, a sign will point to an alternative exit gate equipped with cash machine. The sign will also display amount due.

  8. When find car menu in kiosk is opted, the system will also check the amount due

  9. Database will have license plates under "seasoned parking" category

  10. Display sign "Car park full" in front if the car park is full, however the entry gantry will still operate

  11. Check via sms / wap will only return number of empty slots in a specified zone

  12. Weight sensors at the entry gantry to determine weight category and thus decide the right rate

  13. We assume the parking slots have individual sensors which will detect if the slot is occupied and the license plate number

  14. We will disregard number 15 of the requirement on the basis of during emergency those vehicle will not bother to find a parking slot and most probably will park somewhere convenient to them and also that the administrator will have the power to override the system if needed.

 

A write up of the requirements used in Object Oriented Analysis

The intelligent car parking system should allow the drivers to find a parking slot using a LCD touch screen.

 The LCD touch screen should display a list of places the users wish to go and after selecting, the system should display the nearest vacant parking lot of the desired destination.

The system should allow ERP auto reduction from the cash card. If the driver does not have enough credit in his/her cash card, the system should be able to warn the driver before they leave the car park.

At the entrance gantries of the car park, the car license plate number should be captured by the system and stored in the system database. The entry time should also be stored in the database so that when the vehicles exit from the exit gantries of the car park, the exit time of the vehicle can be recorded and the system will be able to charge the user accordingly. Charges are also based according to the weight of the vehicles. Every vehicle that enters the car park will have their car license plate number check with the local police database to verify whether the vehicle is a stolen vehicle.

The system should display to the users the reserved parking space in the car park. These parking lots are reserved for season parking users. There will be multiple entrances in the car park (up to 4 entrances and exits). The system should indicate to the users when the car park is full and should incorporate features to disallow entry to the full car park.

In the case when the user does not have enough credits in their cash card or their ERP machines are faulty, users will still be able to pay their charges by cash or NETS via kiosks located around the parking complex. Drivers who are unable to find their cars in the parking complex can locate the position of their cars by keying in their car license plate number into the paying kiosk. Sensors are used to detect the actual position of the vehicles in the parking slot.

The system should display the parking lots for lorries if a lorry wants to enter the parking lot. In the case of an emergency, priority should be given to emergency vehicles (i.e. police, ambulance….) wanting to enter the parking complex. Drivers wanting to park their cars in the car park can check the vacancies in the car park using their mobile phones via SMS or the Internet via WAP.

 

 

 From this write up, we tried to separate the potential objects/classes by identifying keywords. These keywords are usually connected to: External entities, Things/occurrences remembered, Roles played, Sites, Organizational units, and structures.

This potential list were then confirmed using considerations such as

  1. Needs remembrance

  2. Needs services

  3. Multiple attributes

  4. Connected to an external entity (if the object satisfies this point, it is automatically confirmed)

 

 

The full list of our analysis is as follows (in the form of a table)

Potential List Category Confirmed List
intelligent car parking system  System itself confirmed(System itself)
parking slot  Things to remember confirmed(criteria 1-3 apply)
LCD touch screen external entity confirmed(connected external entity)
a list of places the users wish to go  Things to remember rejected(criteria 1 and 2 apply but 3 fails)
ERP  external entity confirmed(connected external entity)
entrance gantries Things to remember confirmed(connected external entity)
cash card external entity rejected(criteria 1 and 2 fails)
license plate number  Things to remember rejected(criteria 1 and 2 apply but 3 fails)
system database Things to remember confirmed(criteria 1-3 apply)
entry time  Things to remember rejected (criteria 1 and 2 apply but 3 fails)
vehicles external entity confirmed(connected external entity)
exit gantries external entity confirmed(connected external entity)
exit time  Things to remember rejected(criteria 1 and 2 apply but 3 fails)
Charges  Things to remember rejected(criteria 1 and 2 apply but 3 fails)
weight of the vehicles Things to remember rejected(criteria 1 and 2 apply but 3 fails)
local police database external entity confirmed(connected external entity)
stolen vehicle Things to remember rejected(criteria 1 and 2 apply but 3 fails)
reserved parking space  Things to remember rejected(criteria 1 and 2 apply but 3 fails)
season parking users roles played rejected(criteria 1 and 2 fail)
features to disallow entry external entity rejected(criteria 1 and 2 fails)
full car park Things to remember rejected(criteria 1 and 2 apply but 3 fails)
NETS external entity confirmed(connected external entity)
kiosks  external entity confirmed(connected external entity)
drivers roles played rejected(criteria 1 and 2 fails)
Sensors external entity confirmed(connected external entity)
parking lots for lorries  Things to remember rejected(criteria 1 and 2 apply but 3 fails)
mobile phones external entity confirmed(connected external entity)
SMS external entity rejected(criteria 1 and 2 apply but 3 fails)
WAP external entity rejected(criteria 1 and 2 apply but 3 fails)

 

The class diagram obtained can be seen in 5. Requirements Model

 


Home | Project | Progress | Report | About Us

CopyRight @ 2003 FreshMaker Ltd. All rights reserved