Software Requirements

Specification
for

Shipping Compony
Version 1.0 approved

Prepared by :

Amr Nasser 42110370

Akram Hatem 42110113

Yasmin Reda 42110133

Mustafa Mahmoud 42110114

Moaaz Hossam 42110042

Mahmoud Raafat 42110309

Soudy Shipping

12 – 3 – 2023

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ........................................................................................................................... iii
1. Introduction ..............................................................................................................................1
1.1 Purpose ........................................................................................................................................ 1
1.2 Product Scope .............................................................................................................................. 1
1.3 References.................................................................................................................................... 1
2. Overall Description ..................................................................................................................1
2.1 Product Functions ....................................................................................................................... 1
2.2 User Classes and Characteristics................................................................................................ 2
2.3 Operating Environment ............................................................................................................... 2
2.4 Assumptions and Dependencies................................................................................................... 2
3. System Functions .....................................................................................................................2
3.1 Register Employee ....................................................................................................................... 2
3.2 Register Customer ....................................................................................................................... 3
3.3 Log in Employee .......................................................................................................................... 3
3.4 Log in Customer .......................................................................................................................... 3
3.5 Log out ......................................................................................................................................... 3
3.6 Record Attendance....................................................................................................................... 3
3.7 Absence ........................................................................................................................................ 3
3.8 Collecting bills............................................................................................................................. 4
3.9 Paying salaries ............................................................................................................................ 4
3.10 Maintenance ................................................................................................................................. 4
3.11 Compensation .............................................................................................................................. 4
3.12 The Reports.................................................................................................................................. 4
3.13 Create order ................................................................................................................................ 5
3.14 Edit order..................................................................................................................................... 5
3.15 Shipping Status ............................................................................................................................ 5
3.16 Cancel order ................................................................................................................................ 5
3.17 Track order .................................................................................................................................. 5
3.18 The Returner ................................................................................................................................ 6
3.19 Review customers ........................................................................................................................ 6
3.20 Best Customers ............................................................................................................................ 6
3.21 Generate coupons ........................................................................................................................ 6
3.22 Lost password .............................................................................................................................. 6
3.23 Contact us .................................................................................................................................... 6
3.24 Help ............................................................................................................................................. 7
3.25 Purchase History ......................................................................................................................... 7
3.26 Update Account Information ....................................................................................................... 7
3.27 Locations ..................................................................................................................................... 7
3.28 About Us ...................................................................................................................................... 8
3.29 Rating .......................................................................................................................................... 8
3.30 Staff .............................................................................................................................................. 8
3.31 Engagements................................................................................................................................ 8
4. Nonfunctional Requirements ..................................................................................................8
4.1 Performance ................................................................................................................................ 8
4.2 Security ........................................................................................................................................ 9
4.3 Scalability .................................................................................................................................... 9
4.4 Availability .................................................................................................................................. 9
4.5 Usability ...................................................................................................................................... 9
4.6 Maintainability ........................................................................................................................... 9
4.7 Reliability .................................................................................................................................... 9
4.8 Compliance .................................................................................................................................. 9
4.9 Portability .................................................................................................................................. 10
 Software Requirements Specification for <Project> Page iii

Revision History
Name Date Reason For Changes Version
Eng. Ahmed Kamal 13/3/2023 Errors in the order of functional and non- functional 1.0
Software Requirements Specification for <Project> Page 1

1. Introduction

1.1 Purpose
A shipping company operates manually and has a problem. This is the purpose of my system to
help it facilitate and speed up work and have a reference for each job with the details of customers,
employees and companies that deal with it, in addition to paying attention to the accounts
department to prevent theft or financial errors. The system helps reduce the number of account
employees based on the customer’s request.

1.2 Product Scope

The Shipping Company SRS will be a web-based software application that aims to streamline and
optimize the shipping process for the company's clients. The software will be designed to meet the
needs of both small and large businesses that need to ship goods domestically.

1.3 References

https://www.studocu.com/row/document/national-institute-of-technology-
rourkela/software-engineering/srs-for-transport-company-computerization/46399884

https://visuresolutions.com/requirements-management-traceability-guide/non-
functional-requirements

2. Overall Description

2.1 Product Functions

 Register Employee
 Register Customer
 Log in Employee
 Log in Customer
 Log out
 Record Attendance
 Absence
 Collecting bills
 Paying salaries
 Maintenance
 Compensation
 The Reports
 Create order
 Edit order
 Shipping Status
