Uploaded by rovor70201

srs sample.docx

advertisement
Software Requirements Specification for SDLC
Submitted To:
Dream Choice
Submitted By:
Your Name (ID N0)
Date of Submission:
15.12.2021
Table of Content
1. Introduction
1.1. Purpose
1.2. Problem statement
1.3. Project Scope
1.4. References
2. Overall Description
2.1 Product features
2.2. User characteristics
2.3 Operating environment
2.4
2.5
Design and implementation constraint
Assumptions and dependencies
3. System features
3.1 Functional requirements
4. External Interface Requirements
4.1 User interfaces
4.2 Hardware Interfaces
4.3 Software Interfaces
4.4 Communication Interfaces
5. Non-functional Requirement
5.1 Usability
5.2 Security
5.3 Performance
5.4 Availability
5.5 Error handling
5.6 Ease of use
1.0 Introduction of Yarl Taxi
Transport is an integral part of our social living. Nowadays, the modern society can’t run
without transport facilities. There are many companies who give transport services to the
individual and corporate customers on occasions like weeding, local long distance
journeys, airport and hotel transfers, meet and great at airport as well as drivers and car
for daily hire. The yarl taxi online booking system is the online service which will automate
the process of booking a taxi and will facilitate both the customer and company with
reduced time and efforts. So, the yarl taxi company has decided to install a new GPS
dispatch system along with the online booking and Mobile App. Therefore, the yarl taxi
company can check it and take appropriate action for the future improvements.
1.1 Purpose
The purpose of this SRS document is to specify software requirements of the major
investment to installing a new GPS dispatch system along with the online booking and
Mobile App. Specific design and implementation details will be specified in a future
document.
1.1.1. Enhance business process
To be able to use Internet Technology to project the yarl Taxi company in SriLanka
instead of limiting their services to their local domain alone, thus increase their
return on investment.
1.1.2. Online booking system
GPS dispatch system through which customers can reserve available drivers or
cars online prior to their expected pick up date or time.
1.1.3. Customer’s registration
A registration portal to hold customer’s details, monitor their transaction and
improve service to them.
1.1.4. Group bookings
Allows the customer to book space for a group in the case of long distance journeys
or corporate meetings.
1.2. Problem Statement
The Yarl taxi company’s call center staffs are getting extremely busy and have to handle
a large number of calls with the whole booking process becoming inefficient and time
consuming. So, they face many difficulties for handling. They have decided to install new
GPS dispatch system along with the online booking and mobile app.
1.3. Product Scope
This project traverses a lot of areas ranging from business concept to be computing
field, and required to perform several researches to be able to achieve the project
objectives. The area covers include:
The yal taxi company: the includes study on how the car online booking is being done,
process involved and opportunity that exist for improvement.
PHP technology used for the development of the application.
General customers as well as the company’s staff will be able to use the system
effectively.
1.4. References

https://www.carbooking.lk/about-us [Accessed 16 Oct. 2019].

https://www.taxi.lk/ [Accessed 16 Oct. 2019].

https://codecanyon.net/category/mobile?term=vehicle%20tracking [Accessed
16 Oct. 2019].
2.0 Overall Description
2.1 Product Perspective
2.1.1
Existing system function
The yarl taxi booking company gives car booking service for customers. This
company carries out its daily work by providing. This company uses a manual
system for booking, register and to keep record of all the booking activities and
customer information. The detailed existing system functions are listed as follows.

During car booking the customers reserve a vehicle by making a phone call to
the company, otherwise company staff is expected to go the company make
booking.

During booking a car the customer personal information, payments status and
rent agreements form in order to hold legal contract between the customer and
company for booking the vehicle.

The company makes a general report about the booked cars once at the end
of the month and generates a report.
2.1.2 Product functionality
The yarl taxi company provides the features for booking a car online. It includes
several functionalities describe as below.

Car booking management
It provides car booking facility online customer can not only visit the website
but also installing the mobile app for checking various cars. If they are feasible
with requirement, then booking can be done.

