Software Requirement Specification

Project Title

B.S. in Computer Engineering, Batch 2020F

Project Advisor
Name of Advisor
Designation
SSUET

Submitted By:

Name of Group Member 1 (GL) 2020F-CE-xx

Name of Group Member 2 2020F-CE-xx
Name of Group Member 3 2020F-CE-xx
Name of Group Member 4 2020F-CE-xx

DEPARTMENT OF COMPUTER ENGINEERING

Sir Syed University of Engineering &
Technology University Road Karachi - 75300
May 2024
Contents

1 Software Requirement Specification 1

1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.1 Product Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.2 Product Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.3 System Diagram & Description . . . . . . . . . . . . . . . . . . . . 2
1.1.4 Project Stakeholders . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1.5 Project WBS & Gantt Chart . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Project Functional Requirements . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.1 Project Functional Requirements . . . . . . . . . . . . . . . . . . . 4
1.2.2 Functional Requirement Identification Techniques . . . . . . . . . 5
1.2.3 UX Prototype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3 Project Non-Functional Requirements . . . . . . . . . . . . . . . . . . . . 5
1.3.1 Performance Evaluation . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3.2 Safety Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.3 Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.4 Business Perspective/Requirements . . . . . . . . . . . . . . . . . 7
1.3.5 Licensing Requirements . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3.6 Legal Copyrights & Notices . . . . . . . . . . . . . . . . . . . . . . 7
1.4 Software Design Methodology . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4.1 Data dictionary / Data set . . . . . . . . . . . . . . . . . . . . . . . 8
1.4.2 Design Models [along with descriptions] . . . . . . . . . . . . . . 8

i
1.4.3 Specialized Algorithms (if used)...........................................................8
1.5 External Interfaces Requirements...........................................................................9

ii
List of

1.1 Workplace safety end to end safety compliance system.................................2

1.2 Cab booking process diagram............................................................................2
1.3 Sample Gantt Chart.............................................................................................4
1.4 Sample Gantt Chart.............................................................................................6

i
List of

i
Software Requirement

A software requirements specification (SRS) is a document that describes what the

software will do and how it will be expected to perform. It also describes the
functionality the product needs to fulfill the needs of all stakeholders (business,
users).

1.1 Introduction

1.1.1 Product Purpose

A strong distinct perspective that influences what your company/product does

and doesn’t do. It’s what drives your company forward.

1.1.2 Product Scope

Product scope is about the product details; what the product will look like, how it
will work, its features, and more.It is the result of the project or the solution to the
problem.

In SRS: Use a simple Line-Box-Diagram for simpler systems and detailed

diagrams (Client-Server, Layered, Multi-tiered) for complex systems.

1
Software Requirement

Figure 1.1: Workplace safety end to end safety compliance system

1.1.3 System Diagram & Description

A system diagram is a visual model of a system, its components, and their

interactions.A high-level overview of how the system’s modules collaborate
with each other in order to achieve the desired functionality. In SRS: Use a
simple
Line-Box-Diagram for simpler systems and detailed diagrams (Client-
Server, Layered, Multi-tiered) for complex systems.

Figure 1.2: Cab booking process diagram

2
Software Requirement

1.1.4 Project Stakeholders

Individuals or organizations that are actively involve in the project and can influence
the success of a project in a negative or positive manner.

UPIG: Users, Providers, Influencer, Governance

• Customers Stake: Product/service quality and value

• Employees Stake: Employment income and safety

• Investors Stake: Financial returns

• Suppliers & Vendors Stake: Revenues and safety

• Communities Stake: Health, safety, economic development

• Governments Stake: Taxes and GDP

All web applications and desktop applications should have a real client.
Project Sponser Mention your project sponsor
The default option will be SIR SYED UNIVERSITY oF ENGINEERING & TECHNOLOGY
Mention stakeholders with your roles and responsibilities.
Default options will be
Stakeholder
Students Names
Project Supervisor Name Mr/Miss
Final Year Project Committee

1.1.5 Project WBS & Gantt Chart

It is a deliverable-oriented hierarchical decomposition of the work to be executed by

the project team to accomplish the project objectives and create the required
deliverable. A WBS is the cornerstone of effective project planning, execution,
controlling, monitoring, and reporting.

1.2 Project Functional Requirements

1. Product Functional Features

• Describe the product’s context and origin.

3
Software Requirement

Figure 1.3: Sample Gantt Chart

• Is it the next member of a growing product line, the next version of a mature
system, a replacement for an existing application, or an entirely new product?

2. Operating Environment

• Describe the environment in which the software will operate, which

might include

• Hardware platform

• Operating systems and versions

• locations of users, servers, and databases; and

• Organizations that host the related databases, servers, and websites.

3. Design & Implementation Constraints There are times when a certain

programming language must be used, a code library that has already had
time invested to develop it needs to be used, and so forth.

