Group member names:

Husnain Haider(70067977)
Shahid(70068107)
Usman(70067897)
Taimoor Sarwar(7006898)
Subject:Objected Oriented Software
Submitted to:Sir Hassan
Assingemnt no:3
………………………………………………………………………………………………………………
<Sale management System>
Table of Contents REVISION HISTORY........................................................................... ERROR!
BOOKMARK NOT DEFINED. DOCUMENT
APPROVAL.................................................................... ERROR! BOOKMARK NOT DEFINED. 3.
SPECIFIC
REQUIREMENTS.........................................................................................................................
2 3.1 EXTERNAL INTERFACE REQUIREMENTS ....................................................ERROR!
BOOKMARK NOT DEFINED. 3.1.1 User
Interfaces........................................................................................Error! Bookmark not
defined. 3.1.2 Hardware Interfaces................................................................................Error!
Bookmark not defined. 3.1.3 Software
Interfaces..................................................................................Error! Bookmark not defined.
3.1.4 Communications Interfaces......................................................................Error!
Bookmark not defined. 3.2 FUNCTIONAL
REQUIREMENTS...................................................................ERROR! BOOKMARK NOT
DEFINED. 3.2.1 ................................................Error! Bookmark not defined. 3.2.2
................................................Error! Bookmark not defined. 3.3 USE CASES
..............................................................................................ERROR! BOOKMARK NOT
DEFINED. 3.3.1 Use Case #1.............................................................................................Error!
Bookmark not defined. 3.3.2 Use Case
#2.............................................................................................Error! Bookmark not defined.
3.4 CLASSES / OBJECTS..................................................................................ERROR!
BOOKMARK NOT DEFINED. 3.4.1 ................................................................................Error!
Bookmark not defined. 3.4.2 ................................................................................Error!
Bookmark not defined. 3.5 NON-FUNCTIONAL REQUIREMENTS
..........................................................ERROR! BOOKMARK NOT DEFINED. 3.5.1
Performance............................................................................................Error! Bookmark not
defined. 3.5.2 Reliability................................................................................................Error!
Bookmark not defined. 3.5.3 Availability
..............................................................................................Error! Bookmark not defined.
3.5.4 Security ...................................................................................................Error! Bookmark
not defined. 3.5.5 Maintainability
........................................................................................Error! Bookmark not defined. 3.5.6
Portability ...............................................................................................Error! Bookmark not
defined. 3.6 INVERSE REQUIREMENTS..........................................................................ERROR!
BOOKMARK NOT DEFINED. 3.7 DESIGN CONSTRAINTS
.............................................................................ERROR! BOOKMARK NOT DEFINED. 3.8
LOGICAL DATABASE REQUIREMENTS .......................................................ERROR! BOOKMARK
NOT DEFINED.
3.9 OTHER REQUIREMENTS ............................................................................ERROR!
BOOKMARK NOT
Software Requirements Specification

3. Specific Requirements
External Interface Requirements
User Interfaces
We aim to provide simple and interactive interference to all the system users Software
Interface
• IOS 7.0 or above
• ANDROID 8.0 or above
• WINDOWS 7/8/10
Hardware interface
No special hardware is required for this application. A standard PC, smartphone with
following processing power is more than enough for the requires operations of the system.
• Minimum 256 MB RAM
• Minimum required memory 1 GB
Communications Interfaces
Client on Internet will be using HTTP/HTTPS Protocol and Client on intranet will be using
TCP/IP protocol.
Functional Requirements
Administrator Aspect
• Perform weekly roster of Employees
• Print reports annually, weekly, and daily
• Check feedbacks • Send newsletters
• Manage user portfolio
• Changing the super password
Employee Aspect
• Logging into the system.
• To check their rosters.
• Maintain daily logs
• Select availability.
• Check online bookings
Client Aspect:
• Make a booking
• Check their booking status
• Fair calculation
• Driver history
• Changing password.
• Resetting of forgotten password.
Software Requirements Specification

