System Analysis and Design Report: WorldTour Case Study

This report provides a comprehensive system analysis of WorldTour, an online tour booking company. It begins with an introduction to the case study, outlining its key features, including online booking and payment processing. The report then delves into various system development methodologies, such as the System Development Life Cycle (SDLC), and contrasts predictive and adaptive approaches. The chosen methodology for WorldTour is Agile, with a justification for its selection based on flexibility and adaptability. The report details the requirement gathering process, involving interviews with administrative staff. It lists both functional requirements, such as booking and payment functionalities, and non-functional requirements, including security and user-friendliness. Finally, the report concludes with requirement modeling, presenting an activity diagram illustrating the interactions within the WorldTour system. The report is designed to provide insights into system analysis and design principles in the context of the WorldTour case study.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of Student-
Name of University-
Author’s Note-

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
1. Introduction..................................................................................................................................1
2. Methodologies.............................................................................................................................1
3. Chosen Methodology...................................................................................................................3
4. Requirement Gathering................................................................................................................3
5. Requirements...............................................................................................................................4
6. Requirement Modelling...............................................................................................................5
References........................................................................................................................................6

2SYSTEM ANALYSIS AND DESIGN
1. Introduction
This report deals with the case study of an online tour booking known as WorldTour.
This company helps its customer to book tour online and also pay for the tour online. The case
study of WorldTour states it has administrative member to maintain the system and staff
members to guide the users who wants to book tour from the company. The customer can
register themselves with the company and then can search for the tour packages that the
company offers. The users can also search for the tour packages without registering and at the
time of booking they will have to register to keep track on their payment and booking id. The
payment that is done by the customer is done online via other payment intermediate applications
and only after the payment, the company confirms the booking for the customer. The staffs who
are associated with the company helps the customer to guide through the packages they are in
search of and offers package tour as per the requirement of the customers. The admin of the
WorldTour has the ability to add up new tour package, delete them as well as modify the price as
needed by them. This report discuss the methodology that can be used by the World Tour for
implementing the information system in the company and the activities of the actors involved in
the company are shown in this report in form of activity diagram.
2. Methodologies
For developing a system there is a system development life cycle that is to be followed in
the procedure of development. The SDLC process helps to design an information system of an
application and also ensure that all the functional as well as non-functional requirements are
fulfilled by the developer (Stark 2015). The SDLC approach of system development also ensures
all the requirements of the user that fulfils the objective of developing the system. There are

3SYSTEM ANALYSIS AND DESIGN
phases in SDLC method that helps to develop the application and track the development process
of the application. The phases are defined as planning phase, followed by defining phase. Then
comes the designing phase followed by building phase and testing phase. The last phase of
SDLC approach is deployment phase where the application is deployed.
Adaptive approach: This approach of system development schedules the planning and
finds out the milestone of project that is being carried out (Fang et al. 2016). The quick changes
that might be included in the system are included in adaptive method. This approach enhance
future changing of requirements in future.
Predictive approach: This approach includes planning as well as outlining the
functionalities of the project at the beginning of project starting (Chen et al. 2019). The scope of
the project and the functionalities of the project are not changed after starting the project. The
work is proceeded as per the documentation.
Advantages and Disadvantages of adaptive approach:
The advantage of adaptive approach is that it enhance future changing of the
requirements even after developing the system.
The disadvantage of this approach is the re-usability approach that is included (Bohnes et
al. 2018). A particular application can be developed in many different ways and that serves as a
drawback for the developers to decide which method is to be chosen.
Advantages and Disadvantages of predictive approach: At the starting of the project, the
objective and the scope of the project is defined clearly and there is no way to change the
requirement (Hölzl et al. 2015). This serves the developers as an advantage to carry out with the
project.

4SYSTEM ANALYSIS AND DESIGN
The disadvantage that this approach has is the requirement cannot be changed as per
usability testing and for doing the changes, developers has to start the process from beginning as
a new project requirement (Nicholas and Steyn 2017). Future change is not possible in predictive
approach.
3. Chosen Methodology
Agile methodology is chosen for developing the information system of the WorldTour.
The method of Agile will help the development team to build a flexible system. The advantage
that the agile methodology provides is changing the requirement of developing system in a
flexible way. While carrying out the usability testing, the objectives can be changed as per the
user requirement. The methodology of agile helps the development team develop an information
system in an adaptive manner, deliver the project in time and develop the project as per the user
requirement (Sulaiman, Ahmad and Ahmad 2019). The application can be built with the
changing response of the user in agile methodology of development.
4. Requirement Gathering
The requirement gathering for developing the information system for WorldTour is done
by conducting interview with the administrative staffs of the company. The requirements that
WorldTour needs in the information system are to be known to the developer and it is possible
only through interview process (Kerzner and Kerzner 2017). Some customers can also be
interviewed about what kind of service they are expecting from an online tour booking
application and the design the application as per the user requirement.
5. Requirements

5SYSTEM ANALYSIS AND DESIGN
Functional requirements that are included in the WorldTour system are listed below:
1. The customer want to book a tour, searches for the tour packages as per their
requirement.
2. For confirming the booking and proceeding with the payment option, the user needs to
register in the system.
3. All the personal information related to the staff are to be stored in the database of the
system.
4. In the system, the admin can modify the data, add new data and delete any package if
they want to.
5. The system will also have a payment interface for paying for the booked package.
Non-functional requirement includes:
1. The system should be secured as it contains personal data of the staffs and the customer.
2. The payment procedure should have an easy interface so that the users do not find any
difficulty while making the payment.
3. The storage system of the application should be large and secure as it will contain large
amount of data.

6SYSTEM ANALYSIS AND DESIGN
6. Requirement Modelling
Figure 1: Activity Diagram of WorldTour
(Source: Created by Author)

7SYSTEM ANALYSIS AND DESIGN
References
Bohnes, F.A., Hauschild, M.Z., Schlundt, J. and Laurent, A., 2018. Life cycle assessments of
aquaculture systems: a critical review of reported findings with recommendations for policy and
system development. Reviews in Aquaculture.
Chen, J., Xu, W., Zuo, H., Wu, X., Jiaqiang, E., Wang, T., Zhang, F. and Lu, N., 2019. System
development and environmental performance analysis of a solar-driven supercritical water
gasification pilot plant for hydrogen production using life cycle assessment approach. Energy
Conversion and Management, 184, pp.60-73.
Fang, L.L., Valverde-Pérez, B., Damgaard, A., Plosz, B.G. and Rygaard, M., 2016. Life cycle
assessment as development and decision support tool for wastewater resource recovery
technology. Water research, 88, pp.538-549.
Hölzl, M., Koch, N., Puviani, M., Wirsing, M. and Zambonelli, F., 2015. The ensemble
development life cycle and best practices for collective autonomic systems. In Software
Engineering for Collective Autonomic Systems (pp. 325-354). Springer, Cham.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and
technology. Routledge.
Stark, J., 2015. Product lifecycle management. In Product lifecycle management (Volume 1) (pp.
1-29). Springer, Cham.

8SYSTEM ANALYSIS AND DESIGN
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).