Professional Documents
Culture Documents
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:
Reliability:
All data storage for user variables will be committed to the database at the time of entry.
techniques.
Maintainability
The user will be able to reset all options and all stored user variables to default settings
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.
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:
Class:
Ride
Attributes:
Reference number: Reference number
Driver details: Driver details
b)
Question#03: