KOI: Modelling System Requirements - System Analysis and Design

This report provides a comprehensive analysis of system requirements, focusing on the QuickCabs case study. It begins with an introduction to the project, highlighting the need for a cab booking system and the importance of system analysis and design. The methodology section details the Software Development Life Cycle (SDLC) and its phases, followed by a comparison of predictive and adaptive approaches. The report then explores various SDLC methodologies, choosing agile methodology as the most suitable for the project. It discusses requirement gathering techniques using questionnaires and outlines both functional and non-functional requirements for the system. The functional requirements include the ability for customers to select rides, make online payments, and change locations, while non-functional requirements emphasize availability, reliability, and flexibility. A diagram is developed to model the system's functionality. The report concludes with a bibliography of relevant sources.

Running head: SYSTEM ANALYSIS AND DESIGNING
Modelling System Requirements-
SYSTEM ANALYSIS AND DESIGNING
Name of the Student
Name of the University
Author Note

1SYSTEM ANALYSIS AND DESIGNING
Table of Contents
Introduction......................................................................................................................................2
Methodology....................................................................................................................................2
Types of SDLC approaches.............................................................................................................3
SDLC methodologies.......................................................................................................................4
Chosen Methodology.......................................................................................................................4
Requirement gathering.....................................................................................................................5
Requirements...................................................................................................................................5
Requirement modelling...................................................................................................................6
Bibliography....................................................................................................................................8

2SYSTEM ANALYSIS AND DESIGNING
Introduction
The main purpose behind developing a modelling requirement based on a case study is to ensure
that the challenges faced by the group have been removed effectively. Case study is mainly
defined as the process that can be used for the development purpose and ensures that all data are
being collected.
QuickCabs is an emerging online company that evolved with the purpose of fulfilling the needs
of the customers who wishes to travel from one location to other. The online company allows the
customer to book a cab and ensures that the customers are able to pay for the fares online. With
the launch of these applications everyone will be able to search for the available taxis around and
book at any time. This system will start processing the request by checking whether the user is
new or existing one.
The main purpose behind choosing this case study is that it will help in analyzing the needs of
booking system and will ensure that the system is able to carry out all the necessary functionality
including the new users addition in the system, checking for the taxis availability and will ensure
that proper amount of fair is being calculated based on the distance. With the help of system
analysis and designing it will become easy to determine the functionality of the system.
Methodology
Software development lifecycle is considered as one of the best methodology that can be used
for the purpose of developing software. This ensures that the development process has been
executed properly stepwise. This methodology ensures that the quality of software has been
enhanced with the development process.

3SYSTEM ANALYSIS AND DESIGNING
In order to develop software with the help of SDLC process it becomes essential to follow the
basic steps. This includes:
 Phase 1: Planning
 Phase 2: Designing
 Phase 3: implementation
 Phase 4: Testing
 Phase 5: Documentation
 Phase 6: Deployment
 Phase 7: Maintaining
Types of SDLC approaches
There are basically two different types of approaches that are offered with the methodology of
SDLC. This includes predictive approach and adaptive approach.
Predictive approach: predictive approach in SDLC methodology includes assuming the fact that
the development related to the project is being planned in the early stages and the new
information system can be developed based on the plan.
The major benefits that are offered with the use of predictive approach include:
 Ensures that the project is being executed with stable requirements and minimizes the
changes through the project progress period.
 This method ensures that the development process is measurable enough for determining
the success criteria.
The major disadvantage that comes along with the use of predictive approach includes:

4SYSTEM ANALYSIS AND DESIGNING
 This method is time consuming and thus impacts the process of software development.
Adaptive approach: this is an approach that mainly focuses on assuming the basic requirements
for the project and ensures that all flexible criteria are being implemented within the project at
the time of project execution.
The main benefits that are offered with an adaptive approach include:
 The major benefit includes better and improved monitoring process.
 The system is being developed based on the well detailed criteria.
The disadvantages that come along with the implementation of this method include:
 The methodology involves a lot of requirements and this increases the development
process.
 Testing at every single stage increases the project cost and also the time.
