Collins Car Parking System Validation Phase: A Detailed Analysis of Entry, Management, and Exit Subsystems

This report delves into the validation phase of the Collins Car Parking System, focusing on the critical entry, management, and exit subsystems. It provides a comprehensive analysis of each subsystem, including detailed use case diagrams, sequence diagrams with descriptions, and a complete use case diagram encompassing all system functionalities. The report concludes with a class diagram illustrating the relationships between key classes within the system.

ITC508
Object Modelling
Assessment Item3
Validation phase
Student Name-
Student ID-

Table of Contents
List of Figures............................................................................................................................................2
List of Tables..............................................................................................................................................2
Introduction...............................................................................................................................................3
Interaction diagram...................................................................................................................................4
Collaboration diagram..............................................................................................................................4
Sequence diagram......................................................................................................................................4
Entry Subsystem and Exit Subsystem for Collins Car Parking System............................................5
Parking entrance system.......................................................................................................................6
Use case diagram...............................................................................................................................6
Sequence diagram..............................................................................................................................8
Parking management system..............................................................................................................10
Use case diagram.............................................................................................................................10
Sequence diagram............................................................................................................................11
Parking exit system..............................................................................................................................13
Use case diagram.............................................................................................................................13
Sequence diagram............................................................................................................................14
Full use case diagram..........................................................................................................................17
Class diagram..........................................................................................................................................19
Conclusion................................................................................................................................................20
References................................................................................................................................................21
1

List of Figures
Figure 1 Use case for car entrance system...................................................................................................6
Figure 2 Sequence diagram of car entrance system.....................................................................................7
Figure 3 Use case for car park management system....................................................................................9
Figure 4 Sequence diagram for car park management system...................................................................10
Figure 5 Use case diagram for car exit system...........................................................................................12
Figure 6 Sequence diagram for car exit system.........................................................................................13
Figure 7 Full use case description..............................................................................................................16
Figure 8 Class diagram..............................................................................................................................18
List of Tables
Table 1 Car entrance sequence diagram description..............................................................................7
Table 2 Car Park management sequence diagram description............................................................10
Table 3 Car exit sequence diagram description....................................................................................13
Table 4 Use case description...................................................................................................................16
2

Introduction
After successful completion of the first and second assignment, the next assignment is associated with
validation phase. This assignment three for Collins car parking system will be based on validation phase.
As the assignment one was an inspection phase and assignment two was elaboration phase and the third
assignment is validation phase. The report will include the three subsystems of use case diagram. The
report will also contain three sequence diagrams along with a description of sequence diagram activity.
And in the last section, a full use case will be design and class diagram will also be generated for Collins
car parking system.
3

