Collin's Car Parking System: Use Case and Sequence Diagram Analysis

This project report details the design and analysis of a smart car parking system for Collin's Car Parking, a prominent organization in Melbourne. The report focuses on three key subsystems: customer registration, payment processing, and ticket generation. Each subsystem is illustrated with use case and sequence diagrams created using MS VISIO, providing a clear visual representation of the processes involved. The customer registration process allows users to create accounts, streamlining the parking experience. The payment process supports multiple payment methods, including card payments and payment gateways, ensuring flexibility for users. The ticket generation process enables users to request and receive parking tickets based on their needs. The report emphasizes the importance of these functionalities in enhancing customer comfort and maintaining a competitive advantage. The diagrams and descriptions are designed to be accessible to both technical and non-technical stakeholders, offering a comprehensive overview of the proposed system's design and functionality. The project also includes a summary and references to support the findings.

Running head: COLLIN’S CAR PARKING SYSTEM
COLLIN’S CAR PARKING SYSTEM
Name of Student
Name of University
Author note

1COLLIN’S CAR PARKING SYSTEM
Table of Contents
Overview of Collin’s Car Parking...................................................................................................2
Use case & Sequence Diagram of Customer Registration Process:................................................3
Use case & Sequence Diagram of Payment Process:......................................................................6
Use case & Sequence Diagram of Ticket Generation Process:.......................................................9
Summary:.......................................................................................................................................11
References......................................................................................................................................13

2COLLIN’S CAR PARKING SYSTEM
Overview of Collin’s Car Parking
Collin’s car parking is one of the most prominent car parking organisation of Melbourne
that operates over 20 car parks in the city of Melbourne CBD. The organisation is planning to
update its services to smart services to offer comfort to the customers and maintain a competitive
advantage at the same instance. The system requirement states that the system should be capable
of upgrading all the process such as ticket generation, payments, records maintenance and others
to the online means. According to the system’s requirement there are multiple important
processes and the deemed report has taken account three important functions of the system. The
first is to have a suitable customer registration process through which they can make an account
that will collect the necessary details of the customers and mitigate the effort invested in
repetitive uploading of documents and customer verification. The second is the payment process
which will enable the customer to generate online tickets and other necessary actions. Finally,
the third is the ticket generation according to the needs of the customer.
The three functional requirement of the system has been depicted in the use case scenario
and their sequence diagram has also been provided to understand the process & steps involved in
successful completion of the project. The diagrams have been drawn in the MS VISIO tools and
a brief description of each of the diagram has been discussed. Finally, a summary of the
discussion has been attached at the end of the paper with a bibliography to cite the sources that
assisted in completing the deemed assignment. Another notable fact is that the language of the
report has been kept simple to ensure that it is understandable to both the technical and the non-
technical stakeholders associated with the Collin’s Car parking services.

3COLLIN’S CAR PARKING SYSTEM
Use case & Sequence Diagram of Customer Registration Process:
Figure 1: Use Case of Collin’s Registration Process
(Source: Created by Author Using MS VISIO)

4COLLIN’S CAR PARKING SYSTEM
Figure 2: Sequence Diagram of Collin’s Registration Process
(Source: Created by Author Using MS VISIO)
The diagrams above have cited the registration process into the system of the Collin’s
server. It is prominent because it will assist the customers to verify themselves as an associated
external stakeholder of the organisation and will also prevent the customers to verify their
identity every time they enters the system and wishes to book a parking spot for themselves.
Additionally, it will even make the customers eligible for the perks that the organisation offers to
the regular users. Another notable fact is that the use case and the sequence diagram has been
designed taking consideration of the fixed customers of the Collin’s. Though the system can also
be used by the users who only pay when they use the parking service. The users can register

5COLLIN’S CAR PARKING SYSTEM
themselves and use the service. The description of the diagram has been discussed in the
following paragraphs.
The first defined by the diagram is that after the user opens the application or website of
the Collin’s car parking on line module. The system will cite an option that will ask for the login
or signup process. The registered users can use the services of the organisation by signing in the
system while the first time users need to make an account to access the services of the parking
organisation. The first step of making an account is to select the “Registration” which will take
the user to the registration page where the user will be asked for the personal details. The details
will include “Name of the User”, “Date of Birth”, “Email Id”, “Date of Birth”, “Sex: Male,
Female or other (It will be a checkbox)”, “Preferred locations that the user will use the parking
services”, “Mode of services that the user wishes to adopt (monthly, weekly, daily)” and others.
Additionally, the mode of services will flash a message “Permanent membership will offer a
designated parking stop”. After the details are filled and submit button is clicked the system will
verify the validity of the data and provide a ticket generation to the system UI (User Interface).
The system UI will then flash the login details page where the user will create the login details
according to their comfort. The login details input by the user will then be verified by the
administrator system and give ticket generation to the System UI which will then respond to the
user. The details collected from the user will then be saved in the database of the organisation.
Post completion of the login details, the user is now able to login to the system and access the
services of the organisation.
The key players & actors of the deemed subsystem are the customer, admin, ticket
generation and the system UI. The communication that takes place in the deemed scenario are
the communication between the system UI & user, System UI & the server, Admin & the server

