Scribd
Upload
74 views4 pages

Functional Requirements:: Question#01

The document outlines functional and non-functional requirements for a ride-sharing application, including requirements that allow administrators to manage drivers and print reports, drivers to view schedules and accept bookings, and customers to make bookings and check statuses. Performance requirements specify supporting a minimum of 10,000 records and multiple concurrent users. Security, reliability, and maintainability requirements are also described along with some design constraints.

Uploaded by

Muhammad Hamza
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
74 views4 pages

Functional Requirements:: Question#01

The document outlines functional and non-functional requirements for a ride-sharing application, including requirements that allow administrators to manage drivers and print reports, drivers to view schedules and accept bookings, and customers to make bookings and check statuses. Performance requirements specify supporting a minimum of 10,000 records and multiple concurrent users. Security, reliability, and maintainability requirements are also described along with some design constraints.

Uploaded by

Muhammad Hamza
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Question#01:

FUNCTIONAL REQUIREMENTS:
 Administrator should Perform weekly roster of drivers
 Administrator should Print reports annually, weekly, and daily
 Administrator should check system reviews the driver rating and feedback and record the
follow up action taken.
 Gift card can be used to offset customer bill.
 Administrator can Check feedbacks
 Administrator can Send newsletters
 Administrator will Manage user portfolio
 Administrator will be able to Changing the super password.
 Driver can Login into the system.
 Driver will check their rosters.
 Maintain daily logs
 Driver will select their availability.
 Driver will Check online bookings
 Customer will Make a booking
 Customer can Check their booking status
 Customer will check Fair calculation
 Customer can check Driver history
 Customer can Change their password.
 Customer can reset of forgotten password.

Non-FUNCTIONAL REQUIREMENTS:
Performance:

 The database shall be able to accommodate a minimum of 10,000 records of customers.

 The software shall support use of multiple users at a time


Security:

 Check data integrity for critical variables

 System Restrict communications between some areas of the program

 Communication will be restricted when the application is validating the user


 System will Keep specific log or history data sets

Reliability:
 All data storage for user variables will be committed to the database at the time of entry.

 Data corruption is prevented by applying the possible backup procedures and

techniques.

Maintainability

 The user will be able to reset all options and all stored user variables to default settings

Design and Implementation Constraints

Some of the design and implementation constraints identified are listed below:

 Clients or employees do not have any rights to edit any data in the system.

 Online Payment facility may be restricted if the Company not want this facility for some

reasons.

 This system is not support distributed database Facility.

 System is limited to HTTP/HTTPS Protocols.

B.
Now user requirements are clear, complete and consistent.
 Administrator should check system reviews the driver rating and feedback and record the
follow up action taken.
Now this functional requirement is complete because here everything is described that admin can
check reviews, feedback of user and records to take the actions.

Question#02:

a):
Class:
Driver

Attributes:
Name: name of the driver
Contact number: contact number of driver
Email: email of driver
Identification number: Identification number of driver
Bank name: Bank name of driver
Vehicle detail: vehicle detail of driver

Class:
Customer

Attributes:
Name: name of the customer
Contact number: contact number of customer
Email: email of customer
Identification number: Identification number of customer

Class:
Vehicle

Attributes:

License number: License number of vehicle


Brand: Brand of vehicle
Model: Model of vehicle

Class:
Ride

Attributes:
Reference number: Reference number
Driver details: Driver details

Customer details: Customer details


Pick point: Pick point of customers
Distance: Distance of trip
Date: Date of booking
Start time: Start time of trip
End time: End time of trip

b)
Question#03:

You might also like