neeine

1. Introduction

1.1 Purpose
1.2 Scope and
Abbreviations

Acronyms,
Definitions,
1.3
1.4 References
1.5 Overview

The Overall Description

Produet Perspective
System Interfaces
2.1.1
Interfaces
2.1.2 Hardware Intertaces
2.1.3 Software Interfaces
2.1.4 Communications Interfaces

2.1.5
Memory Constraints
2.1.6
Operations
Site Adaptation Requirements

duct Functions

Characteristics

traints
ptions and Dependencies.

ioning of Requirenments

rements

l interfaces

ance Requirements
Database Requirements
onstraints

ndards Compliance
System Attributes

Keliability
3.6.2 Availability
3.6.3 Security
3.6.4 Maintainability
3.6.5 Portability
3.7 Organising the Specific Requirements
3.7.1 System Mode
3.7.2 User Class
3.7.3 Objects
3.7.4 Feature
3.7.5 Stimulus
3.7.6 Response
3.7.7 Funetional Hierarchy
3.8 Additional Comments
Proces8
4. Change Management
Document Approvals
6. Supporting Information
Fig. 3.18: Organisation of SRS [IEEE-std. 830-19931

Scanned by CamScanner
 Software Enginee
76

1. Introduction

1.1 Purpose
1.2 Scope and
Abbreviations

Acronyms,
Definitions,
1.3
1.4 References

1.5 Overview
Description
2. The Overall
2.1 Product Perspective
System Interfaces

2.1.1
Interfaces
2.1.2
Hardware Interfaces

2.1.3 Software Interfaces

2.1.4 Communications Interfaces

2.1.5 Memory Constraints

2.1.6
2.1.7 Operations
Requirements
2.1.8 Site Adaptation
2.2 Product Functions

User Characteristics
2.3
Constraints
2.4 Assumptions and Dependencies.
2.5
Apportioning of Requirements
2.6
3. Specific Requirements
3.1 External interfaces
3.2 Functions
Performance Requirements
3.3
Logical Database Requirements
3.4
3.5 Design Constraints

3.5.1 Standards Compliance

Attributes
3.6 Software System
3.6.1 Reliability
3.6.2 Availability
3.6.3
Security
3.6.4Maintainability
3.6.5Portability
3.7 Organising the Specific Requirements
3.7.1 System Mode
3.7.2 User Class

3.7.3 Objects
3.7.4 Feature
3.7.5 Stimulus
3.7.6 Response
3.7.7 Functional Hierarchy
Additional Comments
3.8
Process
4. Change Management
5. Document Approvals
6. Supporting Information

Fig. 3.18: Organisation of SRS [IEEE-std. 830-1993

Scanned by CamScanner
 224 Software Engineering
GDD
Table 5.1: Organisation of

1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions and acronyms
2 References
3 Decomposition description
3.1 Module decomposition
3.1.1 Module 1 description
3.1.2 Module 2 description
Concurrent process decompostion
3.2
3.2.1 Process 1 description
3.2.2 Process 2 description
3.3 Data decomposition
3.3.1 Data entity 1 description
3.3.2 Data entity 2 description
4 Dependency description
4.1 Intermodule dependencies
4.2 Interprocess dependencies
4.3 Data dependencies
5. Interface description
5.1 Module Interface
5.1.1 Module 1 deseription
5.1.2 Module 2 description
5.2 Process interface
5.2.1 Process description
5.2.2 Process 2 description
6. Detailed design
6.1 Module detailed design
6.1.1 Module 1 detail
6.1.2 Module 2 detail
6.2 Data detailed design
6.2.1 Data entry 1 detail
6.2.2 Data entry 2 detail

o ltheesst
Entity altribute information can be organised in several ways to reveal all ot
Cach design

tial aspects of a design. There may be number of ways to view the design. Hence, ea proride

view represents a separate concern about a soft ware system. Together, these view>
l i e s inhorm

comprehensive description of the design in a concise and usabBe form that simpline
tion access and assimilation. A recommended organisation of the SDD into separa
views to facilitate infoimation access and assimilation is given in Table 5.2.