(back)
(Home)
(next)
>>>>>>>>>>>>>>>>>. |
|
|
| >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> |
Table of Contents
>>>>>>>>>>>>>>>>>>>>>>
|
Problem Specification |
|
The maintenance company has faced problems in maintaining records of vehicles parked in its country club carpark. As there are frequent complaints that members could not find empty slots during weekends, the company had performed a survey and found that many slots were occupied by non-member’s car during weekend. It has greatly affected the member’s confidence on the company as well as it pose a threat to the security of the club. Therefore, a intelligent vehicle parking system to overcome the present inefficient and time consuming process is needed.
|
|
a) Low security Unauthorized access into the car park pose a threat to member as well as the country club’s security and reputation. b) Poor management of records Records of vehicles parking in the car park is unorganized and required lot of work to compile them manually. Furthermore, searching for particular record is difficult. c) Inefficiency Members were not able to know the status of the car park and might waste time roaming around looking for empty slots.
|
|
The system is divided into 2 main subsystem namely the carpark security system and carpark management system. Prior to entry into the carpark, a list of available empty slots at each level is displayed and it also display the total number of available slots. The carpark security system will then verifies the user's identity by getting the data from a swap card reader when the user swapped his ID card through. The members can then proceed to their desired carpark slot. Therefore, if there is no empty slot, the system will output a message to inform the user. On the whole, the system prevents non-member from using the carpark thus creating more empty slots for the members. The carpark management system allows the viewing of daily parking records conveniently as well as generating reports upon request. It can track down past records of any suspect’s car parked in the carpark if investigation will to be done by the police. In addition, updating of registered member's personal data and the system user’s details is also provided. But only authorized system user like the manager or supervisor or system administrator can change the user access status. However, the changing of password can be done by any system user individually (for himself only). Authorized system user like the supervisor can also access the utilities option to do some system housekeeping like purging of old records and resetting void card numbers that is produced due to the losses of the card. The rest of the functions are accessible by the normal system user.
|
|
a)
Software Used
-
Visual Basic 6.0, Rational Rose (UML), Microsoft Access 7.0
|
|
a) Assumption
-
Every member own only 1 car (Enhancement can done in later stages)
-
Keyboard entry will simulate the sensing of the car entry, exit as well
as its car park slots.
-
Random allocation of a car park slot is done to simulate the member
selection of his slots at a certain level.
-
The system can be accessed online.
- The
carpark is purely for the use of registered member only but in the
case of their guests coming in, they have to parked in another carpark
where advanced reservation of a slot is also available.
b) Limitation
-
System handles 1 member at a time at the entry and exit point. The next
car to enter has to wait till the earlier car finds a carpark slot to
park before its entry is granted.
c) Constraint
-
Cannot restrict intruder who enter the carpark forcefully.
d) Preferences
-
Security cameras installed at the entry/exit point to look out for any
trespassing of intruder.
-
Any loss of ID card should be reported immediately to the club so that
a new card can be issued and the old one will be disable.
|
|
Deployment diagram The diagram illustrates the main objects, represented by the block, and the links between them. The user's ID card have to swap through the card reader before entry into the carpark is granted (registered member) as well as during the exit process. Concurrently, information of the member will be process by the system. The maintenance company also access the records and details using the system. The users can feedback to the maintenance company through emails and vice versa regarding any important matters e.g. loss of ID card. So that necessary actions can be taken. ( Please refer to the deployment view under the Architecture design ) Back to Top
|
|
The diagram briefly summaries the inputs, the tasks to focus on and the desired outputs e.g. staff database from the parking system during the development. The specifications will be refined regularly based on feedbacks obtained from the users. Back to Top
|
|
