SOFTWARE REQUIREMENTS

SPECIFICATION

For

<Project Name>

Version 1.0

Prepared by Group #

Supervised By:

Software Engineering Department

Sir Syed University of Engineering & Technology

July 22, 2022

1
Contents
1 Introduction 4
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 Definition, Acronyms and Abbreviations . . . . . . . . . . . . . . . . . . 4
1.4 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Project Planning and Management 5

2.1 SWOT Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Gantt Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.3 Work Breakdown Structure[WBS] . . . . . . . . . . . . . . . . . . . . . 5
2.4 Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3 Overall Description of Product 6

3.1 Product Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2 Product Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.3 User Classes and Characteristics . . . . . . . . . . . . . . . . . . . . . . 6
3.4 Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.5 Design and Implementation Constraints . . . . . . . . . . . . . . . . . . 6
3.6 User Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.7 Assumptions and Dependencies . . . . . . . . . . . . . . . . . . . . . . . 6

4 Functional Requirements 7
4.1 Domain Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2 Project Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2.1 Web / Android / Game Module . . . . . . . . . . . . . . . . . . 7
4.2.1.1 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2.1.2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2.2 Database Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.2.3 Administration Module . . . . . . . . . . . . . . . . . . . . . . . 7
4.3 System Analysis & Design Overview . . . . . . . . . . . . . . . . . . . . 7
4.3.1 Object Oriented Modeling Technique . . . . . . . . . . . . . . . . 7
4.3.1.1 Functional Model: Use Case Diagram . . . . . . . . . . 7
4.3.1.2 Object Model . . . . . . . . . . . . . . . . . . . . . . . 7
4.3.1.3 Dynamic Model: Event Trace Diagram and State Diagram 7
4.3.2 Structured Systems Analysis and Design Method . . . . . . . . . 7
4.3.2.1 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . 7
4.3.2.2 Entity Relationship Diagram . . . . . . . . . . . . . . . 7
4.3.2.3 Flow Chart / Structure English . . . . . . . . . . . . . 7
4.4 Data Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.4.1 Data dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.4.2 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2
 4.4.3 Data acquisition, Data Integrity, Retention, Disposal . . . . . . . 7
4.5 External Interface Requirements . . . . . . . . . . . . . . . . . . . . . . 8
4.5.1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.5.1.1 User Interfaces . . . . . . . . . . . . . . . . . . . . . . . 8
4.5.1.2 Hardware Interfaces . . . . . . . . . . . . . . . . . . . . 8
4.5.1.3 Software Interfaces . . . . . . . . . . . . . . . . . . . . . 8
4.5.1.4 Communication Interfaces . . . . . . . . . . . . . . . . . 8
4.5.2 Design Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.5.2.1 Standard Development Tools . . . . . . . . . . . . . . . 8
4.5.2.2 Web / Android based Projects . . . . . . . . . . . . . . 8

5 Non Functional Requirements 9

5.1 Performance Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.2 Safety Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.3 Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.4 Software Quality Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.5 Business Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.6 Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.7 Extensibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.8 Maintainability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.9 Portability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.10 Reusability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.11 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

6 Other Requirements 10
6.1 On-line User Documentation and help System Requirements . . . . . . . 10
6.2 Purchased Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.3 Licensing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.4 Legal, copyright and other Notices . . . . . . . . . . . . . . . . . . . . . 10
6.5 Applicable Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.6 Reports (Feedback, Invoice, User, Usage, Balance Sheet, Executive Sum-
mary etc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

7 Appendix A: Glossary 11

3
1 Introduction
1.1 Purpose

1.2 Scope

1.3 Definition, Acronyms and Abbreviations

1.4 References

4
2 Project Planning and Management
2.1 SWOT Analysis

2.2 Gantt Chart

2.3 Work Breakdown Structure[WBS]

2.4 Activity Diagram

5
3 Overall Description of Product
3.1 Product Perspective

3.2 Product Functions

3.3 User Classes and Characteristics

3.4 Operating Environment

3.5 Design and Implementation Constraints

3.6 User Documentation

3.7 Assumptions and Dependencies

6
4 Functional Requirements
4.1 Domain Information

4.2 Project Architecture

4.2.1 Web / Android / Game Module
4.2.1.1 Functions
4.2.1.2 Architecture
4.2.2 Database Module
4.2.3 Administration Module

4.3 System Analysis & Design Overview

Note: Only one Method is to be adopted i.e. either Object Oriented Modeling Technique
or Structured Systems Analysis and Design Method.

4.3.1 Object Oriented Modeling Technique

4.3.1.1 Functional Model: Use Case Diagram
4.3.1.2 Object Model
4.3.1.3 Dynamic Model: Event Trace Diagram and State Diagram
4.3.2 Structured Systems Analysis and Design Method
4.3.2.1 Data Flow Diagram
4.3.2.2 Entity Relationship Diagram
4.3.2.3 Flow Chart / Structure English

4.4 Data Requirements

4.4.1 Data dictionary
4.4.2 Reports
4.4.3 Data acquisition, Data Integrity, Retention, Disposal

7
4.5 External Interface Requirements
4.5.1 Interfaces
4.5.1.1 User Interfaces
4.5.1.2 Hardware Interfaces
4.5.1.3 Software Interfaces
4.5.1.4 Communication Interfaces
4.5.2 Design Constraints
4.5.2.1 Standard Development Tools
4.5.2.2 Web / Android based Projects

8
5 Non Functional Requirements
5.1 Performance Requirements

5.2 Safety Requirements

5.3 Security Requirements

5.4 Software Quality Attributes

5.5 Business Rules

5.6 Interoperability

5.7 Extensibility

5.8 Maintainability

5.9 Portability

5.10 Reusability

5.11 Installation

9
6 Other Requirements
6.1 On-line User Documentation and help System
Requirements

6.2 Purchased Requirements

6.3 Licensing Requirements

6.4 Legal, copyright and other Notices

6.5 Applicable Standards

6.6 Reports (Feedback, Invoice, User, Usage, Balance Sheet,

Executive Summary etc

10
7 Appendix A: Glossary

11