MOD002581: Carpool System Design with UML Diagrams - Case Study

This document presents a system analysis and design for a carpool system at Eastern Industries, addressing the limitations of their current spreadsheet-based booking process. The analysis includes various UML diagrams such as use case, class, sequence, activity, state, and entity-relationship diagrams. The use case diagram outlines interactions between receptionist, manager, staff, and the system, detailing functionalities like booking, performance monitoring, and email notifications. The class diagram defines classes such as Manager, Staff, Carpool, and Receptionist, along with their attributes and methods. Sequence and activity diagrams illustrate the workflow of booking a car, while the state diagram shows the different states of car availability. The entity-relationship diagram maps the relationships between staff, cars, and management roles. The document concludes that the proposed system will enhance efficiency and provide better monitoring capabilities for Eastern Industries.

System analysis
System analysis
1 [Date]
[Year]
|

System analysis
Table of Contents
Table of Contents...........................................................................................................................1z
Introduction......................................................................................................................................2
Wireframe………………………………………………………………………………………..2
Use Case Diagram...........................................................................................................................2
Class Diagram..................................................................................................................................3
Sequence Diagram...........................................................................................................................4
Activity Diagram.............................................................................................................................5
State Diagram..................................................................................................................................6
Entity Relationship Diagram...........................................................................................................7
CONCLUSION................................................................................................................................8
REFERENCES................................................................................................................................8
2 [Date]

System analysis
Introduction
Eastern Industries is a large manufacturing company that is looking forward to creating a carpool
system that will replace the existing system. The current system comprises of a receptionist desk
where a staff member has to request for a booking and records are kept in a spreadsheet which is
difficult to work with. The current system does not also allow the manager to monitor the
performance of the vehicles and how the staff members are using the system.
The process of developing any software, there is a need to generate UML diagrams that are used
to communicate to the system designer on whom the system is supposed to behave. UML is a
standard language that is used in constructing, visualizing, specifying and documenting
components of the system.
Wireframe
This diagram represents the framework of the website. It has several menus as show above this
include Vehicle Performance ,History of booking cancelation, History of booking failed to
collect vehicles and the logging out. When the user clicks on one of them a specific page appears
like us shown above.
3 [Date]

System analysis
Use Case Diagram
A use case diagram is usually developed at the infant staged of a system development. In the use
case diagram above, there are four actors; receptionist, manager, staff and the system itself
(Briand, Labiche, & Leduc, 2016). The use case scenarios of the receptionist include:
 The receptionist can view the system for cars that are available for booking for that day.
 The receptionist can make a booking for a customer who was already requested for
booking, this use case scenario is extended from the view state of booking where the
receptionist should ensure that the car is available for booking.
 The receptionist should also be able to see the car booking for the next 7 days.
 Before a car is booked to a staff member, the receptionist has to ensure that the staff has
the required skills to operate the vehicle.
The carpool system is also supposed to carry out some operations automatically thus making it
an actor. The use case scenarios include:
 The system should generate and send an email to the receptionist once the staff has
requested a booking for a car.
 The system should also generate a list of staff who fails to show up
The use case scenarios of the staff include:
 A staff can take classes for unfamiliar vehicles
 Request a car from the receptionist
The use case scenarios of the manager include:
The manager should be able to view the performance of each car
The manager should be able to determine whether to buy or sell a car based on the performance
of each car.
The manager should be able to view canceled bookings to ensure that the system is not misused
The manager should be able to view bookings that the staff failed to show up.
4 [Date]

System analysis
The manager should be able to view the entire booking history of the system.
Class Diagram
A class diagram in unified modeling language (UML) is a diagram that aims to show the
relationships and how the sources codes interdepend among each other. A class is used to define
the various variable and methods that exist in an object.
There are four classes in the class diagram; manager, staff, carpool and the receptionist.
The class staff has the following attribute; staff ID, staff phone number, staff name, and the staff
email address. The operations that are contained in this class include; taking driving classes,
requesting a car, using a car and returning a car.
The class Manager has the following attributes; manager name, manager phone number and the
manager email address. The methods in this class include; buy a car, sell a car, view a car
performance, view entire booking history and view canceled booking.
The class receptionist has the following attributes; receptionist name, ID, phone number and the
email address. The operations in this class include; view available cars for the day, view cars
booking for the next 7 days, view the state of a booking and make a booking for a staff.
The class car-pool has the following attributes; the number of cars, car ID and car model. The
operations in the car-pool class include; stores cars, generate car performance chart, log all
5 [Date]