Interaction diagram
Interaction diagram is a type of model which is used to define a group of objects merged in some manner-
typically known as a single use case. The diagram depicts objects and messages which passed between
objects in use-case. There are mainly two types of the interaction diagram i.e. sequence model and
collaboration model. The diagram made is very simple and easy to understand. The only weakness of
interaction diagram is that it describes the behavior but not define the behavior. The interaction diagrams
are used to show the collaboration among the objects but not give a proper idea of the definition of
behavior (Kumar & Bhatia, 2012).
Collaboration diagram
The collaboration diagram is the type of a visual presentation which is used to show that how different
software objects interact with one another and how the clients can take advantage of this collaboration.
The collaboration diagram is made from individual software pieces. The labels used in collaboration
diagram are determined by the user base. The collaboration diagram is a combination of arcs and vertices.
For every message in a collaboration diagram, there is associated sequence number for that.
Sequence diagram
The sequence diagram is a diagram which is used to presents the object connections which is arranged in
the time order. It is used to represent classes and objects from case scenario and order of messages
interchange among objects needed to transmit out functions of scenario. The other name for sequence
diagram is event scenarios and event diagrams. In the sequence diagram, the messages are written above
on horizontal arrows which display interaction. The solid arrows head is used to represent the open
arrowheads and synchronous calls are used to represent the asynchronous messages and the dashed line is
used to represent the reply messages. If the synchronous message is sent by the caller, he must wait until
the message is done and if the message is asynchronous he can send message continuously without the
need of getting a response. The sequence diagram is a good way for visualizing and validating the
different runtime scenarios. This diagram helps to predict about a system that how it will act in certain
conditions. The Unified modeling language object symbol is used to demonstrate the class roles. The
activation box is used to represent time which an object need for completing the task. When the object is
a busy thin gray rectangle is located vertically on the lifeline. The loop in the sequence diagram is
represented by a rectangle. The reply message is represented by dotted line (Smartdraw,2017).
There are various numerous components of sequence diagram which help in envisioning a time control
flow of the system. The components use for sequence diagram are mentioned below:
a. Message- The message is the type of information which flows in between objects. The messages
are represented as a pointed line in the sequence diagram.
b. Lifeline- The lifelines are always placed on top of the sequence diagram. The lifeline is
represented by vertical dashed lines which specify object’s occurrence over time.
c. Self-message- When an object is sent to itself, it is usually shown by U shape arrow which points
back to itself.
d. Reply message- The return or reply message is drawn with the dotted line and open arrowhead
also points back to the original lifeline (Zafar,2016).
4

Entry Subsystem and Exit Subsystem for Collins Car Parking System
The Collins car parking system is designed to help the customers and to provide the parking facility.
For Collins car parking system, the subsystem used for the validation phase is entry subsystem and
exit subsystem. The subsystem deals with process start when a customer enters and ends when a
customer makes exit. In Collins car parking system user enter into premises, system manage to
provide the space for car parking for users and exits when payment is done by customers. For these
three functionalities, the three use cases are designed along with sequence diagram.
5

Parking entrance system
There will be an access button in car parking system which will help to generate a ticket and print the
payment receipt. The barrier will open after ticket generation. A camera is also fitted to capture the
car details. The card details like car number, the color of the car, user details all get captured. At entry
point system will differentiate between the ordinary customer and fixed customer. The system has
different functionality according to customer type.
Use case diagram
The use case diagram is used to provide an overall overview of the system. There are three major
components of use case i.e. use cases, actors, and relationship. In this section, the Use case for car
entrance system will be discussed which gives an overall overview of car parking.
6

Figure 1 Use case for car entrance system
7

Sequence diagram
Figure 2 Sequence diagram of car entrance system
Table 1 Car entrance sequence diagram description
Components Description of components
Insert Card The user will enter the card into the system if he is a regular customer.
Card
validation
The system will validate the card details.
Card validates After validation, the system allows the user to park the car.
8

Barrier Raise Barrier will raise after successful customer validation.
Returns Card After card insertion, the card is returned to the customer.
Card not OK If the card is not validated barrier will not open.
Barrier Lows Barrier is closed.
Ticket generate The ticket will be generated for the ordinary customer.
Barrier Raise Barrier will raise after ticket generation.
9

Parking management system
This system is designed to properly manage the car parking management system. The ticket will be
generated for the customer at the entry point and help to automatically search the vacant space for car
parking. And if there is vacant space the car will get the space for parking. The entry and exit time of card
will be recorded for payment.
Use case diagram
This use case describes the car management. All the process involves in car park management are
discussed in this use case. The car park space is searched and if it is vacant user allocates the space for car
park.
Figure 3 Use case for car park management system
10

Sequence diagram
Figure 4 Sequence diagram for car park management system
Table 2 Car Park management sequence diagram description
Components Description
Enter into the parking area The user will enter into parking allowance.
Request for parking space Request is sent to user for vacant space by user.
Look for vacant space The admin will look for vacant space.
Vacant space detects The vacant space is detected for car park.
11

Allots vacant space The vacant space is detected and allocated for car parking.
Location sent The vacant space location is sent to the user.
Sent to parking space The user directed to vacant space for car parking.
Car Parked The car is parked by the user at vacant space.
12

