Tour and Transport System | Report

Running head: TOUR AND TRANSPORT SYSTEM
TOUR AND TRANSPORT SYSTEM
Name of the student:
Name of the university:
Author Note:

1TOUR AND TRANSPORT SYSTEM
Table of Contents
1. Use-Case Realization.............................................................................................................2
1.1. Analysis Class Diagram..................................................................................................2
1.1.1. Description of Class Diagram..................................................................................2
1.1.2. Class Diagram View................................................................................................3
1.1.3. Class Diagram Analysis...........................................................................................3
1.2. Communication Diagram................................................................................................4
1.2.1. Communication Diagram Description.....................................................................4
1.2.2. Communication Diagram View...............................................................................4
1.2.3. Analysis of Communication Diagram......................................................................5
2. Sequence Diagram.................................................................................................................5
2.1. Sequence Diagram Description.......................................................................................5
2.2. Sequence Diagram View.................................................................................................6
2.3. Analysis of Sequence Diagram.......................................................................................7
3. Evaluation of CASE Tool......................................................................................................7
3.1. Description of CASE Tool..............................................................................................7
3.2. Role of Analyst supported by CASE Tool......................................................................8
3.3. Role of Analyst supported by UML Modelling..............................................................9
References................................................................................................................................10

2TOUR AND TRANSPORT SYSTEM
1. Use-Case Realization
1.1. Analysis Class Diagram
1.1.1. Description of Class Diagram
The objects and the interrelationship between them is defined in the Class Diagram,
which is classified as one of the types of the structural diagrams of Unified Modelling
Language. The components also define their own functionalities in the system and state what
services the user can get from the system (Sulaiman, Ahmad and Ahmad 2019). Each
component of the class diagram that are known as objects has certain attributes, signals and
operations associated with it. Class diagrams helps in understanding the behaviour of a
system and explain the operations between them. Software developers use the class diagrams
to determine the objects and define their attributes while writing codes for a program to
develop a system.

3TOUR AND TRANSPORT SYSTEM
1.1.2. Class Diagram View
Figure 1: Tour Management System-Class Diagram
(Source: Created by Author using Enterprise Architect)
1.1.3. Class Diagram Analysis
In the management system of transport for the given case study, a class diagram is
generated stating clearly each object involved in the system that will have a role to play. The
objects in this management system are the Team Administrator, Finance Officer, Branch
Manager, Clerical Assistant, Tour Leader, Driver and finally the Customer. To each of these
objects are related certain attributes that defines their personal details like their name, contact
number, email ID and their respective registration ID in the system (Kumar and Singh 2015).
The services provided by each of the components and the operations done by them are
defined in the class diagram. For instance, the customer will book a tour and make the

4TOUR AND TRANSPORT SYSTEM
payment. The clerical assistant in the system manages the tour bookings, tour timings and
assigns drivers to the coaches. The branch manager supervises the operations carried out by
the clerical assistants and submits the cost reports to the Finance Officer.
1.2. Communication Diagram
1.2.1. Communication Diagram Description
Any management system has certain messages or communication between them. To
specify the messages interchanged, the communication diagram is constructed amongst the
components of the system. It is very similar to a sequence diagram, the only difference being
that it is not designed as sequentially as the sequence diagram including the time as well as
the order of events. Thus, it can be said that the communication diagram helps to understand
the interaction and the messages that are involved within the components of a system but it
does not clearly states the sequence of the messages amongst the components.
Communication Diagrams are thus widely used in the management systems to understand the
communication process.
1.2.2. Communication Diagram View
Figure 2: Tour Management System- Communication Diagram
(Source: Created by Author)

