Software Design

This document provides a comprehensive study material on software design. It includes a foldable concept map model, use case diagrams, and a requirements table. The document also includes a bibliography for further reading. Find solutions for your software design assignments and essays at Desklib.

Running head: SOFTWARE DESIGN
Software Design
Name of the Student
Name of the University
Author’s note:

1SOFTWARE DESIGN
Table of Contents
1. Foldable Concept Map Model:....................................................................................................2
2. Use Case:.....................................................................................................................................4
3. Requirements Table:....................................................................................................................7
Bibliography:.................................................................................................................................11

2SOFTWARE DESIGN
1. Foldable Concept Map Model:

3SOFTWARE DESIGN
Figure 1: Foldable Concept Map of Bus in Metropolis
(Source: Created by Author)

4SOFTWARE DESIGN
2. Use Case:
Figure 2: Use Case Diagram of Bus in Metropolis
(Source: Created by Author)
Enter card at Entrance: The passenger will have a card with valid amount of money. At
the time of boarding the bus, the passenger will swipe the card into entrance gate. The system
will detect the passenger’s boarding bus stop. This use case is related to swipe card at exit gate.
The stakeholders are passenger, driver and Bus in Metropolis. If the card does not have valid
amount of money then passenger has to recharge the card.

5SOFTWARE DESIGN
Swipe card at Exit: At the time of leaving the bus, the passenger will swipe the card into
exit gate. The system will detect the passenger’s destination bus stop and charge for journey as
per distance covered. This use case is related to swipe card at entrance. The stakeholders are
passenger, driver and Bus in Metropolis. If the passenger does not swipe card at exit gate then
final destination of the bus will be considered as passenger’s destination bust stop and charge for
journey as per that.
Manage Journey: Bus drivers will have an interface using which the driver can manage
the journey. They can see the route and live status of the same bus on that same route. This use
case is related to indicate route. This use case has a precondition that bust should not have any
malfunctioning.
Add Bus: The administrator will be responsible for adding new buses in the routes so that
everyone can access the information of new bus. Administrator has an interface using which
busses can be added. Proper details of the bus such as route, bus number, type and other details
should be entered into the system. In order to enter the details of new bus, the administrator must
be logged into the system.
Assign Driver: Only the administrator can assign a driver to a bus. Each bus has to be
driven by a registered driver. The administrator can also add new bus in the route and assign the
driver of malfunctioning bus to that new bus. The related actor is administrator. This use case
does not have any related use case.
See Bus Journey Status: The administrator will have an interface that can fetch the
location and status of every bus in all the routes in real time. The admin can also search for

6SOFTWARE DESIGN
busses in a specific route or route of a specific bus. In order to access this information, the
administrator must have a valid account.
Use Case Name Search bus and route
Use Case ID Passenger_UC_03
Description The passenger can search for specific bus route or buses on a specific
route. This search can also show the currently available buses in the
route.
Actors Passenger
Related Use Case Manage Bus Service
Pre-condition The entered bus number or route is valid
Activities User System
Passenger enters the route or bus
number
System check the validity of
entered data
System accept the data if valid
Customer can see the information System fetch information and
show on passenger screen
Post condition Only the active buses or routes are shown to passenger
Exception Passenger’s application is not able to establish connection
Use Case Name Indicate route
Use Case ID Driver_UC_02
Description The driver can indicate when a journey starts by selecting route in the

7SOFTWARE DESIGN
provided interface
Actors Driver
Related Use Case Manage Journey
Pre-condition A driver is assigned to the bus
Activities User System
The driver will see the list of
routes in the interface
The system fetch and show all the
route information in the interface
The driver will select one of the
available routes
System accept the data
Activate the route and shows the
live location
The system updates the
information in the system
Post condition The live location of the driver is available on the interface of driver
Exception The bus is cancelled
3. Requirements Table:
Requirement Description Source
Authentication Authentication allows the
system to determine the
validity of the user. This way
the system can share and
accept authorized information
from valid user only. In order
to implement authentication,
Administrators, Drivers and
Passengers

8SOFTWARE DESIGN
the system must register the
users into the system.
Authorization Authorization is the technical
term that refers to check the
validity of a user to access the
requested information or
process. The system will have
three authorization levels for
three users. The passenger
can only search information
where the drivers and
administrator can write data
into the system.
Administrators, Drivers and
Passengers
Search bus The passenger can search for
buses directly using the
application. The system will
fetch every detail of the bus
and show it in the screen.
This information includes live
location of bus. The
administrator can also search
for buses.
Passenger and Administrator
Update bus location @bus sub-system will update System

9SOFTWARE DESIGN
the location of the bus based
on the current bus stop it is
in. The transponders within
the bus will be responsible for
identifying the bus stop.
Place a bus out of service The bus driver will contact
the administrator through
phone if a bus starts
malfunctioning. After
receiving the information, the
administrator will mark a bus
out of service and the system
will remove the bus from
availability.
Administrator and bus driver
Add a new bus The administrator can add a
bus into the system by
entering all the required
details into the system. Once
that bus starts a journey, the
system will update the live
feed continuously and show
that information to authorized
users.
Administrator

10SOFTWARE DESIGN
View time table The administrator can view
the time table of each buses
of specific route using the
system. For this, they have to
enter the start and destination
stop.
Administrator
Data Storage The system will need to store
all the data in a medium that
can be accessed for writing
and reading data. This storage
can be NoSQL database. It is
because, NoSQL database are
capable of handling a lot of
data in efficient time.
System

11SOFTWARE DESIGN
Bibliography:
Afanasyev, A.N., Voit, N.N., Voevodin, E.Y. and Gainullin, R.F., 2015, October. Control of
UML diagrams in designing automated systems software. In 2015 9th International Conference
on Application of Information and Communication Technologies (AICT) (pp. 285-288). IEEE.
Fernandez-Saez, A.M., Genero, M., Chaudron, M.R., Caivano, D. and Ramos, I., 2015. Are
forward designed or reverse-engineered UML diagrams more helpful for code maintenance?: A
family of experiments. Information and Software Technology, 57, pp.644-663.
Khan, F., Jan, S.R., Tahir, M., Khan, S. and Ullah, F., 2016. Survey: dealing non-functional
requirements at architecture level. VFAST Transactions on Software Engineering, 9(2), pp.7-13.
Mahmoud, A. and Williams, G., 2016. Detecting, classifying, and tracing non-functional
software requirements. Requirements Engineering, 21(3), pp.357-381.
Torre, D., Labiche, Y., Genero, M. and Elaasar, M., 2018. A systematic identification of
consistency rules for UML diagrams. Journal of Systems and Software, 144, pp.121-142.
Torre, D., Labiche, Y., Genero, M., Baldassarre, M.T. and Elaasar, M., 2018, May. UML
diagram synthesis techniques: a systematic mapping study. In 2018 IEEE/ACM 10th
International Workshop on Modelling in Software Engineering (MiSE) (pp. 33-40). IEEE.