Requirement Models                (back)          (Home)    (next)

In the starting stage or the elaboration stage, we need to come up with a statement of scope for the system and determine the build the object diagram. Please refer to the below tables for more details.

Statement of scope 

                 The Vehicle Parking System displays information regarding the carpark to any member prior to his or her entry. The member is able to view the carpark status from the system. The information displayed are as follow : the total empty slots available, the empty slots available on level 1, level 2 and level 3 of the carpark. In addition, every entry will be recorded and updated as parking lots information. It will contain data like date in, time in, hours and NRIC of the member when the car first entered into the carpark. Upon reaching the desired slot, information like the number and the level of the slot will be updated. Furthermore, when the member exit, the time out and date out is also updated too. 

                 In the system, system users, the employees, can also login into the system using his user id and password. After login successfully, a number of options can be selected. There is the maintenance of the member and system user records. It also has the utilities and report manager that will manage the system and print out reports

                Under the maintain member option, the user can create , update, delete, search records and replace card based on the member's name, NRIC, card no or plate number of his car. The member can have the same name but what differentiate them will be their NRIC which is unique. Therefore checking of duplicates has to be done. The member's card number will be generated upon the a new creation. Moreover, the member can also be either a registered member or an employee as the employee can also be a member of the club. They are differentiated by using a type field (for future enhancement as employees will have special benefits from a  normal member).

               In the maintenance of the system user records, function like adding of a new user, modifying and deleting of the records are also available. But certain function is only accessible by user of high status or authority like a supervisor. The user id is created automatically for new user therefore duplication is impossible.

              In the utilities manager option, user can allow the reuse of void card number that was caused due to the losses by the member. The resetting of the slot availability is also available, if there is any discrepancy, to enhance data correctness. Purging of one year old records is necessary for housekeeping purposes.

              Lastly in the report manager option, users also generate different reports based on their selections like using date, date range or plate number combination to retrieve the desired data only.   

 

 Analysis of the statement - noun parsing

(1) - needed remembrance, (2) - needed services, (3) - multiple attributes

Potential List Category Confirmation
Vehicle Parking system system itself Confirmed
carpark external entity Rejected due to (1) and(2)
member role Confirmed
carpark status things to remember Confirmed
total empty slots things to remember Rejected due to (1) and(2)
level1 empty slots things to remember Rejected due to (1) and(2)
level2 empty slots things to remember Rejected due to (1) and(2)
level3 empty slots things to remember Rejected due to (1) and(2)
parking lots information things to remember Confirmed
date in  things to remember Rejected due to (1) and(2)
time in things to remember Rejected due to (1) and(2)
NRIC things to remember Rejected due to (1) and(2)
slot number things to remember Rejected due to (1) and(2)
slot level things to remember Rejected due to (1) and(2)
time out things to remember Rejected due to (1) and(2)
date out things to remember Rejected due to (1) and(2)
system user (employee) role Confirmed
user id things to remember Rejected due to (1) and(2)
password things to remember Rejected due to (1) and(2)
utilities manager structure or role Confirmed
report manager structure or role Confirmed
report structure or things to remember Rejected due to (1) and (2)
member name things to remember Rejected due to (1) and(2)
plate number things to remember Rejected due to (1) and(2)
type field things to remember Rejected due to (1) and(2)
status things to remember Rejected due to (1) and(2)
supervisor role Rejected similar  to system user
housekeeping purpose things to remember Rejected due to (1) and (2)
date range things to remember Rejected due to (1) and (2)
 

Back to Top 

 

Hosted by www.Geocities.ws

1