Parking exit system
This system is designed for an easy exit for users. This system is used by the user when he leaves the
parking allowance. When user exit the parking space, he will submit the ticket and system will calculate
the fee for parking according to entry and exit time. And after successful payment user can leave the
parking allowance. The barrier will open after successful payment.
Use case diagram
This use case is designed for describing the overall exit system of the car when payment is successful.
Figure 5 Use case diagram for car exit system
13

Sequence diagram
Figure 6 Sequence diagram for car exit system
Table 3 Car exit sequence diagram description
Components Description
Input card The fixed customer will input the card in the system.
Entry and exit time record The entry and exit time of car is recorded.
14

Generate bill The bill is generated by the system for car parking.
Bill payment The bill is paid by the user for car parking.
Verification of payment The payment is verified by the user.
Returns card The card is returned to the user after payment.
Raise The barrier will open after successful payment.
Card not there If the card is not there the barrier will not open.
Lower If the card is not there the barrier will not open.
Gives ticket The ordinary customer will give a ticket for payment.
Entry and exit time record The entry and exit time of car is recorded.
Generate bill The bill for car parking is generated by the system.
Bill pay The bill is paid by the customer for car parking.
Verification of payment The payment is verified by the system.
15

Raise The barrier will open after successful payment.
16

Full use case diagram
The full use case for the car park management system is described in this section:
Figure 7 Full use case description
Table 4 Use case description
Use Case Description
Ordinary
Customer
Ordinary customers are the type of customer who is not a regular customer.
Fixed customer The fixed customer is the customer who re regular customer
Admin The admin is the person who manages the administration system.
Barrier The barrier is a gate which opens after successful payment
Clicks on barrier
button
The customer clicks on barrier button for using the car park management
system.
17

Make payment The customer makes payment for using the car park system services.
Card The card is a type of payment method.
Cash The cash is a type of payment method.
Enter parking
area
The customer enters into the parking area for car parking
Exit parking fee The customer exit from parking premises.
Billing The billing is done according to entry and exit time.
Generate bill The token is provided to the ordinary customer.
Input card The regular customer input card for entry.
Search parking The system searches the parking space for a car.
Validation of
card
The card is validated by the admin.
Filled area The system detects if the area is filled.
Vacant area The system detects if the area is vacant.
Accepts payment The system accepts the payment from the customer.
Record entry
and exit system
The entry time and exit time is recorded by the system for generating a bill.
18

Class diagram
The class diagram is used to depict the relationship between classes. In this section, the class diagram is
made for Collins car parking system (Albert, Cabot, Gómez & Pelechano, 2010).
Figure 8 Class diagram
19

Conclusion
The assignment three is based on validation phase. The assignment is based on Collins car parking system
case study. The implementation of each subsystem is discussed in this report. The report discussed the
three-use case. The report also discussed the sequence diagram along with its description of activities. A
diagram of complete case scenario is also made along with its description of use case. And in the last
section of the report, a class diagram is generated for defining the relationship among classes.
20

References
 Albert, M., Cabot, J., Gómez, C., & Pelechano, V. (2010). Automatic generation of basic
behavior schemas from UML class diagrams. Software & Systems Modeling, 9(1), 47-67. doi:
10.1007/s10270-008-0108-x
 Kumar, R., & Bhatia, R. (2012). Interaction Diagram Based Test Case Generation.
Communications In Computer And Information Science, 202-211. doi: 10.1007/978-3-642-
29216-3_23
 Smartdraw. (2017). Sequence Diagrams - What is a Sequence Diagram?. Retrieved from
https://www.smartdraw.com/sequence-diagram/
 Zafar, N. (2016). Formal Specification and Verification of Few Combined Fragments of UML
Sequence Diagram. Arabian Journal For Science And Engineering, 41(8), 2975-2986. doi:
10.1007/s13369-015-1999-9
21