ITC508 Object Modeling: Validation Phase Report for Car Parking System

This report details the validation phase of an object modeling project for a Collins car parking system. It describes three key subsystems: transaction processing, security, and invoice/pass printing. The report includes use case diagrams and sequence diagrams to illustrate the functionality of each subsystem. The transaction process covers payment methods and fraud detection. The security system focuses on detecting unauthorized activities. The invoice system outlines the printing process. A class diagram provides a static view of the system, showing the relationships between classes such as customer, payment, entry/exit, and collector. The report concludes by summarizing how these subsystems work together to manage the car parking system effectively. Desklib offers a variety of study resources, including past papers and solved assignments.

ITC 508
Object Modelling
Assessment 3
Validation Phase
Student Name:
Student ID:

Contents
Introduction......................................................................................................................................2
Description of subsystem.................................................................................................................3
Conclusion.....................................................................................................................................10
References......................................................................................................................................11
List of Figures
Figure 1: Transaction processing system use case diagram............................................................3
Figure 2: Use case diagram of ticket system security......................................................................4
Figure 3: Use case diagram of invoice & passes printing...............................................................5
Figure 4: Sequence diagram of printing invoice system.................................................................6
Figure 5: Sequence diagram of the transaction process...................................................................7
Figure 6: Sequence diagram of security process of parking............................................................8
Figure 7: Class diagram of Collins parking area.............................................................................9
1

Introduction
In this, the Collins car parking system wants to develop so the car is managed effectively. In this
report what are the subsystem used in the car parking are used are described. In the report how
the transaction system, security & printing system are constructed should use to design the
system. In this, the use case and the sequence diagram of the subsystem want to develop are
discussed. The class diagram of the Collins car parking system is discussed with the description.
With the help of these how the parking is managed and security is used are discussed in the
report.
2

Description of subsystem
In the description, the Collins car parking system is used in which three subsystems are used.
The first case is entry and the second case are payment mode chosen and the third case is exit
mode from the parking.
Use case diagram: The use case diagram can also call a behavioural model description in which
what actor is performing what actions individually or in the collaboration are discussed. In ovals,
the actions of the actor are defined and by the arrow the action that is used is discussed.
In first type, the record has kept a store of entry of each car. In second the payment is tracked by
the detector through sensors and detectors and store in the database if the person tries to give the
foreign amount then it will not accept and the alert is sent then security team catch the culprit. In
third case, the exit of each and every car are recorded so to manage the parking area effectively.
In Collins car parking system, the three subsystems that are used are developed in which actor
will play which function are discussed (Microsoft, 2016)
Transaction process
Figure 1: Transaction processing system use case diagram
In the use case diagram, two actors the costumer and the system manager who manages the car in
the parking are made. The customer enters in the parking area and gives the payment the
3

payment mode is either through card, coins and through notes than the notes and coins are
collected by the collector and the collector gives the collected money to the manager and the
collector will also provide the receipt to the user. If the person is selected the card payment, then
if they try to fraud by giving the other foreign type then an alert is generated. So the manager
manages it appropriately the parking area. In Collins parking system the transaction is recorded
in the database so that anytime the manager is not available then they can check it later and also
see all the details of all transactions.
In this transaction processing, it is the subsystem of the car parking. At the exit area, the
customer should provide the receipt which they get at the entry time so the collector checks that
they are right one or not. In the parking area, the customer is of two type either they are regular
or new if the user is regular then the pass is created in which they can give the pass at the entry
time so they are eligible to the entry.
Ticket security system
Figure 2: Use case diagram of ticket system security
Another subsystem that is created is a security system in the Collins car parking this provide the
security that no frauds and problems are caused by the system. In this subsystem the customer
4

when enter the parking then detecting device detected by sensors and detector then the detecting
device fetch the payment mode and if person is going in parking without pay or using any
foreign mode then the sensor device detects and send an alert and log are stored in the database
the security team are present which can go and catch the person. The log is using the cloud for
storing the data so it can be accessed anytime and from anywhere and the database is stored on
cloud so the maintenance problem is solved because the payments are given to the third party
who is offering the cloud service so they are managing the system. The system manager can see
the logs from the cloud and also see all the details of costumer and all see all the databases and
maintain the database (Altova, 2018).
Printing passes and invoice system
Figure 3: Use case diagram of invoice & passes printing
In the third system, the use case describes the printing system of passes and invoice of costumer.
In this subsystem costumer enters in parking and gives the payment from any mode then after the
payment, the customer is verified that they are giving the proper payment then after it will pass
5

