University Project: Modelling System Requirements for QuickCabs

This project report focuses on modeling the system requirements for QuickCabs, a newly established online company providing various services. The report begins with an introduction to QuickCabs, highlighting its goals of providing excellent customer service and addressing transportation needs. It then explores different System Development Life Cycle (SDLC) methodologies, including Predictive and Adaptive approaches, and justifies the selection of the Adaptive approach for its flexibility in accommodating changing requirements. The report details requirement gathering techniques such as questionnaires, interviews, and surveys. It then outlines both functional requirements, such as software requirement specifications, system models, and use cases, and non-functional requirements, including usability, security, performance, and reliability. Finally, the report includes a requirements modeling diagram (Figure 1: The Cab Booking Facility within the new system) and concludes with a list of relevant references.

Running head: MODELLING SYSTEM REQUIREMENTS FOR QUICKCABS
Modelling system requirements for QuickCabs
Name of the Student
Name of the University
Author note

1MODELLING SYSTEM REQUIREMENTS FOR QUICKCABS
Table of Contents
1. Introduction..................................................................................................................................2
2. Methodologies.............................................................................................................................2
3. Justification of Chosen Methodology..........................................................................................4
4. Requirement Gathering................................................................................................................4
5. Functional and Non-Functional Requirements............................................................................4
6. Requirements Modelling.............................................................................................................6
References........................................................................................................................................7

2MODELLING SYSTEM REQUIREMENTS FOR QUICKCABS
1. Introduction
The analysis in this report focuses over the most important aspects of QuickCabs, which
is newly established online company that helps in providing different kind of facilities to
customers. The online website primarily aims to provide the best class of service to their
customers and thus target the main areas from which they would be able to create a large base of
customers. In the present times, the government of different countries focus over an equitable,
safe and affordable mode of transportation.
The envision of QuickCabs is to bring in transparency in data, provide on-demand cab
service to their customers and also solve real-time needs of transportation escalated by
customers. The discussed case focuses over the important factors of car availability based on the
search facilities built within the website. However, certain improvements would still be needed
based on designing a new cab booking system (Alias et al. 2014). This new system would allow
customers to update their own details and modify with their own information. The administrators
would also be able to modify information and gain information about their drivers and users
within the system. The discussion would also focus over a certain methodology that would help
in development of the system and define the necessary requirements that would be required for
designing the system.
2. Methodologies
System Development Life Cycle (SDLC) – The SDLC is defined as a term, which is
mainly used for the process of development, maintenance and replacement of the software
system. It also comprise of different kind of steps that includes the stages of planning, designing,
developing, testing, deployment and maintenance over the software product (Khan, Parveen and

3MODELLING SYSTEM REQUIREMENTS FOR QUICKCABS
Sadiq 2014). With the implementation of this model, it would be highly useful for the creation of
the new booking system for QuickCabs.
The Predictive Approach to SDLC – The predictive methodology within SDLC
specifies the certain stages that would be performed during the stages of development of the
software. Based on defining the certain steps of development process, a specified budget and
timeframe is also provided. It thus helps in defining an easy way of predicting timelines and
budget.
The main usefulness of the approach is that it helps the team to define an expected budget
and describe the timeframe required for the completion of the project (Moparthi and Geethanjali
2016). The overruns within the project are minimized within the approaches towards predictive
SDLC.
The limitations within this approach is that by making use of this approach, the software
product for QuickCabs would only be produced at the final stage of the entire process. Any form
of requirement that might not had been put in within the development process, would result in
zero effort to the entire solution (Pears, Finlay and Connor 2014). The development process
might need to be set up again in order to integrate the new requirement. This would increase the
time of delivery of the software product to a huge extent.
The Adaptive Approach to SDLC – The adaptive software development approach
provides opportunities to stakeholders for kicking off with software development projects and
further describe each of the project stages. The development team would work in collaboration
with other teams to develop the software product successfully.