5TOUR AND TRANSPORT SYSTEM
1.2.3. Analysis of Communication Diagram
The Tour Management System has certain components involved in it and interaction
amongst these components are quite vital to establish the system properly. The main
component that interacts in the system is the Clerical Assistant who interacts with the Tour
Leader and does all the bookings of the tours (Popovic 2018). He asks for the price assigned
by the Tour Leader for a particular tour and saves into the system all the details associated
with a certain tour. Once all the details are saved for a particular system, the system displays
a message asking whether to assign a new driver for a new tour. The Clerical Assistant again
repeats the same process for a new tour. Thus, the interaction is mainly involved with the
Clerical Assistant and the system that works according to the instructions or the messages of
the Clerical Assistant (Shirado, Palma and Leite 2016). He also can instruct the system to
display the driver list, which are involved in the system and the ones who are active on their
duty.
2. Sequence Diagram
2.1. Sequence Diagram Description
The sequential diagrams are those type of UML Diagrams that displays the interaction
involved amongst the components sequentially according to the time and the order of events
that can happen in a system. Thus, the sequence diagrams are the depiction of the messages
involved that helps in having a clear understanding of the system and what the functionalities
should be (Jagtap et al., 2016). The diagram has a section called ‘Lifeline’ that clearly
specifies the entities or the objects of any system. The messages exist in the rest of the
diagram in a sequential manner stating the interactions and the decisions taken based on it.

6TOUR AND TRANSPORT SYSTEM
2.2. Sequence Diagram View
Figure 3: Tour Management System- Sequence Diagram

7TOUR AND TRANSPORT SYSTEM
(Source: Created by Author)
2.3. Analysis of Sequence Diagram
The sequential diagrams are being drawn using the software ‘Enterprise Architect’ for
the management system of the Wide World Tour. The sequential diagram is drawn keeping in
mind the ‘Use Case Description’ that clearly depicts all the functionalities of the Clerical
Assistant component (Lewis 2017). The Clerical Assistant is the main component of the Tour
Management System that does various types of tasks related to assigning and fixing tours,
updating tour destinations, assigning drivers, setting up tour types and so on. Hence, the
conversation is happening between the Clerical Assistant and the System User Interface
(Khurana, Chhillar and Chhillar 2016). The Lifeline of the diagram are the Clerical Assistant,
the System User Interface and the Screen Display. The message is being sent from the Screen
Display to the Clerk asking whether to add another driver or not. The Clerk has to reply to
this message with a ‘Yes’ or a ‘No’ according to his decision of wanting to assign a new
driver.
3. Evaluation of CASE Tool
3.1. Description of CASE Tool
Popularly known as the Computer Aided Software Engineering Tools, the software
aids that help in carrying out the processes in a Software Development Life Cycle are known
as CASE Tools. While developing a software, the SDLC procedure is followed that
comprises of the six steps of Planning, Analysis, Implementation, Design, Testing and
Maintenance. In this emerging era of technology, these procedures are not done manually.
Certain tools are designed for the execution of the processes in SDLC. These tools are Project
Management Tools, Documentation Tools, and Database Management Tools and so on
(Hooda and Chhillar 2015). All these tools together comprise to be known as the CASE tools

8TOUR AND TRANSPORT SYSTEM
that helps in development of a software. The project managers or software developers use
these CASE tools to execute the processes methodically in developing the software and
produce the desired result. The CASE tools help in developing the software in a robust
manner with the least amount of errors possible.
There also exists certain components of CASE tools that are generally used while
developing a software system. Central Repository is a pool where information are stored in
the CASE tool. To develop a software, various documentation is needed like the product
specifications, the software requirement specifications, reports and various diagrams and so
on. These documents help in clearly understanding the functionalities of the system. Central
Repository is the storage space where all this relevant information are stored (Sajja 2017).
Anybody starting from the project manager, to the developer and the tester can access to the
information required for developing the software from this pool of Central Repository
(Enikeev, Mohammed and Stepanova 2015). Due to this storage function, thus the Central
Repository is termed as the data dictionary of the system. Apart from this repository, there
exists Upper Case tools responsible for the planning and designing of the tour management
system and the tools of Lower Case that helps in testing and maintaining the transport system
at later stages. The Integrated Case tools available are responsible for integrating the system
at all stages of development. Each of the modules that are developed separately, are
completely integrated and tested by using the CASE tools.
3.2. Role of Analyst supported by CASE Tool
The CASE tools used in the development of the software prove to be of great help to
the analysts that are developing a software system for any company. By using these CASE
tools, the developers check what is expected of the software and what needs to be done
sequentially to incorporate in the system. Similarly, for the tour management system, the
developer takes help from these CASE tools to enhance the development process in a robust

