Management of Car Parks - Assignment Example

Object Oriented Systems Analysis and Design Name: Number: Course: Tutor: Date: Possible use cases Issuing tickets Ordinary customers press a button on the control pillar, and a ticket is printed and issued. The ticket must be printed within five seconds. A ‘Take Ticket’ display is flashed on the control pillar. If the car park is full, no ticket is issued, and a ‘Full’ display is flashed on the control pillar. Handling payments and controlling barriers When a car approaches an entry barrier, its presence is detected by a sensor under the road surface, and a ‘Press Button’ display is flashed on the control pillar Management of car parks The system handles all aspects of the car park management that are not part of the daily operational system. Recording problems Details of all problems are recorded by the system and a statistical monthly report of all problems is produced. Issuing season tickets and monitoring SLA with the security company After the ordinary customer is ready to leave, he or she must go to a pay station to pay. The ticket is inserted into a slot, and the bar code is read. Also all security guards arriving in the car park, put cards into the reader and the date and time of arrival is recorded it is also repeated during departure. System wide Non functional requirement document Usability The system will undergo two stages of testing, first the clients and the board management will be required to test the system to ensure that it met its intended purpose. The system will then be subjected to programmers to identify errors within the code and system functionality. Speed of use The system simple coding and powerful machines to enable users speed up their tasks. Again while coding all the complex will be done on the database side while only simple task will be left to the interfaces. Learnability and Training material The system will first adopt mechanism used by pre-existing software systems and only take what most users are used to finding in systems this will fasten the process of learning and adapting to such a system. The programming team will also provide a detailed outlined of the various system components and training manuals to fast track the learning process. Documentation The system will provide two types of documentation the first will be a simple summary of all the system parts and components which will be important for those who wish to quickly have a grasp of the system. The second documentation will be much complex and detailed this will be the major point of reference for all those who experience problems when using the system it will also be important in training new system clients. The system shall also provide an online help facility for quick referencing. Reliability Several steps will be taken to ensure that the system is reliably first is that the system will be optimized to a maximum failure rate of twice per month and a maximum down time of one hour. The system shall have a database with automatic back ups after specific intervals this will ensure that the system shall be easy to restore in case of failures. Security Several security mechanisms will be undertaken by the system for security the first step being adopting several user categories each with specific privileges. The other mechanism would be an anti virus software with regular updates installed on the server not forgetting the implementation of a powerful firewall within the network to the system. Supportability The system shall provide support basically for two operating systems namely windows and Linux which are the operating systems commonly used. The system will also be easy to configure within both the two operating systems Question two Issuing season tickets and monitoring SLA with the security company Summary After the ordinary customer is ready to leave, he or she must go to a pay station to pay. And all security guards entering and leaving must cloak in and out Course of events The season ticket holder goes to the exit and inserts their season tickets into a slot on the exit barrier control pillar. The barrier is raised and a record is made of the time at which the season ticket holder left.. Security guards arriving in the park put their cards into the card reader and the date and time of arrival is recorded. Security guards leaving also put their cards in again and their departure time is recorded. Each security company is issued with a specific number of cards, depending on the number of car parks they are responsible for. Each security company is responsible for specific car parks Handling payments and controlling barriers Course of events The customer goes to a pay station to pay. The ticket is inserted into a slot, and the bar code is read. The ticket bar code information is compared with the stored information. If the dates or times are not the same, the ticket is ejected, and the customer is told via an LCD display to go to the office. At the pay station, if the ticket dates and times are the same as the bar code dates and times, then the current date and time are obtained, and the duration of the stay in the car park is calculated. The car park charge is calculated and displayed on the LCD display If no change is available, this information is displayed on the LCD display The customer then inserts notes or coins to at least boost the amount of the charge. Each note or coin is identified as it is inserted and the value added to an accumulated amount and displayed on the LCD display. Invalid coins are dropped through into the return tray and a message displayed on the LCD display. As soon as the amount accumulated exceeds the charge, the ticket is validated and the current date and time are added to the stored data for that ticket. The system displays a message telling the customer to press the ‘Receipt’ button if they need a receipt. If they press this button, a receipt is printed and ejected into the receipt tray. The system displays a message for the customer telling them to take the ticket back to their car and leave the car park within 15 minutes. The customer drives up to the exit barrier, the car is detected by a sensor, and an ‘Insert Ticket’ display is flashed on the control pillar. The customer then inserts the ticket where the bar code is read and a check is made that no more than 15 minutes have elapsed since the payment time for that ticket. If more than 15 minutes have elapsed, an intercom in the control pillar is activated and connected to the attendant in the car park office. If no more than 15 minutes have elapsed, the barrier is raised. A sensor on the other side of the barrier detects when the car has passed and the barrier is lowered. The number of vehicles in the car park is decremented by 1 and a check is made against the capacity of the car park. If the car park was full, then the display near the entrance is switched to say ‘Spaces’, and a check is made to see if any vehicles are waiting. If they are, then the control pillar for the first waiting vehicle is notified. If the driver of the vehicle waiting there does not press the button, then the control pillar for the next waiting vehicle is notified. Issuing season tickets and monitoring SLA with the security company Handling payments and controlling barriers Question four Issuing season tickets and monitoring SLA with the security company Issuing season tickets and monitoring SLA with the security company Question seven References Read More