4MODELLING SYSTEM REQUIREMENTS FOR QUICKCABS
The usefulness of this approach is that they help in bringing transparency within the
process of software development (Dora and Dubey 2015). The developers would explain the
progress over the development phase after each of the performed steps. Clients would thus be
able to share personal opinions with them regarding any changes.
However, the primary limitations of this approach is that due to the agile nature of the
approach, there is a high growth of emergence of requirements at each stages of development.
Testing is mostly integrated at every phase of the lifecycle. Hence, it further leads to increase in
cost factors.
3. Justification of Chosen Methodology
Based on the discussion over the methodologies, it can be described that adaptive
approach towards SDLC would be suitable for the design of the new booking system for
QuickCabs. During the development of the new software product, different requirements might
creep in and thus the development team would need to make changes accordingly. However,
limitations are also present in relation to increase of cost factors of the project but would lead to
the successful development of the software product.
4. Requirement Gathering
In order to capture the requirements of the business and understand the specifications as
mentioned for the new system, the certain techniques that could be used are questionnaires to the
owner proposing the new system. Interviews could also be conducted over user groups and
employees within the company (Davey and Parker 2015). Surveys would also be done in order to
understand the current business scenario and the ways of upgrading the business prospects.

5MODELLING SYSTEM REQUIREMENTS FOR QUICKCABS
5. Functional and Non-Functional Requirements
Functional Requirements – The functional requirements of the development of the new
cab booking system are:
1. A software requirement specification (SRS) document.
2. Models of the system that would help in presenting a prototype model of the system
under development.
3. Use cases defining the interaction of the system with the users.
4. Documentation of the entire system defining the specifications about the working
capability of the product (Eckhardt, Vogelsang and Fernández 2016).
5. System testing requirements that includes End-to-End testing, system integration
testing and API testing
Non-Functional Requirements - The functional requirements of the development of the
new cab booking system are:
1. Usability of the system would be defined. This would help the owner or user to
understand the type of intuitiveness of the application. The efficiency of use of the system
2. The requirements for security implemented within the software would also be
considered to be a primary requirement (Alruwaili and Alrajhi 2018). The confidential
information would be encrypted so that the vital information might not get hacked by outsiders.
3. The performance factors for the new cab booking system would need to be determined.
This would define the responsiveness factor of the booking system.

6MODELLING SYSTEM REQUIREMENTS FOR QUICKCABS
4. Reliability of the software system should also be determined. Based on this factor, it
could be determined whether the software would perform without any kind of failure or bugs
within its code.

7MODELLING SYSTEM REQUIREMENTS FOR QUICKCABS
6. Requirements Modelling
(Figure 1: The Cab Booking Facility within the new system)
(Source: Created by author)

8MODELLING SYSTEM REQUIREMENTS FOR QUICKCABS
References
Alias, Z., Zawawi, E.M.A., Yusof, K. and Aris, N.M., 2014. Determining critical success factors
of project management practice: A conceptual framework. Procedia-Social and Behavioral
Sciences, 153, pp.61-69.
Alruwaili, F. and Alrajhi, M., 2018. How Agile Development and Its Tools Support Digital
Transformation. INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY, 18,
pp.7440-7450.
Davey, B. and Parker, K., 2015. Requirements elicitation problems: a literature analysis. Issues
in Informing Science and Information Technology, 12, pp.71-82.
Dora, S.K. and Dubey, P., 2015. Software Development Life Cycle (SDLC) Analytical
Comparison and Survey on Traditional and Agile Methodology. National Monthly Referred
Journal of Research Science and Technology, 2(8).
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.
Khan, M.A., Parveen, A. and Sadiq, M., 2014, February. A method for the selection of software
development life cycle models using analytic hierarchy process. In 2014 International
Conference on Issues and Challenges in Intelligent Computing Techniques (ICICT) (pp. 534-
540). IEEE.
Moparthi, A.N.R. and Geethanjali, B.D.N., 2016, February. Design and implementation of
hybrid phase based ensemble technique for defect discovery using SDLC software metrics.

9MODELLING SYSTEM REQUIREMENTS FOR QUICKCABS
In 2016 2nd International Conference on Advances in Electrical, Electronics, Information,
Communication and Bio-Informatics (AEEICB) (pp. 268-274). IEEE.
Pears, R., Finlay, J. and Connor, A.M., 2014. Synthetic Minority over-sampling technique
(SMOTE) for predicting software build outcomes. arXiv preprint arXiv:1407.2330.