<Sale management system>

Use Case diagram:
Software Requirements Specification

<Sale Management System>

Use Case #1
Use Case ID: 1
Use Case Name: Sign up
Date Created: 9 April ,2021.
Actors: Customer of sale
Description: Customer needs to be registered to be able to book any ride. A customer
will need to be registered only once. He will provide basic some basic
information like name, phone number, email, password. Only one
account will be created against each phone number.

Preconditions: 1. Customer should download the application.

2. The customer should create an account by clicking on sign up button.
Post conditions: 1. System must have added the record of the customer in the database.

Normal Flow:
Customer System
1. System will prompt the
customer to enter basic
information
2. Customer will enter the basic
information
3. System will verify that the
entered phone number in
the database
 4. System will prompt the
customer to set a new
password and verify
password.
5. The customer will enter a new
password and will re-enter it
6. If both entered passwords
match and satisfy password
requirements then create an
account for the customer
Alternative Flows:

Exceptions: Phone Number already registered

Ask the user to login or recover password

Passwords do not match

Ask the user to retype passwords

Password does not satisfy password requirements

Ask the user to enter minimum 8 characters with at
least 1 numerical digit.

Use Case #2
Use Case ID: 2
Use Case Name: Login
Date Created: 9 April ,2021.
Actors: Customer and User.
Description: Customer or user needs to be logged in before booking any sale product
for buy. The customer will need to add the phone number and password
to login systematically.
Preconditions: 1. Customer should have opened the application to check their sales
review.
2. The customer should click on login to open the application by
verifaction of user.
Post conditions: 1. The customer should be logged in system

Normal Flow:
Customer System
 1. System will prompt the
customer or user to enter
phone number and key
password
2. Customer will enter his phone
number and password
3. System will authenticate the
User for verify.
4. System will display a
welcome message to the
customer to validate
their product.
Alternative Flows:
Exceptions: 2.1 User not authenticated
Ask the user to re-enter phone number and password

Use Case #3
Use Case ID: 3
Use Case Name: Supplier record system
Date Created: 9 April ,2021.
Actors: Customer and manager
Description: The customer should have supply their items by login in their system
Or supply the prouducts very clear with reports.
Preconditions: 1.Customer should have opened application.
2. The customer should have opened their website and should have
requested to check their record system.
Post conditions: 1.

Normal Flow:
Customer System
1. System will prompt the
customer to enter current supplier
 record
2. Customer will enter the current
details and saling
products.
3. System will check the
availability of the record at
that time.
4. System will display the all
record details.
Alternative Flows: 3.1 User wants to search for other record
Return to back step of search.

Exceptions: 3.2 No record found

Display the user that no record are available currently.

Use Case #4

Use Case ID: 4

Use Case Name: Employee record
Date Created: 9 April ,2021.
Actors: Customer and user
Description: Employer should login first and check the records of clients that buy products.
Manage the record system by employee is basic part of saling.
Preconditions: 1. Customer should have opened the application
2. Customer should be logged in to the application
3. Customer should click on the choose the record to be checked
Post conditions: 1. Employer has searching for the good services in records and get the services
for next clients..
Normal Flow:
Customer System
1. System will prompt the
customer to choose the
record of employee.
2. Customer will select it’s record
from the menu to check their
product
3. System will check that record is
available or not.

4. System will display the data of

all record if it is on database.
Alternative Flows: 4.1 User wants to choose the record
Return to back step

Exceptions: 4.2 No record found

Display the user that the record is not available

Use Case #5
Use Case ID: 5
Use Case Name: Stocks record system
Date Created: 9 April ,2021.
Actors: Customer and user of stocker.
Description: Customer should display the name of real and beneficial owner the number of
shares and record is updated every time trade is executed.

Preconditions: 1. Customer should have opened the application