System analysis
bookings, generate list for the canceled bookings, generate list of the car available for the day,
generate list of bookings for the next week and generate and send an email to the receptionist
when a staff member request for a booking(Lai, & Sastry,2013).
Sequence Diagram
A sequence diagram is an interactive diagram that depicts how the operations in a system are
done by capturing how the interaction between objects is carried out. They are time conscious
and show the order of the transactions by using vertical axes.
The sequence diagram of Eastern Industries has one actor and two objects (Bernardi, Donatelli,
& Merseguer, 2012). The actor starts by sending a request to the reception desk, the receptionist
desks verifies if the staff has the required skill. If the staff has the skill set, then no message is
replied but if not the staff is recommended to take the necessary classes.
The reception desk checks if there are available cars from the car -pool. If there are no available
cars for booking, then the reception desk can book an already booked car (Ungar, 2011). If
6 [Date]

System analysis
there is a car available for booking, the receptionist sends the booking details to the staff.
Activity Diagram
An activity diagram is a UML diagram that is used to define the dynamic aspects that are in a
system. The activity diagram of the Eastern Industries is in the following order form the
initiation to the termination:
 The staff initiates the activities by requesting for a car from the receptionist desk.
 The receptionist validates that the staff has the required skills if not the staff is referred to
attending training for the required skill.
 If the staff has the required skill, the receptionist verifies if there is a car available for
booking, if there is no car then the receptionist can decide to book for an already booked
car.
 If there is a car available for booking, the staff is booked a car
 Once a staff has a car booked to him, if he or she fails to appear to take the car, the
booking is canceled and the car is returned to the not-yet-booked cars.
 If the staff appears and uses the car, he or she returns the car which is taken to the not-
yet-booked cars and the activity is terminated.
7 [Date]

System analysis
State Diagram
As from the name of the UML diagram, it is clear that the diagram aims at expressing the state in
which the specific components in a system are in. the states that are described by the state chart
can be induced by internal or external factors.
The state diagram of the Eastern Industries starts as the staff has no car booked to him or her. At
this state, the staff may request for a booking and he can either remain in that state or be handed
a booking. For the state to remain in the state pf without a car, it can either be that there is no car
available or that the staff making the request does not have the required skills to operate the
vehicle.
8 [Date]

System analysis
Entity Relationship Diagram
Also referred to as an entity-relationship model, it is a Graphical representation of how the
people, places, concepts, events and object of a system are related to each other.
The Eastern Industries ERD is made up of six entities, namely; common staff, car, senior staff,
manager, receptionist, and a chauffeur. The manager can have zero on more common staff while
the common staff can have only one manager (Ekanayake, & Kodituwakku, 2015). A staff
member can be booked to either zero or one car while a car can be booked to either one staff or
no staff. For the senior staff, a car is assigned to each thus having a one to one relationship. The
senior staff can have only one manager as the manager can have either have zero or many senior
staff. The chauffeur is only assigned to the manager thus having a one to one relationship.
The receptionist can only have one manager while the manager can have either many or zero
receptionist.
.
9 [Date]

System analysis
CONCLUSION
Based on the ERD diagram, I can, therefore, conclude that the system that will be developed will
ensure that Eastern Industries has an effective system. Form the system the manager will be able
to monitor all the factor of his firm. It will also allow the receptionist to work efficiently. In
addition, the system will be able to automate some of the tasks thus making the work of the
receptionist and the manager easier.
REFERENCES
Briand, L. C., Labiche, Y., & Leduc, J. (2016). Toward the reverse engineering of UML
sequence
10 [Date]

System analysis
diagrams for distributed Java software. IEEE Transactions on Software
Engineering, 32(9), 642-
663.
Bernardi, S., Donatelli, S., & Merseguer, J. (2012, July). From UML sequence diagrams and
statecharts
to analysable petri net models. In Proceedings of the 3rd international workshop on
Software and
performance (pp. 35-45). ACM.
Ekanayake, E. M. N. K., & Kodituwakku, S. R. (2015, August). Consistency checking of UML
class and
sequence diagrams. In Ubi-Media Computing (UMEDIA), 2015 8th International
Conference
on (pp. 98-103). IEEE.
Lai, Y. T., & Sastry, S. (2013, July). Edge-valued binary decision diagrams for multi-level
hierarchical
verification. In Proceedings of the 29th ACM/IEEE Design Automation Conference (pp.
608-613).
IEEE Computer Society Press.
Ungar, P. (2011). On diagrams representing maps. Journal of the London Mathematical
Society, 1(3),
336-342.
11 [Date]