to manager of system which manages all the parking system. Then CPU micro unit is giving the
agree of printing the invoice then they give request to print the receipt and if the printer is busy
in task one then error is generated and the error log is saved in the database then the CPU
manage the all logs the log is sent to another printer for printing the receipt. Then the receipt is
giving to the customer.
Sequence diagram
It will show how object are arranged in the sequence of time means what action are perform after
what are discussed like for buying any item the user first select what they want to buy. In
sequence diagram the action with the scenario are discussed where the relation is used by the
arrows can be discussed. In sequence diagram how system affect the overall designing can be
explained with this. In a sequence diagram, the vertical and parallel lines for different objects
and actors that are used in the system are discussed. In horizontal arrows the messages that are
taken in the occurring order (Agilemodeling, 2018).
Figure 4: Sequence diagram of printing invoice system
6

In this sequence diagram of printing invoice, the customer, payment, Micro CPU unit, manager
system & printer are the events and the scenario are present. In this, the customer is the main
event in the sequence diagram.
 In the first scenario, the payment is given through any mode.
 The second mode is sending the transaction history to the manager who manages all the
transaction.
 In third scenario, the transaction log is saved in the database.
 In the fourth scenario, the manager sees the transaction anytime later when they required.
 In fifth, the transaction is verified.
 In sixth, the customer gets the receipt are shown.
 In seventh scenario, the CPU unit is managing the printer which prints the receipt. In this, the
scenario the receipt is generated in the manner the request are sent from the CPU.
 In fifth scenario, the user is providing the receipt or the pass as the type of costumer.
Figure 5: Sequence diagram of the transaction process
7

In this subsystem of sequence diagram the customer, payment, collector & the system manager
ate event in the system. In this, the how transaction process and the transaction are managed
scenario is given.
In first scenario the customer when enter the parking they have pay first then they are allowed to
park the car. The customer has option to pay either through coin, card, notes.
When customer pay through card then first its verification is done then only they are allowed to
enter. Then all the information is pass to the transaction manager. The coins and the notes are
collected by the collector. The system manager is getting the transaction records. The money is
later collected by security team and manager of the parking area.
Figure 6: Sequence diagram of security process of parking
In this scenario, the customer, CPU, security team, database, manager, sensing device are the
events that are playing main role and the scenario are given.
In this, if any person is trying to put any of the foreign objects into the ticketing machine which
generates the ticket then it will be detected and an issue is generated and sent the alert to CPU
which will send to the backend & the security get a message. Then security team arrives and the
CCTV is also present which monitor the parking area so the culprit is catcher easily.
8

Class diagram of Collins car parking system
Class diagram: It shows the static view of a system. The class diagram is also used for construct
the code rather than describing, visualizing. A class diagram can also explain the attributes and
the related operation in the system. It is a collection or set of interfaces, classes, and the
association or collaboration in the diagram (Rouse, 2018).
Figure 7: Class diagram of Collins parking area
In a class diagram, the classes are a customer which are of two types divided regular customer
class and fixed customer class in this the other classes are payment classes, entry and exit class,
bill class, collector class.
In this class diagram, the attributes fields are written which are used in the class to describe. In
this class, relations are also defined as one customer is entering and take exit many times from
one car. And also one customer is generating a bill and pay multiple times for same car.
9

Conclusion
In this report, the Collins car parking system is developed which provide the security. In the
Collins car parking, the car is managed effectively so the system is designed which are operating
the entering and exit of car efficiently.
In this report the cars parking system the system is divided into three subsystem transaction
process, security and the invoice generating system by the combination the whole subsystem are
developed. In this report, the use case diagram and the sequence diagram of the three subsystems
are created with the description. In this report, the class diagram is also discussed for Collins car
parking system to design the system effectively.
10

References
 Agilemodeling. (2018). UML 2 Sequence Diagrams: An Agile Introduction. Retrieved from
http://www.agilemodeling.com/artifacts/sequenceDiagram.htm
 Altova. (2018). UML Diagrams. Retrieved from https://www.altova.com/umodel/uml-
diagrams
 Microsoft. (2016). Create a UML use case diagram. Retrieved from
https://support.office.com/en-us/article/create-a-uml-use-case-diagram-92cc948d-fc74-466c-
9457-e82d62ee1298
 Rouse, M. (2018). What is class diagram? Retrieved from
https://searchmicroservices.techtarget.com/definition/class-diagram
11