Org_it_(TCS-iQMS-104)_Common_SRS_Template.doc

Software Requirements Specifications Version

< month year>

Warning <# Normal instruction from QMS template to be included>

Software Requirements Specifications ver.

DOCUMENT RELEASE NOTICE Document Details: Name Software Requirements Specifications

Version No.

Description SRS document for of

Revision Details Action taken (Add/Del/Change)

Preceding Page No.

New Page No.

Revision Description

This document and any revised pages are subject to document control. Please keep them upto-date using the release notices from the distributor of the document. Approved by:

Date:

Authorised by:

Date:

Internal Use Only

i


TABLE OF CONTENTS 1. INTRODUCTION...................................................................... ............................................ 1 1.1 1.2 1.3 1.4 1.5

PURPOSE..................................... ......................................... ................................... ......... 1 SCOPE..................................... ........................................ ....................................... .......... 1 DEFINITIONS, ACRONYMS AND ABBREVIATIONS...................................................................2 REFERENCES.................................... ........................................ ........................................ 2 OVERVIEW....................................... ........................................ ......................................... 2

2. GENERAL REQUIREMENTS...............................................................................................3 2.1 PRODUCT PERSPECTIVE....................................................................................................3 2.1.1 System Interface.......................................................................................................3 2.1.2 User Interface...........................................................................................................4 2.1.3 Hardware Interface...................................................................................................4 2.1.4 Software Interface....................................................................................................4 2.1.5 Communication Interface..........................................................................................5 2.1.6 Memory Constraints.................................................................................................5 2.1.7 Operations................................................................................................................5 2.1.8 Site Adaptation requirements...................................................................................5 2.2 PRODUCT FUNCTIONS........................................................................................................5 2.3 USER CHARACTERISTICS...................................................................................................5 2.4 CONSTRAINTS....................................... ......................................... ................................... 5 2.5 ASSUMPTIONS AND DEPENDANCIES....................................................................................5 2.6 PRIORATISING OF THE REQUIREMENTS...............................................................................5 3. SPECIFIC REQUIREMENTS................................................................................................6 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8

EXTERNAL INTERFACES.....................................................................................................6 FUNCTIONS..................................... ........................................ ......................... ................. 6 PERFORMANCE REQUIREMENTS.........................................................................................6 LOGICAL D ATABASE REQUIREMENTS..................................................................................6 DESIGN CONSTRAINTS.......................................................................................................6 SOFTWARE SYSTEM ATTRIBUTES........................................................................................7 ORGANIZING THE SPECIFIC REQUIREMENTS........................................................................7 ADDITIONAL COMMENTS ...................................................................................................7

4. APPENDIX.................................................... ......................................... .............................. . 8 5. INDEX.............................................. ......................................... .............................. ............ 10 Total Number of pages: 14

Internal Use Only

ii


1. Introduction 1.1 Purpose

1.2 Scope

Internal Use Only

1


1.3 Definitions, Acronyms and Abbreviations The following abbreviations and Acronyms have been used in this document. Abbreviation/Acronym

Description

1.4 References

1.5 Overview < For e.g. This document consists of sections and appendices. Section 1 Section 2 >

Internal Use Only

2


2. General Requirements 2.1 Product Perspective < Describe how the product operates inside various constraints. A block diagram showing major components of the large system, interconnections and external interfaces. Identify the main processes to be automated as process P1, P2, etc. Draw the overall process map for these main processes and the sub-processes within these. The sub-processes can be identified as P1.1, P1.2, etc.>

P1 Litigation

P2 Trademark & Copyright Process

P3 Patency P4 Designing

Database

EDP Staff

Accounts

Figure 2-1: Name of process

2.1.1 System Interface

Internal Use Only

3


2.1.2 User Interface

2.1.2.1 Screen Layouts 2.1.2.1.1

Navigation Chart

2.1.2.1.2

Screen Layout :

2.1.2.1.3

Screen Description

Attribute Name

Description

Remarks

2.1.2.2 Report Layouts 2.1.2.2.1

Report Layout:

2.1.2.2.2

Report Description

Title: Purpose: Intended Users: Frequency: Report Sequence: Business Logic:

Title of the report Business purpose for the report Intended distribution Frequency of generation Description of the required sequence Description of the business logic

2.1.3 Hardware Interface

2.1.4 Software Interface

Internal Use Only

4


2.1.5 Communication Interface

2.1.6 Memory Constraints

2.1.7 Operations

2.1.8 Site Adaptation requirements

2.2 Product Functions < Specify the summary of major functions that the software will perform>

2.3 User Characteristics

2.4 Constraints

2.5 Assumptions and Dependancies The successful execution of the assignment will depend on the following factors:
Prompt responses from the client on queries from the project

Dependencies < ♦ Involvement of the end users in signing off this SRS document. ♦ Availability of System Software from the client for development. ♦ Availability of installed hardware/System software for implementation. υ Feedback on this report will be provided as per the agreemnent in the contract. Any delay in the feedback will have impact on the schedule and cost of the project. >

2.6 Prioratising of the Requirements

Internal Use Only

5


3. Specific Requirements

3.1 External Interfaces Name of the Item Description of Purpose Source of input/Destination of output Valid range, Accuracy and/or Tolerance Units of measure Timing Relationship to other inputs/outputs Screen formats/Organizatio n Window format/Organization Data format Command formats End messages

3.2 Functions

3.3 Performance Requirements

3.4 Logical Database Requirements

3.5 Design Constraints

Internal Use Only

6


3.6 Software system attributes

3.7 Organizing the Specific Requirements

3.8 Additional Comments

Internal Use Only

7


4. Appendix < Include the reference data and codification requirements including: Reference data that are shared with other applications Reference data that are private> Attribute Name

Description

8


The Analysis Object Model (AOM) will contain the following: a. Use Case View: (i) (ii)

Use Case diagram Activity Diagram to realize Business use cases

b. Analysis View: (i) (ii) (iii)

Class diagram State transition diagram (If classes need to store state information, more pertinent for Embedded systems application) Sequence diagram (or) Collaboration diagram.>

AOM will be done using a tool supporting UML notation, like Rational Rose.

Internal Use Only

9


5. Index

Internal Use Only

10

Org_it_(TCS-iQMS-104)_Common_SRS_Template.doc

Recommend Documents