Checking for availability
Employee can check for the availability of the car. Staff maintains the database
of car. If no any car is available it is the responsibility of the employee to provide
alternative options.

Payment system
Administrator of the applications responsible for payment to the employee order
cancellation, order finalizes, these all activities are done by the administrator of
the application.

Users and characteristics

Admin

Admin can login to the system.

Verify the taxi information database.

Generate price strategy

Handle the payment system.

Finalize the order.

Cancel the account.

Employee

It updates the database.

Give information to the customer about the taxi.

Provides the alternatives.

Maintain contacts.

Maintenance manager

It checks for the maintenance.

Give to the maintenance.

Give information to the admin.

Customer

Customer can login to the system.

Visit the website and Mobile App.

Place the order.

Cancel the order.
2.3 Operating environment
GPS dispatch system

Mobile App.

Online booking system.
2.4
Design and implementation constraints
The application will use Mobile App. Car booking system is a web-based
application, internet connection must be established. The car booking system will
be used on PC and will function via internet in any web browser.
2.5

Assumptions and dependencies
Regularity Policies
Each center user has account created and authenticated by admin. The
website can be accessible within company’s intranet and other user can see
the all the details about booking.

Hardware Limitations
There are no limitations in the operating system in which car booking system
will work. The car booking system and the database will work on a server that
needs to be always online users can access the system with any internet
browser.
3.0 System Features
3.1 Functional requirements
There are statements of service the system should provide, how the system should react
to particular inputs, and how the system should specifies the application functionality that
the developers must build into the product to enable users to accomplish their tasks.

Booking system
The system allows the customer to register for booking.
The system will allow the customer to view detail description of particular taxi.
The system will allow the customers to cancel booking using booking confirmation
number.
The system must be able to display booking summary for successfully committed
booking.

Login in
The system should allow admin to login to the system using their username and
password.
The system should allow employee to login to the system using their username and
password.
4.0 External Interface Requirements
4.1 User Interface
All the users will see the same page when they enter in this website. This page asks
the users a username and a password. The user interface will be simple and
consistence, using commonly understood by intended users of the system. The
system will have simple interface, to eliminate need for user training of infrequent
users.
4.2 Hardware Interface
The system will use the standard hardware and data communication.one of the
main functions of this product is taxi booking, GPS system to find a taxi at any time.
Therefore, the taxi client’s applications must be installed on an android device with
a built-in-GPS. The application used by the customer is to access GPS data to
provide the location of customer ordering the taxi. A GPS can be used to calculate
the speed and similar parameters of a taxi vehicle.
4.3 Software Interface
Following are software used for the GPS dispatch system online application.
Operating system
Database – SQL database / PHP
VB.NET – to implement the project we have chosen VB.Net language for its more
iterative support.
4.4 Communication Interface
GPs dispatch system will communicate with the database that holds all the booking
information users can contact with Mobile App. The customer application must be
connected to the 4G network at all times to send a request to the service and receive
results. The customer receives confirmation from the service by placing customer
application orders; receive orders and responds to them via network connection.
5.0 Non-functional Requirements
Non-functional requirements are requirements that are not directly concerned with
the specific services delivered by the system to its users. They may relate to
developing system properties such as reliability, response, time and store
occupancy. Non-functional requirements such as performance, security, or
availability, usually specify or constrain characteristics of the system as a whole.

Usability
The system provides support menu in all interfaces for the user to interact with the
system. The user can use the system by reading help and support.

Security
The system provides username and password to prevent the system from
unauthorized access.

Performance
The system response time for every instruction conducted by the user must not
exceed more than a minimum of 10 second. The system should have high
performance rate when executing user’s input and should be able to provide
response within a short time.

Availability
The system should be available for 24 hours, 7 days a week.

Error handling
Error should be considerably minimized and a n appropriate error message that
guides the user to recover from an error should be provided.

Ease of use
The users of this system is considered the level of knowledge, a simple but quality
user interface should be developed to make it easy to understand and required
less training.
Download