Software Requirements Specification for <Project> Page 2

 Cancel order
 Track order
 The Returner
 Review customers
 Best Customers
 Generate coupons
 Lost password
 Contact us
 Help
 Purchase History
 Update Account Information
 Locations
 About Us
 Rating
 Staff

2.2 User Classes and Characteristics

 Employee : Enter data and details about orders
 Customer : Create order and tracking orders
 Administrator : He can view the financial exports and imports in an organized and clear
manner

2.3 Operating Environment

The system will work on any device that has internet connectivity and browser to browse the
website. The browser should be up to date to run various functions of the website. The system will
not run on any OS under windows XP. The system will not also run on browsers doesn’t support
JAVA plugins

2.4 Assumptions and Dependencies

 Customer can track and create orders
 Employees have higher features as enter data , view details , review requests

3. System Functions

3.1 Register Employee

Code Requirements statement Must/should Comments
FR001 The system shall allow to register new Must
employee given his name, email, phone,
address, gender, ID and password
FR002 The System will confirm the username Must
and password are acceptable
FR003 The System will store the information Must
in the database
Software Requirements Specification for <Project> Page 3

3.2 Register Customer

Code Requirements statement Must/should Comments
FR004 The system shall allow to register new Must
customer given his name, email, phone,
address, gender and password
FR005 The System will confirm the username Must
and password are acceptable
FR006 The System will store the information Must
in the database

3.3 Log in Employee

Code Requirements statement Must/should Comments
FR007 The system shall allow log in Must
employee given his username,
password, ID and check validation

3.4 Log in Customer

Code Requirements statement Must/should Comments
FR008 The system shall allow log in Must
employee given his username,
password and check validation

3.5 Log out

Code Requirements statement Must/should Comments
FR009 Ask user want to log out Must Print "Log out
of your account"
Click (CANSEL
or LOG OUT)
FR010 The system will allow the user to exit Must
their account
FR011 The system will Prevent others from Must
accessing to it

3.6 Record Attendance

Code Requirements statement Must/should Comments
FR012 The system shall allow record attend Must
employee taking his finger print until
8:30 AM after that time don't accept
his finger print

3.7 Absence
Code Requirements statement Must/should Comments
Software Requirements Specification for <Project> Page 4

FR013 The system allow employee to upload Must

his exception
FR014 If the excuse is accepted, the absence Must
will be cancelled

3.8 Collecting bills

Code Requirements statement Must/should Comments
FR015 The system shall allow record bills Must
given policy number, delegate name,
and the amount

3.9 Paying salaries

Code Requirements statement Must/ should Comments
FR016 The manager will be able to set the Must
salary of every employ
The manager will be able to modify Must
the salary of the employees
FR017 Transfer the amount to employee Must
accounts

3.10 Maintenance
Code Requirements statement Must/ should Comments
FR018 The system shall allow driver request Must
maintenance given truck number,
driver name and reason
FR019 The system shall cashed cost of truck Must
maintenance

3.11 Compensation
Code Requirements statement Must/ should Comments
FR020 The system will record any order Must
damaged given delegate name, cause
of spoilage, order ID
FR021 The system will compensation any Must
order damaged pay 70 pounds

3.12 The Reports

Code Requirements statement Must/ should Comments
FR022 The system shall display to manager Must
number of orders per each day,
month and year
FR023 The system shall display to manager Must Total
revenue per each day, month and year amount of
bills
Software Requirements Specification for <Project> Page 5

FR024 The system shall display expense to Must Salaries +

manager and details Maintenance +
Compensation
FR025 The system shall display to manager Must Total –
total revenue after subtract expense (Salaries +
from revenue Maintenance +
Compensation)
FR026 The system will notify the owner of Must
the money of every quarter
FR027 It will provide the owner with the Must
profit he made

3.13 Create order

Code Requirements statement Must/ should Comments
FR028 The system shall allow logged in user Must
create order given packaging type,
pick-up point, destination, shipping
type and date and time

3.14 Edit order

Code Requirements statement Must/ should Comments
FR029 The system shall allow logged in user Must
edit his order given ID of order

3.15 Shipping Status

Code Requirements statement Must/want Comments

FR030 The system will allow a logged -in Must
user to see the shipping status of the
orders they placed until order arriving
FR031 The system shall send mail to user Must
after each change on order

3.16 Cancel order

