Case Study Scenario

Case study scenario: Car parking system Introduction: This is a case study about a public car park
that needs an automated system to run the day to day business. You, the analyst, have to continue
the work and prepare a Business Requirements Statement and a Systems Design Specification. If you
discover that the case study is not providing you with all required information, you are encouraged
to make necessary assumptions. You are expected to include suggestions that would improve the
system and justify your assumptions. The assignment must be presented in a professional manner.
All the models should be produced using the Enterprise Architect CASE tool. This system must
provide the day-to-day operation for car park—issuing tickets, handling payment and controlling
barriers. The descriptive scenario for such a car park design can be as follow. COMP.6209 System
Analysis and Design • Operational System The car park operational system controls entry to the car
park and exit from the car park and payment for car parking. Customers pay for their use of car park
after they finished using the car park. • Entry to the Car Park 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 post. The customer must press a button on the control post, and then a ticket
is printed and issued. The ticket must be printed within five seconds. A ‘Take Ticket’ display is flashed
on the control post. If the car park is full, no ticket is issued, and a ‘Full’ display is flashed on panel
above control post, therefore cars will not entre. When the customer pulls the ticket from the
control pillar, the barrier is raised. The ticket issued to each customer has a bar code on it. The bar
code has a number on it and the date (ddmmyyyy) and time (hhmmss) of entry to the car park. The
number, date and time of entry are also printed on the ticket in human readable form. The details of
the ticket are stored in the system: ticket no., issue date, issue time, issuing machine etc. The
number of vehicles in the car park is incremented by 1 and a check is made against the capacity of
the car park. If the car park is full, then a display near the entrance is switched on to say ‘Car Park
Full’, and no further tickets are issued until a vehicle leaves the car park. The office staff are able to
redefine the car park capacity ion the system. COMP.6209 System Analysis and Design Payment
system When the customer is ready to leave, he or she must go to a pay station. System will
measure the exit time against the entry time. From this the car park charge is calculated and
displayed on the LCD display. The current date and time are added to the stored data for that ticket
(payment date, payment time).Customer will be prompted for options of payments, credit payment
and cash payment. If customer chooses the credit payment, he/she will be asked to enter their
credit card and system will connect with banking system to deduct the required amount. If the
customer chooses cash payments, system will ask the customer to enter the cash amount in the
machine. As soon as the amount accumulated equals or exceeds the charge, the ticket is validated
by the system. If the amount entered exceeds the charge and change is available, then the amount
of change is calculated and that amount of change is released into the return tray. Otherwise, no
change is given. In either case, a message is displayed on the LCD display. Calculation and display of
the charge must take no more than two seconds. At the time of ticket validation, ticket is inserted
into a slot and the bar code is read. The ticket bar code information is compared against the stored
information. If the dates or times are not valid (or any other error is detected), the ticket is ejected,
and the customer is instructed (via an LCD display) to go to the office. In the office, the attendant has
a bar code reader and can check the ticket. The attendant can use the office system to calculate the
charge, take payment and validate the ticket using office system. The ticket has the payment date
and time printed on it and is ejected from the ticket slot. All payment acceptance, ticketing, card
reading, printing and ejection should not take more than 20 seconds. Leaving the Car Park When 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 post. The customer must insert the ticket. 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 post is activated and connected to the
attendant in the car park office. The customer can talk to the attendant, and the attendant can view
the details of the ticket on his or her computer. The attendant can activate the barrier remotely, for
example if there is a queue to get out and the customer is likely to have been reasonably delayed. 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 (for example, because they have
backed out and left), then the control pillar for the next waiting vehicle is notified. COMP.6209
System Analysis and Design At any time, the attendant can view the status of a pay station or a
barrier control post once a connection is made; the status is updated every 10 seconds.
Tasks: The general intention is to design the required system through system analysis and design
techniques using UML modelling. Use the given case study to write a Business Requirements
Statement for the new system. Use the Unified Modelling Language (UML) to achieve the modelling
Task 8: Sequence Diagram for 2 selected Use Cases Produce set of sequence diagram for 2 Uses
cases that you produced narrative for in question 2, each diagram should have at least a paragraph
explaining the sequence diagram you made (Chosen UseCases for drawing sequence diagram can be
the same as the one were chosen for drawing communication diagram)
Hint1: (you can get help from the narrative you produced in task 2)
Hint 2: (Sequence diagram is the transformation of communication diagram, having sequence timing
in mind)
Task 9: Produce a Class diagram Produce a CLASS diagram that covers 2 parts of the system eg
Entry, Payment

Case Study Scenario

Uploaded by

Copyright:

Available Formats

Case Study Scenario

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Case Study Scenario

Uploaded by

Copyright:

Available Formats

Case study scenario: Car parking system Introduction: This is a case study about a public car park

You might also like