ICT103 Assignment: System Analysis Report on World Tour Company

This report presents a system analysis of the World Tour Company, an online platform for booking and paying for tours. The report begins with an introduction to the company and its need for system automation. It details the System Development Life Cycle (SDLC), including various approaches and methodologies, with a focus on the Waterfall Model as the chosen methodology due to the project's size and the need for departmentalization. The report outlines the phases of the Waterfall Model, including requirement gathering (using interviews), design, implementation, verification, and maintenance. It categorizes requirements into functional (authentication, business rules, login page) and non-functional (reliability, efficiency, maintainability, security, stability). The report concludes with requirement modeling and references used.

Family Name:
Given Name:
Student Number:
Lecturer’s Name: Shaleeza Sohail
Subject Name: Systems Analysis and Design
Assignment Title: System Analysis Report
Case Study: World Tour Company

Contents
Introduction................................................................................................................................2
Methodology..............................................................................................................................2
Types of approach in SDLC...................................................................................................3
SDLC Methodologies.............................................................................................................4
Waterfall Model..................................................................................................................4
Agile Model........................................................................................................................4
Chosen methodology..............................................................................................................5
Waterfall Model......................................................................................................................6
Requirement gathering...............................................................................................................7
Requirements..............................................................................................................................8
Functional requirements.........................................................................................................8
Non-functional requirements................................................................................................10
Requirement Modelling...........................................................................................................11

Introduction
Word Tour Company is a company that offer facility of booking and paying tours online. Due
to advancement of technology, it has raised a need for the company to automate its service in
order to get more clients all over the world. In order to achieve this, the company need to
develop a system where customers can search for the available tour packages and the tour
guide associated with that tour. This system checks whether the user exists or new. If new,
the customer enters personal and tour details for reservation. The system provides customer
with unique id and password. If the customer exists, the system asks the customer to login.
The system verifies the login credentials and if correct the system allows the customer to
continue with the booking process. Registered customers can update their personal details or
even cancel the tour package. Customer makes payments after confirming their touring
packages. Also customers can view the details of their touring details including the tour guide
who will be associated with the tour. Administrator can change, delete or modify the tour
scheme and the associated tour guide.
Methodology
Development life cycle is a term used to describe the process of planning, design and
implementation, testing, deployment and maintenance of an information system. The SDLC
aim at developing a high quality software of hardware. The SDLC involves a number of
clearly defined and distinct phases which are; (Kendall et al, 1992)
i. Planning.
This is the phase where by the whole procedure of developing the system is done. A
preliminary analysis is done and an alternative solution is proposed. The cost of the
whole activity is estimated.
ii. Designing.
In this phase the desired and required features of the system is visualised. This may
include screen layout, data flow diagrams, pseudo codes and how various components
are connected.
iii. Development and implementation
This is the phase where the actual system is created. The engineers can develop units
separately for easier development and specialization. This is the phase where the real
codes are written.
iv. Integration and testing

Various units are verified if they meet their requirements. Then these units are
integrated and tested as a system. Here the client data is used to check if the system
meets the desires of the client.
v. Documentation
After the system is verified that it meets the client specification, a document is
prepared that contains the usage and features of the system.
vi. Deployment and maintenance
This is the last phase of the SDLC. The verified system is put to work. Various users
of the system are trained on how to operate the system. Maintenance is the process of
correcting errors which were not detected in the other phases, improving the system
and updating the features of the system.
Types of approach in SDLC
The following are the two types of approaches in SDLC;
Predictive approach
Advantages
i. Easy to understand
ii. Easy to estimate the budget
iii. Easy to manage
Disadvantages
i. No prototype is produced until the end.
ii. Not suitable for complex system.
Adaptive approach
Advantages
i. There is high interaction between the developers and client which makes it easier to
understand the client requirement and to correct errors.
ii. There is transparency in the development process
iii. High quality system is realised
Disadvantages

i. There may be communication barrier between the client and developers.
ii. A lot of requirement emerges which may inconvenience the developers.
iii. High cost of development due to testing which is made in every stage.
SDLC Methodologies
There are several types of methodology the can be utilized in development of various
systems. The following are some of the common methodologies;
i. Waterfall model
ii. Spiral model
iii. V-shaped model
iv. Agile model
v. Big bang model
vi. Iterative model
Waterfall Model
This is a linear and sequential development model. Every phase of waterfall model has
specific objectives and when accomplished, the development proceeds to the next step
without turning back.
Agile Model
This model divides the requirements into small sections which can be developed in incremental way.
In this case study the requirements maybe divided in such a way that, the authentication part,
administration and database to be developed separately. Client involvement is a key principle in
agile model. (Rahimian et al, pp 342-337 2010) This model constitute of five stages as shown
in the figure below.

Chosen methodology
I find that waterfall model to be a suitable model for developing this system given in the case
study since it is a small project. Waterfall model will allow departmentalization and easy
management. A schedule can be set with deadlines and set budget since the developing
process moves progressively from requirement specification to the operation and
maintenance without overlapping of stages. Waterfall model has one disadvantage, which is
the lack of flexibility. Once an error is made in early stages it is not possible to correct till one
finishes the process. (Petersen et al, 2009)