SDLC methodologies
There are different numbers of SLC methodologies that ensures better development of software
within a project. The basic methodologies that are included in SDLC methodologies are waterfall
model, V shaped model, Spiral model, iterative model, agile model, and big bang model.
Chosen Methodology
The best methodology for the purpose of analyzing the booking system is agile methodology.
Agile methodology helps in development of the process iteratively and ensures that all the
requirements are being successfully implemented within the system. the main advantage behind
selecting this methodology is that it has the potential to provide high quality products and

5SYSTEM ANALYSIS AND DESIGNING
ensures that the customer satisfaction has increased. The main aim is to ensure that the booking
system is able to perform all the basic tasks on the application starting from transaction to
booking process.
Requirement gathering
While developing a system and analyzing the requirements process it becomes essential to
evaluate the necessary requirements so that it can provide better support towards the people
associated with the project. The main aim of launching these applications is to facilitate the
transport process and ensures that the cabs can be easily booked from any location. The
requirement gathering method that is used for this case study is questionnaire. With the help of
this question sets it will become easy to analyze the benefits obtained with the system. The set of
questions are as follows:
 How the developed application will support the customers?
 With the implementation of new design it will become easy to manage the service rate or
not?
 State the benefits that will be obtained with the use of this application?
Requirements
The requirements that are essential for carrying out the system designing phase for QuickCabs is
that it will be able to meet all the basic needs of the customers. The basic requirements are
divided into functional and non functional requirements.
Functional requirements

6SYSTEM ANALYSIS AND DESIGNING
The functional requirements that are associated with the online cab system are as follows:
 Customers are allowed to select their rides
 Can make payment online
 Can change location
Non functional requirements
The non functional requirements that are essential for QuickCabs are availability, reliability,
flexibility. It is expected that with the implementation of this online application it will become
easy to manage the customers.
Availability: availability ensures that the developed system online cab is made available towards
the customers for 24*7 so that they can ensure effective services.
Reliability: reliability ensures that the developed system is able to meet the customer’s
requirement and can be accessed at any time. In case of any emergency purpose the customers
are allowed to select the emergency service so that they can get quick assistance.
Flexibility: flexibility is provided towards the customer that ensures the system is compatible to
run at any platform.
Requirement modelling
Diagram is being developed based on analysis of the system. With the help of an activity
diagram it becomes easy to understand the functionality of newly developed system. The
diagram is being described below:

7SYSTEM ANALYSIS AND DESIGNING

8SYSTEM ANALYSIS AND DESIGNING
Bibliography
Eckhardt, J., Vogelsang, A. and Fernández, D.M., 2016, May. Are" non-functional" requirements
really non-functional? an investigation of non-functional requirements in practice. In 2016
IEEE/ACM 38th International Conference on Software Engineering (ICSE) (pp. 832-842). IEEE.
Jayawardena, P.G.R.P., 2013. Transport Management System For Wasi Quick Cabs & Tours
(Pvt) Ltd (Doctoral dissertation, University of Colombo).
Laplante, P.A., 2017. Requirements engineering for software and systems. Auerbach
Publications.
Mahalakshmi, M. and Sundararajan, M., 2013. Traditional SDLC Vs Scrum Methodology–A
Comparative Study. International Journal of Emerging Technology and Advanced
Engineering, 3(6), pp.192-196.
Ragunath, P.K., Velmourougan, S., Davachelvan, P., Kayalvizhi, S. and Ravimohan, R., 2010.
Evolving a new model (SDLC Model-2010) for software development life cycle
(SDLC). International Journal of Computer Science and Network Security, 10(1), pp.112-119.
Tong, Y., Chen, Y., Zhou, Z., Chen, L., Wang, J., Yang, Q., Ye, J. and Lv, W., 2017, August.
The simpler the better: a unified approach to predicting original taxi demands based on large-
scale online platforms. In Proceedings of the 23rd ACM SIGKDD international conference on
knowledge discovery and data mining (pp. 1653-1662). ACM.
Zhu, Q. and Azar, A.T. eds., 2015. Complex system modelling and control through intelligent
soft computations (Vol. 319). London, UK: Springer.

9SYSTEM ANALYSIS AND DESIGNING