6COLLIN’S CAR PARKING SYSTEM
and among the admin and the database. The key processes are request registration page, input
details and select login detail by the user. While, the organizational server, admin, database &
system UI is responsible for validating the customer details, citing availability of login and
saving the details in the server.
Use case & Sequence Diagram of Payment Process:
Figure 3: Use Case of Collin’s Payment Process
(Source: Created by Author Using MS VISIO)

7COLLIN’S CAR PARKING SYSTEM
Figure 4: Sequence Diagram of Collin’s Payment Process
(Source: Created by Author Using MS VISIO)
The payment process of the Collin’s parking services demanded special attention because
it is a major process and it extend to three primary factors from user and organisation to the bank
or payment gateway owners. Additionally, the payment options that are proposed as part of the
service extend from card payment to payment gateway and others for user’s comfort which
further enhances the complexity. The use case and the sequence diagram has been attached
above and the description of the process within the proposed system has been attached in the
following paragraphs.
Post selection of the ticket validity type that is monthly, weekly, daily or yearly, the user
is derived to the payment module of the system where the user needs to select the payment mode

8COLLIN’S CAR PARKING SYSTEM
that they want to progress with. The payment options available for the users are card payment
(credit card, debit card and others), micro-banking payment gateways (such as PayPal and
others) or the cash delivery when the user reaches at the parking spot. Then, the user is supposed
to select the payment mode which will drive the user to that gateway where the user will need to
further shortlist their selection in case of the cards. The user needs to select the mode of payment
from the available card options from the debit card, credit card and others if available. Post
completion of the selection the user will be driven to the payment gateway of the selected mode
of payment. In case of the card selection the user will be driven to the bank’s gateway and for
micro-finance they will be taken to their gateway. The next process would involve the bank
which will collect the payment request form the organizational server and then ask the user to
justify their association with the bank. The justification will be done based upon the credentials
that the user offers to their payment gateway and after the verification is done. The bank will
send a notification to the user and the organizational server to ensure the completion of the
transaction. After receiving the payment, the user will be notified by the system of Collins and
they will be provided with an online ticket that will confirm their parking duration and location.
For the cash payers the system will offer them a slip that will enable them to park their vehicle
after paying cash.
The key players & actors of the deemed process are the bank, user and the system and
organizational server & admin. The communication that takes place are between the user & the
organizational system, the user & the bank or payment gateway and the organizational systems
& the bank or other payment system. The key processes that takes place are the mode of
payment mode, further shortlisting the selection and entering the credentials to the payment
gateways by the users. On the contrary, the bank receives input from the organizational system,

9COLLIN’S CAR PARKING SYSTEM
receives credential from the user & sends notification to the user and the Collin’s system as well.
Finally, the organizational system processes involve assistance in shortlisting the payment modes
& factors, receive payment & notification from the payment module and confirm the user of
process completion by offering them the desired output.
Use case & Sequence Diagram of Ticket Generation Process:
Figure 5: Use Case of Collin’s Ticket Generation Process
(Source: Created by Author Using MS VISIO)

10COLLIN’S CAR PARKING SYSTEM
Figure 6: Sequence Diagram of Collin’s Ticket Generation Process
(Source: Created by Author Using MS VISIO)
One of the key processes that is vital for the sustainability of an organisation is to take
ticket generations from the users and accordingly upgrade its services. Hence, the system of
Collin’s car parking should add an adequate functionality for the ticket generation process and
hence has been selected as one of the sub-processes that needs discussion. The use case of the
discussed process has been attached above which has been further produced as a sequence
diagram to increase the understandability of the system and process. The following paragraphs
offers an insight in the working and key factors & components of the discussed process.

11COLLIN’S CAR PARKING SYSTEM
The first role of the discussed task is played by the customer who inputs response in the
system by selecting the ticket generation option. The next measure is taken by the system UI
which displays the message of the categories about which the user wishes to provide his/her
ticket generation. Then, the user inputs their response which is then collected by the ticket
generation system from the system UI and processed in appropriate category that is monthly,
weekly, daily or any other category. After categorizing the ticket generation, it is sent to the
administrator system which will take necessary action about the ticket generation after the
payment is done. In the final step of the discussed process, the administrator receives a
notification message from the ticket system and on confirmation posts it to the system UI which
is displayed on the display. The flashed message includes a “thank you” notification for the
ticket generation along with ticket for the details provided by the user. The deemed step
completes the ticket generation process.
The key actors and objects of the ticket generation sub-process are the user, System UI,
ticket generation server and the admin. The communications in the deemed sub-process take
place between the customer & the system UI, system UI & the ticket generation system, Ticket
generation system & the admin and the admin & the system UI. The key processes that takes
place are the process of entering input from the user, sending the input to the ticket generation
system which categories it and then forward it to the admin. Finally, a ticket generation
receivable notification to the user which completes the discussed ticket generation process from
the customer to the system.