Waterfall Model
The waterfall model contains the following steps as shown in the figure below.
Requirement
In this step, the developer will interact with World Tour Company staffs and some customers
to get their requirements. Some of these requirements are the security, business rules e.g. the
customer is given a unique id and password for security purposes. These requirements are
clearly stated to become system specifications. The system constraints are also identified.
Design
This is the step in which the system architecture is developed. The requirement gathered will
be allocated to ether software of hardware.
Implementation
This is the stage in which World Touring system designs are realised in terms of programs.
These programs are tested individually to verify that they meet their requirements.
Verification
These individual units are combined and tested as a system to verify that the system meets the
World Tour company requirements.
Maintenance

This is the stage where the tested system is put to work. Users are trained on how to operate
the system. The maintenance is a life process where the system is update time by time to meet
the upcoming requirements of the user.
Principles of waterfall model are;
Less Client involvement
Customer is involved only before the project begins to document his/her requirement and at
the end after the project is done to verify if the system meets his/her needs.
Strong documentation
There is strong documentation of the whole process since the client is not present in the
development process.
Sequential nature
Waterfall model is sequential in nature. One phase is complete after the other and once a
phase is completed there is no going back to it.
The reason why I choose waterfall model can be understood by looking at the following
advantages;
i. It is easy to manage.
ii. It is simple and easy to use.
iii. Different stages are completed one at a time.
Requirement gathering
This is a process of gathering requirements and conditions from the system users and
analysing the information. (Fabian et al, pp.7-40, 2010.) Though there many techniques to
gather information, we shall use interview in our case study. An interview is to be conducted
to some representative of World Tour Company in order to gather information about the
system to be developed. Below are some sample questions.
What are the objectives of the company?
What are the touring packages the company offers?
Which mode of payments do you prefer?
What details do the company require from the customer?

Also it is equally important to gather the information from the client/customer about the
system. The following are some of the questions that may help to get the information.
What feature would you need to be included in the system?
What is the mode of payment do you prefer?
What are the likes and dislikes of the existing system?
Requirements
Requirements can be categorized into two groups;
Functional requirements
These are statements of the services the system should provide, how the system responds to
certain inputs and how the system handles different situations. These requirements can be
classified further as user requirements and system requirements as shown below.
Some of these functional requirements are;
Authentication
This is a technique of allowing only those authorized users to access some services in the
system. For example in this case study, only those logged in customers will be allowed to
book tour package otherwise they are required to register with the company. Also only the

administrator can change, delete or modify the tour package details and tour guide associated
with the package.
Business rules
These are the set regulations on how the business is to be conducted. For example, customer
will only see their tour details after making the required payments. The business owner may
set terms and condition in which the business operate under.
Login page
This is a common page in systems which its function it to authorize only those users with
correct login details to access the system. The user login details are checked againist those
details that are saved in the system database and if there is an exact match then the user is
allowed to access the system. Otherwise the system output a message directing the user to
either enter the correct details or registered as a new user. This page also should give the user
a chance to recover his/her password.
Non-functional requirements
Reliability
The system should be accessible anytime, anywhere by the authorized customers. The system
should back up the database in case of any failure the data can be retrieved. The system
should give accurate feedbacks to customers. (Chung et al, 2012)
Efficiency
The system should be fast in processing the user requests even when there is many users who
are logged in. The system should have less loading time.
Maintainability
The system being developed should be able to accommodate future changes e.g. upgrading,
degrading and adding of new features.
Security
This is the most important functional requirement. The system developer is concerned on
how the user data is to be handled. The system must ensure that the user data e.g. the user
password is kept a secret. This can be accomplished by applying data encryption. The system
should also have a feature for retrieving data in case of any failure.

Stability
The system should give constant results when give the same input. The system should give
quality results in all circumstances.
Requirement Modelling
After gathering the requirements in this case study, the requirements can be represented in a
diagram as shown blow;
(Dennis et al, 2009)

References
Chung, L., Nixon, B.A., Yu, E. and Mylopoulos, J., 2012. Non-functional requirements in
software engineering (Vol. 5). Springer Science & Business Media.
Ilieva, S., Ivanov, P. and Stefanova, E., 2004, August. Analyses of an agile methodology
implementation. In Proceedings. 30th Euromicro Conference, 2004. (pp. 326-333). IEEE.
Kendall, K.E., Kendall, J.E., Kendall, E.J. and Kendall, J.A., 1992. Systems analysis and
design (Vol. 4). Englewood Cliffs, NJ: Prentice Hall.
Petersen, K., Wohlin, C. and Baca, D., 2009, June. The waterfall model in large-scale
development. In International Conference on Product-Focused Software Process
Improvement (pp. 386-400). Springer, Berlin, Heidelberg.
Radack, S., 2009. The system development life cycle (sdlc)(No. ITL Bulletin April 2009).
National Institute of Standards and Technology.
Fabian, B., Gürses, S., Heisel, M., Santen, T. and Schmidt, H., 2010. A comparison of
security requirements engineering methods. Requirements engineering, 15(1), pp.7-40.
Rahimian, V. and Ramsin, R., 2010, June. Designing an agile methodology for mobile
software development: A hybrid method engineering approach. In 2010 Second
International Conference on Research Challenges in Information Science(pp. 337-342).
IEEE.
Dennis, A., Wixom, B.H. and Tegarden, D., 2009. Systems Analysis and Design UML
Version 2.0. Wiley.