Faculty of Engineering

And Information Technology

Module: Software Design Course

SRS of
[Human Resource System for Small
Business]

By:

Ahmad Yasser Abo Aisha 20192851

Submitted to:
Eng. Haya Abed

1
Project overview:
Ahmed's delivery app is a mobile application that aims to help people to
order the office easily the application has a simple user interface so that
the user can take full advantage of the screen space. The application
works on two systems: Android and iOS, and does not require a
permanent connection to the Internet.
Why is necessary?
1. Gives the administrator control of his office and his drivers.
2. Manage drivers to keep in touch with the office and monitor the
available orders.
3. Manage the users to order easily.
Goals:
1- Make the process easier.
2- Manage the orders from different resources.
3- Make the process cheaper.
Challenges:
• Misusing the app by users.
Resource estimate:

• Location for monitoring the process.

• Mobile application developer.

• UI/UX Designer.
• A computer that meets the required specifications.
• Energy source.
• Internet connection.
• Cloud storage services.

2
Schedule:
Tasks\ time (week) 1 2 3 4 5 6 7 8 9 10 11 12
Planning
Design
Templates and layout design
Implementation
Test
Maintenance
Total 3 Months

Budget:
The estimated total cost is $1000, Financial returns are obtained via
• Use of in-app ads
• Providing the subscription feature for a small fee
• Budget for running cost.

Current situation:
The delivery offices face a problem in controlling their drivers and orders
and drivers face a problem in communication between users and
administrators, also it's hard for users to make an order.
Objective:
This app will provide us the possibility to receive multi orders at the same
time without overlapping between orders and give the users and
administrators to keep in touch with drivers and monitoring his location.

Features that the application will support:

1. The application supports Android and iOS.
2. The application gives delivery offices the ability to create accounts.
3. The application saves the orders created by the users.
4. The ability to make the drivers to be in touch with their offices.
5. The app does not require a permanent connection to the Internet.

3
Functional Requirements:
Users:
RQ1.01: The system shall allow the user to sign up.
RQ1.02: The system shall verify user sign up.
RQ1.03: The system shall allow the user to sign in.
RQ1.04: The system shall allow the user to reset his/her password.
RQ1.05: The system shall allow the user to choose his destination.
RQ1.06: The system shall allow the user to choose the nearest driver.
RQ1.07: The system shall allow the user to know the time for driver coming.
RQ1.08: The system shall allow the user to get message when driver reach him.
RQ1.09: The system shall allow the users to communicate with office when
problems occur.
RQ1.09: The system shall allow the user to know price order.
RQ1.10: The system shall allow the user to pay by the app or cash.
RQ1.11: The system shall allow the user to write feedback about the service.
RQ1.12: The system shall allow the user to rate the app and drivers.
RQ1.13: The system shall allow the users to cancel the order when driver is late.

Drivers:
RQ1.01: The system shall allow the driver to sign up.
RQ1.02: The system shall verify drive sign up.
RQ1.03: The system shall allow the driver to sign in.
RQ1.04: The system shall allow the driver to show available orders.
RQ1.05: The system shall allow the driver to verify his location.
RQ1.06: The system shall allow the driver to communicate with users.
RQ1.07: The system shall allow the driver to communicate with administrator.
RQ1.08: The system shall allow the driver to check when he receives the order.
RQ1.09: The system shall allow the driver to check when he delivers the order.
RQ1.10: The system shall allow the driver to pay fees for office.

4
Administrator:
RQ1.01: The system shall allow the administrator to make an account.
RQ1.02: The system shall allow the administrator to sign in.
RQ1.03: The system shall allow the administrator to a list of his driver.
RQ1.04: The system shall allow the administrator to add new drivers to his list.
RQ1.05: The system shall allow the administrator to remove drivers to his list.
RQ1.06: The system shall allow the administrator to monitor his driver's location by
google maps.
RQ1.07: The system shall allow the administrator to communicate with his drivers.
RQ1.08: The system shall allow the administrator to get list with total orders per
day.
RQ1.09: The system shall allow the administrator to get his fees from drivers.

Use Cases:
Name Register and sign in UC-1
RQ1.01 to RQ1.04
Actor User
Description The system shall allow user to create account and sign in
Precondition Create an account.
Basics Flow -user will enter his information
-user confirm his/her register.

Alternative flow -
Postcondition -user will sign in.

Name Communication with driver UC-2

RQ1.05 to RQ1.09
Actor User
Description The system shall allow user to communicate and get info about driver
Precondition Choosing the destination.
Basics Flow -user will enter his destination.
-user will show drive's location by app.

Alternative flow - user contact with office to send him/her driver.

Postcondition -user will give the driver the order.

5
Name Paying for driver UC-3
RQ1.10 & RQ1.11
Actor User
Description The system shall allow user to pay for driver.
Precondition Send message with coast.
Basics Flow -user will choose payment page.
-user choose the way for paying.

Alternative flow -
Postcondition -

Name Feedback and rating UC-4

RQ1.12, RQ1.13, RQ1.14
Actor User
Description The system shall allow user to rate app and drivers.
Precondition Choose feedback place
Basics Flow -user will write feedback about service.
-user will rate the app.

Alternative flow - calling the office when a big problem occurs.

Postcondition -exhibit message to thank user.

Name Register and sign in UC-5

RQ1.01 to RQ1.03
Actor driver
Description The system shall allow driver to create account and sign in
Precondition Create an account.
Basics Flow -driver will enter his information
-drive confirm his/her register.

Alternative flow -
Postcondition -driver will sign in.

6
Name Receive the order UC-6
RQ1.01 to RQ1.0
Actor driver
Description The system shall allow driver to receive order
Precondition Monitor the available orders
Basics Flow -driver will choose the nearest order.
-driver will receive the order.

Alternative flow - driver will contact with office to send another driver if he can't reach
the user.
Postcondition -driver will deliver the order.

Name Paying fees. UC-7

RQ1.10
Actor driver
Description The system shall allow driver to pay fees for office.
Precondition Driver will see the total fees per day
Basics Flow -driver will choose the way for pay.
-

Alternative flow
Postcondition -the fees will enter office account.

Name Register and sign in UC-8

RQ1.01 , RQ1.02
Actor administrator
Description The system shall allow administrator to create account and sign in
Precondition Create an account.
Basics Flow - administrator will enter his information
- administrator confirms register.

Alternative flow -
Postcondition - administrator will sign in.

Name Preparing the list of drivers UC-9

RQ1.03 to RQ1.05
Actor administrator
Description The system shall allow administrator to create a list with drivers.
Precondition Create a list.
Basics Flow - administrator will add drivers.
- administrator confirms the list.

Alternative flow -
Postcondition - administrator list is ready.

7
Name Monitoring the drivers UC-10
RQ1.05 to RQ1.07
Actor administrator
Description The system shall allow administrator to monitor drivers and keep in
contact with them.
Precondition Administrator following up the available drivers.
Basics Flow - administrator will open map to monitor drivers' locations.

Alternative flow - calling drivers when app when problem occurs.

Postcondition