Systems Analysis and Design Report: Wide World Tour Information System

This report provides a comprehensive analysis and design of an information system for Wide World Tour. It begins with an overview of the importance of class diagrams in depicting the static behavior of the proposed system, demonstrating their utility in visualizing, documenting, and developing executable code. The report then presents a class diagram for the 'add tour' use case, illustrating attributes, operations, and constraints. Following this, it explores communication diagrams, highlighting their role in showing interactions between objects to perform use cases, and presents a communication diagram for the 'add new tour' use case. The report then delves into sequence diagrams, explaining their function in demonstrating message sequences between objects, and includes a sequence diagram for the 'add new tour' use case. Finally, the report evaluates the role of CASE tools in information system development, emphasizing their impact on productivity and quality, and discusses different types of CASE tools used in various stages of the system development lifecycle. The report concludes with a discussion on the advantages of using CASE tools, including reduced development time and cost, and the importance of integrating these tools with standard software development methodologies.

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 developing an information system there are multiple diagrams and designs helps the
analysts a designer of the system to better understand the system and its behavior. The class
diagram is helpful in depicting the static behavior of the proposed information system (Stobart,
Thompson and Smith 2018). The Class diagrams are very helpful in not only describing,
visualizing, or documenting diverse aspects of any proposed system but also in the developing
executable code for the modules in the application. Following is the class diagram for add tour
use case;
Figure 1: Class Diagram for Add New Tour
(Source: Created by Author Using Enterprise Architect)
Class diagrams are also helpful in describing different attributes and as well as different
required operations for the classes as described by the clients. In addition to that, it is also

2SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
possible to impose constraints on the classes of the system to maintain the modularity. In the
present era, class diagrams widely utilized in modeling of the object-oriented systems as these
are only diagrams that can be mapped into the system modules object-oriented languages. With
the class diagram it is possible to depict the collection of different interfaces, associations,
classes, collaborations between then as well as constraints (Khan, Sengupta and Sarkar 2015).
The class diagrams are also known as a structural diagram.
In developing and designing a system with the planning and modeling of the system
with the classes and different relations it helps in making the programming process much easier.
In addition to that the making changes in the class diagrams designed for the system is
considered as easy compared to coding implementation of functionalities for the system after the
design process is time consuming and tedious job (Stobart, Thompson and Smith 2018).
The class diagram acts as the blueprint for the implementation of the system so that the
analysts can analyze and modify the system in the maintain ace phase.
Communication diagram
While working with the information system development projects the communication
diagrams are utilized in order to show interaction between the objects that are required in order
to perform and complete a particular use case or functionality or some part of any particular use
case. With the help of the communication diagrams, designers are capable of defining and
clarifying the roles of different objects in the use case in order to perform some particular flow of
events so that a functionality of the system can be achieved of a chosen use case (Shen, Tan and
Siau 2018). The communication diagrams are considered as the primary source in order to know
about the information used so that class responsibilities and interfaces can be determined.

3SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
Figure 2: Communication Diagram for Add New Tour
(Source: Created by Author Using Enterprise Architect)
Compared to the other UML diagrams, the communication diagram is capable of
depicting the relationships among different objects. Both the sequence and communication
diagrams express similar information, but in different ways (Khan, Sengupta and Sarkar 2015).
The communication diagram is more efficient in depicting relationships among different objects
and better tool for the analysts in order to understand the effects on the given object for a specific
use case in procedural design.
Due to the format in which the communication diagrams are structured and depicted, they
considered to be better matches in analysis tasks in any information system development
projects. Precisely it can be sad that communication diagram tends to be better tool in order to
depict simpler interactions among the minimal numbers of objects inside the system (Stobart,
Thompson and Smith 2018). With the increasing number of objects as well as messages between
them grows the related communication diagram becomes complex and hard to understand.

4SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
Furthermore, it becomes difficult to provide additional descriptive data about the interaction like
timing, decision points as the notes for a sequence diagram.
Part 2
Sequence Diagram
The sequence diagram in system design is a collection of participants and objects. The
participants in the sequence diagrams are the parts of the system which interacts with each other
during interaction. Objects in the sequence diagram represent class object in completing a use
case. It is depicted by its named icon on the top of the diagram.
In UML design phase the, Sequence diagrams allows the analysts to demonstrate sequence of
the different messages in a flow inside the system between the objects (Shen, Tan and Siau
2018). These diagrams are also helpful in depicting the interaction using the lifelines as a time-
ordered sequence. Following is the Sequence diagram for the Add New Tour Use case,
Figure 3: Sequence Diagram for Add New Tour
(Source: Created by Author Using Enterprise Architect)

5SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
Even though the sequence diagrams are used in order to explain any collaborations of
related messages among the objects of the classes most often one sequence diagram is used for
every single use case (Stobart, Thompson and Smith 2018). There are different kind of messages
as depicted below;
Synchronous messages: These type of message among the active objects refers to the
wait semantics. Sender of the message waits until the message is handled before it continues for
the next one. Usually, these messages invoke a method call.
Asynchronous: While using the asynchronous messages or flow of control, there are no
return message for the messages to the caller of the messages. Asynchronous message among
objects imply no-wait semantics (Khan, Sengupta and Sarkar 2015). In this type of
communication sender of the message does not wait for handling over the message before it
continues for further task. In this way, this type of messages allows the objects of the classes in
order to execute processes execute concurrently.
Reply: It depicts return message against a message from the sender.
Part 3
Evaluation of the CASE tools
In the modern-day information system development projects CASE (Computer Aided
Software Engineering) tools immensely helps in the improvement of the productivity of any
information system that is to be developed. Moreover, by providing support at every stage the
quality is also improved through the automation of the different tasks in development process.

6SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
Sequence fragments in the diagram makes the task of the analysts to create and maintain
the flow of message sequence for the project team in the maintenance phase. sequence
fragments are denoted by a box, known as the combined fragment, which encompasses a part of
a specific interactions.
Through the use of the CASE tools in the analysis phase to detect the concurrent
processes, their activations and their interaction with the objects or actors. Through the use of
the time sequenced messages in that are not easily depicted in other diagrams the analysts can
easily get the details of a processor (Shen, Tan and Siau 2018). From analysis and design to the
documentation of the system in order to have understanding about the logical flow of the system
the CASE tools are very important for information system project. There are different kind of
CASE tools available that can be used in the different stages,
Diagramming tools in the Analysis phase: Use of this systems are helpful in getting
idea about the different system process, data required in the different phases as well as control
structures in a graphical way.
Display and report generators: This kind of tool is helpful in defining and designing
the prototypes that helps in understanding the way system will look as well as feel. In this way,
this tool makes the process easier for analysts in order to identify relationship and data
requirements for the system.
Central repository: This tool enables the integration of the storage of specifications for
the proposed system, reports, different diagram as well as project management information.
Analysis tools: Utilization of this tool is helpful in automatically check for
inconsistency or incorrect specifications in the developed diagrams for the systems.

7SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
Documentation Generator: This tool of CASE tools produces user and technical
documentation by maintaining standard formats.
Automated Code generators: These tools help in automatic generation of application
as well as data base definition code from diagrams, design documents and reports.
Project Management Tools: There are different steps/tasks included in the software
project that needs to be managed and complied by managers in order to swiftly execute the
project. Activities like planning, project scheduling, cost estimation can be easily managed by
the project management tools available under CASE. Real-time data about the project activities
are stored by these tools.
CASE tool in any project should be flexible enough that can be easily integrated with any
information system project. Furthermore, the CASE tool supports standard software development
methodology and techniques (Khan, Sengupta and Sarkar 2015). Regardless of high cost of the
CASE tools the project teams provides great help in the development of the high-quality
information systems applications that even with the reduced cost and development time. With the
increasing complexity of the software engineering processes it becomes important to be as cost-
efficient as possible by reducing unnecessary overheads. With the CASE tool knowledge with its
complexity will continue to be helpful and efficient for the productivity of the projects.

8SYSTEMS ANALYSIS AND DESIGN FOR WIDE WORLD TOUR
References
Khan, G., Sengupta, S. and Sarkar, A., 2015, March. Modeling of services and their
collaboration in enterprise cloud bus (ECB) using UML 2.0. In 2015 International Conference
on Advances in Computer Engineering and Applications (pp. 207-213). IEEE.
Paola, Z.O.M., Rafael, V.P.M., Rolando, M.R.J. and José, C.S.M., 2016. Analysis of Upper
CASE Tools in Software Design Process. International Journal of Applied Engineering
Research, 11(18), pp.9377-9384.
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.
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.
Stobart, S.C., Thompson, J.B. and Smith, P., 2018. An Examination of Computer Aided
Software Engineering Tools as an Aid to Software Reliability. In Reliability 91 (pp. 152-161).
Chapman and Hall/CRC.
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.