1.2.1 Project Functional Requirements

All functional requirements which may include calculations, data processing, etc.
are placed in a ranked order.

It is organized by feature as system feature name and specific functional

4
Software Requirement

requirements associated with this feature.

Other organizational options include arranging functional requirements by use

case, process flow, mode of operation, user class, stimulus, and response.

1.2.2 Functional Requirement Identification Techniques

The selection of the technique(s) will depend on the type of project. For

instance,

• Use case is an effective technique for interactive end-user applications.

• Event- response tables is for real time system and

• Story boarding for graphically intensive applications.

1.2.3 UX Prototype

• Provide graphical layout of the UX of the system (frond end and back end).
[if applicable]

• It can be hand drawn but proper tool is recommended.

• The purpose is to provide visualization of how the system should be

available to the user.

• Can create WIREFRAME

1.3 Project Non-Functional Requirements

1.3.1 Performance Evaluation

State specific performance requirements for various system operations.

If different functional requirements or features have different performance

requirements, it’s appropriate to specify those performance goals right with the

5
Software Requirement

Figure 1.4: Sample Gantt Chart

corresponding functional requirements, rather than collecting them in this

section.

1.3.2 Safety Requirements

• Specify those requirements that are concerned with possible loss, damage, or
harm that could result from the use of the product.

• Define any safeguards or actions that must be taken, as well as actions that
must be prevented. Refer to any external policies or regulations that state safety
issues that affect the product’s design or use.

• Any safety certifications that must be satisfied. (Attach it in Appendices)

1.3.3 Security Requirements

• Specify any requirements regarding security or privacy issues surrounding use

of the product or protection of the data used or created by the product.

• Define any user identity authentication requirements. Refer to any external

policies or regulations containing security issues that affect the product.

• Any security or privacy certifications that must be satisfied (Attach it in

Appendices).

6
Software Requirement

1.3.4 Business Perspective/Requirements

1. Target Industry/ Market

A group of employers closely linked by a common product or service,

workforce skills, similar technologies, supply chains, or other economic ties.

2. Competitors Analysis

Identify competitors in your industry and researching their different marketing

strategies.(Uber, Careem)

3. Potential Customers A person who has the potential to be interested in the

services and products that are offered by the company but has not yet
purchased.(Swal)

4. Scalability/ Extensibility The ability of a system to grow to meet a company’s

business needs

1.3.5 Licensing Requirements

Any provisions of law, rule, regulation, or formal order of the department

which apply to facilities with respect to initial or continued authority to
operate.

1.3.6 Legal Copyrights & Notices

A copyright notice is a short line of text that lets the public know that your work
is protected by copyright law and is not to be copied.

1.4 Software Design Methodology

Explain and justify the choice of design methodology being followed. (OOP or
procedural).

Also explain which process model are you following and why.

7
Software Requirement

1.4.1 Data dictionary / Data set

• Alphabetically list the system entities or major data along with their types and
descriptions.

• If you provided a functional description, list all the functions and

function parameters.

• If you provided an OO description, list the objects and its attributes,

methods and method parameters.

1.4.2 Design Models [along with descriptions]

The applicable models may include:

• Use Case Diagram

• Entity Relationship Diagram

• Sequence Diagram

• Schematic diagram (Hardware projects only)

• Timing diagram (Hardware projects only)

1.4.3 Specialized Algorithms (if used)

• In this section, we take a closer look at what each component does in a more
systematic way. Provide a summary of your algorithm for each function
listed in procedural description language (PDL) or pseudo code.

• If you gave an OO description, summarize each object member function for

all the objects listed in PDL or pseudo code. Describe any local data when
necessary.

8
Software Requirement

1.5 External Interfaces Requirements

1. User Interfaces

• Describe the logical characteristics of each interface between the software

product and the users.

• This may include sample screen images, any GUI standards or product
family style guides that are to be followed, screen layout constraints,
standard buttons and functions (e.g., help) that will appear on every screen,
keyboard shortcuts, error message display standards, and so on.

• Define the software components for which a user interface is needed.

2. Hardware Interfaces

• Describe the logical and physical characteristics of each interface between the
software product and the hardware components of the system.

• This may include the supported device types, the nature of the data
and control interactions between the software and the hardware, and
communication protocols to be used.

– Windows

– A browser which supports CGI, HTML & Javascript.

3. Software Interfaces

• Describe the connections between this product and other specific software
components (name and version), including databases, operating systems,
tools, libraries, and integrated commercial components.

4. Communications Interfaces

• Requirements associated with any communications functions required by

this product, including e-mail, web browser, network server communications
protocols, electronic forms, and so on.

9
Software Requirement

• Any pertinent message formatting, communication standards that will

be used, such as FTP or HTTP. Specify any communication security or
encryption issues, data transfer rates, and synchronization mechanisms.