9TOUR AND TRANSPORT SYSTEM
way. The selection of the CASE tool that can be of helpful assistance in the management
system is a vital one and training should be a key factor in selecting the type of CASE tool
that should be used in the system (Wrycza, Marcinkowski and Gajda 2017). The tool should
also support Reverse Engineering procedure. The Wide World Tour Management System
already had an existing framework on which they had their company running. While adapting
the Reverse Engineering process, they will not have to abolish their existing system, rather
they can modify the system into an advanced one by implementing the information software
system.
3.3. Role of Analyst supported by UML Modelling
The UML diagrams help a system to be designed and implemented easily and it
becomes easy for the software developers and the testers to follow these diagrams while
developing the system. The analysts follow these diagrams and check the order by which they
need to develop the system. The structural diagrams like the class diagrams, sequence
diagrams and the communication diagrams are the ones that are designed in the mentioned
case study of transport management system. These diagrams clearly depict the objects and
their respective attributes that needs to be incorporated in the system like the ‘Tour Details’,
‘Booking System’, ‘Clerical Assistant’, ‘Finance Officer’, ‘Tour Administrator and so on
(Pedreira et al 2015). The ‘Sequence Diagram’ helps to have a vision about the order of
events and the time of it, that should take place in the software system. The messages that are
carried out sequentially, are drawn in order in the given sequence diagram of the case study.
The communication diagram depicts the main messages that are exchanged between the
Clerical Assistant and the Graphical User Interface of the touring system. Thus, these
diagrams will assist the people involved in the project to develop the system in an organized
manner.

10TOUR AND TRANSPORT SYSTEM
References
Enikeev, A., Mohammed, M.B.A. and Stepanova, E., 2015, October. ON FORMAL TOOLS
IN THE SOFTWARE ENGINEERING. In 4th INTERNATIONAL SCIENTIFIC FORUM,
ISF 2015 (p. 24).
Hooda, I. and Chhillar, R.S., 2015. Software test process, testing types and
techniques. International Journal of Computer Applications, 111(13).
Jagtap, S., Gawde, V., Pawar, R., Shendge, S. and Avhad, P., 2016. Generate Test Cases
From UML Use Case and State Chart Diagrams. International Research Journal of
Engineering and Technology (IRJET), 3, pp.873-881.
Khurana, N., Chhillar, R.S. and Chhillar, U., 2016. A Novel Technique for Generation and
Optimization of Test Cases Using Use Case, Sequence, Activity Diagram and Genetic
Algorithm. JSW, 11(3), pp.242-250.
Kumar, B. and Singh, K., 2015. Testing uml designs using class, sequence and activity
diagrams. International Journal for Innovative Research in Science and Technology, 2(3),
pp.71-81.
Lewis, W.E., 2017. Software testing and continuous quality improvement. Auerbach
publications.
Pedreira, O., García, F., Brisaboa, N. and Piattini, M., 2015. Gamification in software
engineering–A systematic mapping. Information and software technology, 57, pp.157-168.
Popovic, M., 2018. Communication protocol engineering. CRC press.
Sajja, P.S., 2017. Computer-Assisted Tools for Software Development. In Essence of
Systems Analysis and Design (pp. 93-105). Springer, Singapore.

11TOUR AND TRANSPORT SYSTEM
Shirado, W.H., Palma, J.G. and Leite, V.M., 2016. Model Driven Architecture for
Development Test Automation Tools. In Proceedings of the International Conference on
Software Engineering Research and Practice (SERP) (p. 167). The Steering Committee of
The World Congress in Computer Science, Computer Engineering and Applied Computing
(WorldComp). (Shirado, Palma and Leite 2016)
Sulaiman, N., Ahmad, S.S.S. and Ahmad, S., 2019. Logical approach: Consistency rules
between activity diagram and class diagram. International Journal on Advanced Science,
Engineering and Information Technology, 9(2), p.552.
Wrycza, S., Marcinkowski, B. and Gajda, D., 2017. The enriched UTAUT model for the
acceptance of software engineering tools in academic education. Information systems
management, 34(1), pp.38-49.