Systems Analysis and Design for Wide World Tour: Coursework Report

This report presents a comprehensive Systems Analysis and Design (SAD) for the Wide World Tour Management System. It includes detailed analysis using UML diagrams such as class diagrams, communication diagrams, and sequence diagrams to model the system's structure and behavior. The report examines the purpose and usage of these diagrams, illustrating their application in representing entities, relationships, and dynamic interactions within the system. Furthermore, it evaluates the role and impact of CASE (Computer-Aided Software Engineering) tools throughout the Software Development Life Cycle (SDLC), emphasizing their importance in improving productivity, quality, and cost-effectiveness. The report also explores the benefits of CASE tools in various stages of the SDLC, including requirements gathering, design, implementation, and maintenance, highlighting their contribution to enhanced system development and maintenance, and the reduction of human errors.

Running head: SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
Systems Analysis and Design for Wide World Tour
Name of the Student
Name of the University
Authors note

1SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
Part 1
Analysis class diagram
In any information system the classes represent the entities with a level of an abstraction
along with some characteristics. The associations among the different classes denotes the
relationship among the classes inside the system. along with this, the class diagrams are also
helpful in depicting the overview of the proposed information system to be built while describing
objects and their related classes inside it. Following is the class diagram for the use case;
Furthermore, it also has wide range of usage, which includes the modeling of domain-
specific data structures in order to have a detailed design view about the system (Shen, Tan and
Siau 2018). With the help of the sharing models it is possible for the analysts to reuse class
model in interaction diagrams in order to model detailed design about the dynamic behavior in
different scenarios. Moreover, the class diagrams are helpful in exploring the related data and
attributes of the classes, getting faster realization of the entities which will be important in
developing the system. In addition to that, analysts can also notice whether there are too

2SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
few/many classes for the proposed system and relationships between the objects of those classes.
Too complex or too many relationships can increase the dependencies among the classes/objects.
Communication diagram
Communication Diagram are mainly used in order to model and depict dynamic behavior
of a selected use case for the proposed information system for wide world tour. When the
communication diagram is compared with the sequence diagrams, it is found that communication
diagrams are more concerned in depicting the collaboration between the objects instead of time
sequence of the interaction. Following is the communication diagram for the Add tour Use case;
It is also possible to automate the creation of both the diagrams manually because CASE
tools can generate from one to the other (Srinivasan, Lee and Yang, 2016). Through the
communication Diagram combination of the information collected from use case, class diagrams
as well as from the sequence diagrams that describes static as well as dynamic behavior of the
proposed for Wide World Tour Management System. Through the communication diagram it is
possible to model alternative scenarios for a chosen use cases that requires involvement and

3SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
collaboration of objects and interactions between them. Moreover, it also Supports in the
identification of the involved objects that participate in completing the use cases.
Part 2
Sequence Diagram
As the name of the UML diagram recommends the sequence diagrams are used in order
to define sequence of different messages/interactions which are passed among the actors and
objects in the specific scenario. In a specific scenario the actors and object are active only in the
scenario whenever another object/actor wants to interact with them (Shen, Tan and Siau 2018).
All the messages in the interaction is listed and depicted in chronological order. In the sequence
diagrams the interaction between the objects and actors are displayed using the horizontal line.
On the other hand, time is represented using vertical line inside the diagram. As this tool is a
very good way to describe the dynamic view of the information system which is not possible
from the static modeling of the system (Srinivasan, Lee and Yang, 2016).
Sequence Diagrams in the UML designing are helpful in modeling the collaboration
among the objects depending on the time sequence of the interactions. This diagram depicts the

4SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
way objects communicate with each other in a specific scenario of the selected use case (Shen,
Tan and Siau 2018). With the complex interactions among the objects complex sequence
diagram with return or error messages. In addition to that, different tools are capable of
generation of sequences diagrams from other data flow of events which are important in
different case descriptions.
While designing the sequence diagram it is kept in mind that, sequence diagram
maintains the chronological order of messages in order to complete a specific use case. Thus.
1. The messages from the objects and actors are depicted in time sequence.
2. No reply message from any actor to object is sent until there is a request messages
from other objects/actors of the use case.
Part 3
Evaluation of the CASE tools
Aim of the CASE tools and technology is improving productivity as well as quality of
proposed system through assisting the developers and analysts throughout the stages of the
project life cycle. From the stage of acquiring the functional/nonfunctional requirements for
designing and implementation of the proposed system while considering different relevant
technical as well as operational features for the system.
Regarding the maintenance phase of SDLC of any project major impact of using CASE
tools is ease of the maintenance of the developed system. Certainly, the most important impact
attributed to different stages of SDLC by organizing the issues and resolving them in the

5SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
maintenance phase. From the different researches it can be stated that major grounds in the
system maintenance phase is to meet and accommodate new requirements that needs to be added
to the system as the enhancements. At this stage the CASE tools become important as it can be
used in order to help the developers and analysts to do a thorough system analysis as well as
design so that it can be ensured that new functional requirements are completely incorporated in
the developed system. In turn this helps in order to reduce the huge amount of subsequent system
maintenance activities and cost due to the ill-defined user requirements. In addition to that, it
also provides the developers more prospects in order to focus on adding the enhancements rather
than checking for the issues in the system.
CASE (Computer Aided Software Engineering) tools plays a very important role in
improving the productivity of the proposed information system as well as its quality by assisting
and automating repetitive and important tasks in software development processes. Within CASE
tool, multiple parametric software cost models that are provided by the CASE tool as one of the
tools which had significant impact on software development projects productivity. In the
present era most of the information system development project teams utilize the CASE tools
which are assembled over time. The teams adopt newer CASE tools without establishing any
evaluation criteria. It is found that the while using the software cost models assess different
productivity impacts on the project. In the testing phase of the development project of the
information system, accuracy of computer-generated code needs to be checked with test data.
Without the human error in design phase system should be able to produce desired correct
results. Whereas in case of the wrong output testing results then it can be can utilized in order
detect the design errors.

6SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
Understanding different relationships among the modules is being designed along with
the interaction with the external environment is essential. In this way, it can help in deciding the
way in which the required system functionality will be achieved (Srinivasan, Lee and Yang,
2016). Structure in which the system communicates with environment is also important. It also
helps the analysts to establish boundaries of the proposed system. By setting system boundaries
it is possible to determine the features that needs to be implemented in the system being designed
and developed and the features that are to be implemented in the associated systems.
Another important aspect of using the CASE tool is related to the data administration in
the proposed system. This is probably one of the least discussed but important aspect of using
the CASE tool. It is found that the CASE provides positive gain in the integration activities of
different modules of software development process as well as in data administration (Shen, Tan
and Siau 2018). Most of the system components like design specification, programs, data are
usually stored in central repository which is shared by the applications.
The CASE central repository is considered as one single point of control in any system
development project for managing the system development project along with related data. In
this way CASE tools helps in improving quality and reliability of the system and logically result
in enhanced client satisfaction. Where as in some researches it is found that the some of the
developers and clients believes that machine-generated code is less efficient compared to the
programs that were developed programmers (Srinivasan, Lee and Yang, 2016).
Finally, it can be stated that the authoritative benefit of using the CASE tool is cost
reduction in the different stages of the development.
CASE tools can help in considerable improvement in the quality of the proposed system.

7SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
Through the use of the CASE tools in different stages of Development and maintenance it
is possible to reduce chances of human error in those stages.
CASE tools are also efficient in order to produce high quality as well as consistent
documents for the systems.
CASE tools assist and automates the developers and analysts’ tasks.
Case tools are very important in creating entity models along with the data flow ,
establishing relationships among the requirements and various models.

8SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
References
Shah, S.A.A., Bukhari, S.S.A., Humayun, M., Jhanjhi, N.Z. and Abbas, S.F., 2019, April. Test
Case Generation using Unified Modeling Language. In 2019 International Conference on
Computer and Information Sciences (ICCIS) (pp. 1-6). IEEE.
Shen, Z., Tan, S. and Siau, K., 2018. Challenges in Learning Unified Modeling Language: From
the Perspective of Diagrammatic Representation and Reasoning. Communications of the
Association for Information Systems, 43(1), p.30.
Mouheb, D., Debbabi, M., Pourzandi, M., Wang, L., Nouh, M., Ziarati, R., Alhadidi, D., Talhi,
C. and Lima, V., 2015. Unified Modeling Language. In Aspect-Oriented Security Hardening of
UML Design Models (pp. 11-22). Springer, Cham.
Srinivasan, M., Lee, Y. and Yang, J., 2016, April. Enhancing Object-Oriented Programming
Comprehension using Optimized Sequence Diagram. In 2016 IEEE 29th International
Conference on Software Engineering Education and Training (CSEET) (pp. 81-85). IEEE.
Torre, D., 2016, October. Verifying the consistency of UML models. In 2016 IEEE
International Symposium on Software Reliability Engineering Workshops (ISSREW) (pp. 53-54).
IEEE.
Sarkar, D., Bhalla, M. and Singal, S.M., 2017, January. Enhancing unified process workflows
using UML. In 2017 7th International Conference on Cloud Computing, Data Science &
Engineering-Confluence (pp. 788-792). IEEE.
Mithun, M. and Jayaraman, S., 2017, September. Comparison of sequence diagram from
execution against design-time state specification. In 2017 International Conference on Advances
in Computing, Communications and Informatics (ICACCI) (pp. 1387-1392). IEEE.