2. Customer should be logged into the system
3. Customer should check fare details of stock system.
Post conditions: 1. It has check their stocks rates in market then for the service and get the good
result.
Normal Flow:
Customer System
1. System will display the fare
details of stocks rates.
2. Customer will select the rate
Of stocks in purchase market.
3. System will confirm that their
Product of stock to be approved.

Alternative Flows: 5.1 User wants search again

Return to back step

Exceptions: 5.2 Customer maybe cancel the Stocks system

Add fine to the customer on his/her account after not arrival.
 Use Case #6
Use Case ID: 6
Use Case Name: Sale generation Details
Date Created: 9 April ,2021.
Actors: Customer or saleman.
Description: The customer should write their sale requirements that easy to sale
Their products.

Preconditions: 1. Customer should have opened the application

2. Customer should be logged into the system
3. Customer should check fare details of saling system.
Post conditions: 1. It has check their sale rates in market then for the service and get the good
result.
Normal Flow:
Customer System
1. System will display the fare
details of every sale system
2. Customer will select it to be
Sale product details
3. System will confirm that their
Product of saling requirements to
be approved
Alternative Flows: 5.1 User wants search again
Return to back step

Exceptions: 5.2 Customer maybe cancel the Details

Add fine to the customer on his saling details or record system.

Use Case #7
Use Case ID: 7
Use Case Name: Advertising and marketing research of sale.
Date Created: 9 April ,2021.
Actors: Customer and saler
Description: Customer will check the fare details of all marketing of products to be
saled and then choose one for advertising to be more perfect.

Preconditions: 1. Customer should have opened the application

2. Customer should be logged into the system
3. Customer should check fare details.
Post conditions: 1. It has check their sale rates in market then for the service and get the good
result.
 Normal Flow:
Customer System
1. System will display the fare
details of marketing price
and advertisement
2. Customer will select a
marketing research to be sale best
3. System will confirm that the
Advertisement of sale to be
perfect or not
Alternative Flows: 5.1 User wants search again
Return to back step in marketing

Exceptions: 5.2 Customer maybe cancel the Research of marketing

Add fine to the customer on making research .

Use Case #8
Use Case ID: 8
Use Case Name: Welfare and health facilities of sale products.
Date Created: 8 April,2021.
Actors: Customer and Welfare manager.
Description: Customer will check the Welfare facilities that available to other
For usage in sale products that get benefits.

Preconditions: 1. Customer should have opened the application

2. Customer should be logged into the system
3. Customer should check fare details
Post conditions: 1. Price may be change due to some conditions of sale products to be
Change by facilities changes
Normal Flow:
Customer System
1. System will display the fare
details of health facilities that
give to sale products easily
for sale
2. Customer will select all the sale
products for welfare facilities
 3. System will confirm that
Welfare facilities easy to use to
Sale product or not.
Alternative Flows: 5.1 User wants search again
Return to back step

Exceptions: 5.2 Customer maybe cancel the Prouct or facilities

Add fine to the customer on his/her facilities available by sale product

.4 Classes / Objects
3.4.1 <Class / Object #1>

3.4.1.1 Attributes
3.4.1.2 Functions
<Reference to functional requirements and/or use cases>
3.4.2 <Class / Object #2

3.5 Non-Functional Requirements

Non-functional requirements may exist for the following attributes. Often these requirements must be
achieved at a system-wide level rather than at a unit level. State the requirements in the following sections in
measurable terms (e.g., 95% of transaction shall be processed in less than a second, system downtime may
not exceed 1 minute per day, > 30 day MTBF value, etc).
3.5.1 Performance
3.5.2 Reliability
3.5.3 Availability
3.5.4 Security
3.5.5 Maintainability
3.5.6 Portability
3.6 Inverse Requirements
State any *useful* inverse requirements.
3.7 Design Constraints
Specify design constrains imposed by other standards, company policies, hardware limitation, etc. that will
impact this software project.
3.8 Logical Database Requirements
Will a database be used? If so, what logical requirements exist for data formats, storage capabilities, data
retention, data integrity, etc.
3.9 Other Requirements
Catchall section for any additional requirements.