Code Requirements statement Must/ should Comments
FR032 The system shall allow logged in user Must
cancel his order given ID of order and
reason for cancelation

3.17 Track order

Code Requirements statement Must/ should Comments
Software Requirements Specification for <Project> Page 6

FR033 The system shall allow logged in user Must

to track their order through the
delegate's tracking by location

3.18 The Returner

Code Requirements statement Must/ should Comments
FR034 The system shall allow logged in user Must
to return their order given reason

3.19 Review customers

Code Requirements statement Must/want Comments
FR035 Should allow the user to write a about Must
a shipping
FR036 Should allow the user to write a Must
review about our staff

3.20 Best Customers

Code Requirements statement Must/ should Comments
FR037 The system must count number of Must
orders for each user

3.21 Generate coupons

Code Requirements statement Must/ should Comments
FR038 The system must generate coupons for Must
users have number of orders greater
than 10 per month

3.22 Lost password

Code Requirements statement Must/Want Comments

FR039 The system will ask for the user’s Must
email
FR040 The system will send a message to the Must
user’s email that has a link to change
his password

3.23 Contact us

Code Requirements statement Must/want Comments

FR041 The system will provide many ways to Must
contact the company
Software Requirements Specification for <Project> Page 7

FR042 The system will display the company’s Must

number, address and email
FR043 The system will display a map Must
showing the location of the company

3.24 Help

Code Requirements statement Must/should Comments

FR044 The help function shall give the Must
user an overview of how to use
the different functions listed above
FR045 Should show how to use the method Must
above

3.25 Purchase History

Code Requirements statement Must/want Comments

FR046 The system will allow the user to see Must
the last purchase made with their
account within the last year
FR047 The system will display the date of Must
purchase, credit card type, credit card
number
FR048 The system will display information Must
about the shipping operations

3.26 Update Account Information

Code Requirements statement Must/want Comments

FR049 The system will allow the user to Must
update their account information
(name, address, credit card number,
password, etc.)
FR050 The user will be able to change the Must
password by entering the old password
once and the new one twice

3.27 Locations

Code Requirements statement Must/want Comments

FR051 Should Show the user our Branches Must
FR052 Should show the user the places we Must
deliver to
Software Requirements Specification for <Project> Page 8

3.28 About Us

Code Requirements statement Must/want Comments

FR053 Should allow the user to read about Must
our philosophy
FR054 Should allow the user to see who Must
founded the business
FR055 Should allow the user to see since Must
when we established

3.29 Rating

Code Requirements statement Must/want Comments

FR056 Should allow the user to give a book Must 1 for very bad
from 1 star to 5
5 for excellent

3.30 Staff

Code Requirements statement Must/should Comments

FR057 The system will provide information Must
about the staff
FR058 It will tell the user every branch staff Must
and its manager

3.31 Engagements

Code Requirements statement Must/should Comments

FR059 The system must allow contracting Must
with companies after verifying the
commercial register and the tax card

4. Nonfunctional Requirements

4.1 Performance
Code Requirements statement Must/should Comments
NR001 The system must respond the MUST
operation in less than 3 seconds for
user
Software Requirements Specification for <Project> Page 9

4.2 Security
Code Requirements statement Must/should Comments
NR003 The system must be secure from MUST
unauthorized access

4.3 Scalability
Code Requirements statement Must/should Comments
NR004 The system must be able to scale up MUST
or down as needed.

4.4 Availability
Code Requirements statement Must/should Comments
NR005 The system must be available 24h MUST

4.5 Usability
Code Requirements statement Must/should Comments
NR006 The system should have user friendly MUST
interface must create order maximum
3 clicks
NR007 The system must be ease of use
and understandability of the
system for the end-users

4.6 Maintainability
Code Requirements statement Must/should Comments
NR008 The system must be ease of MUST
maintaining the system,
including testing, debugging,
and modifying the system.

4.7 Reliability
Code Requirements statement Must/should Comments
NR009 The system must be reliable and meet MUST
the requirements of the user.

4.8 Compliance
Code Requirements statement Must/should Comments
NR010 The system must comply with all MUST
applicable laws and regulations.
Software Requirements Specification for <Project> Page 10

4.9 Portability
Code Requirements statement Must/should Comments
NR011 The system to be easily MUST
transferred to different hardware
or software environments

5. Diagrams

5.1 Data-Flow Diagram (DFD)

5.2 Entity-Relationship Diagram (ERD)