Software Requirement Spec. Template

Only available on StudyMode
  • Topic: Requirements analysis, Software requirements, Software Requirements Specification
  • Pages : 12 (1560 words )
  • Download(s) : 131
  • Published : February 23, 2013
Open Document
Text Preview
[ Project ]

Software Requirements Specification

CxTemp_SoftwareRequirementsSpecification.doc

Draft X

June 27, 2001

[ Organization Name ]

[ Paste Your Organization’s Logo Here ]

Revisions

|Version |Primary Author(s) |Description of Version |Date Completed | |Draft Type and |Full Name |Information about the revision. This table does not need to be |00/00/00 | |Number | |filled in whenever a document is touched, only when the version| | | | |is being upgraded. | | | | |CxPattern_RevisionHistory provides details on CxOne’s | | | | |recommended way to handle document revisions. | |

The paragraphs written in the “Comment” style are for the benefit of the person writing the document and should be removed before the document is finalized.

This template can be used to create Software Requirements Specifications that conform to IEEE Standard 830-1993.

An SRS is a tool for capturing requirements on a project; it is the epitome of “plain language requirements”. Although an SRS is designed to stand on its own, most projects will employ additional tools for capturing requirements. An SRS may be ancillary or unnecessary on many projects, but a partial or lightweight one may be quite useful even if other techniques are being used to capture the bulk of the requirements.

Consider using an SRS when:

• Modeling techniques need to be augmented

• Plain language is the best mechanism for capturing system behavior

• Requirements must be traceable

• Required by regulations

See CxGuide_CxOneArtifact for details on how to utilize the advanced features of CxOne artifact templates.

Contents

1 Introduction1

1.1 Purpose1
1.2 Scope1
1.3 Definitions, Acronyms, and Abbreviations1
1.4 References1
1.5 Overview1

2 Overall Description2

2.1 Product Perspective2
2.1.1 System Interfaces2
2.1.2 User Interfaces2
2.1.3 Hardware Interfaces2
2.1.4 Software Interfaces2
2.1.5 Communications Interfaces2
2.1.6 Memory Constraints3
2.1.7 Operations3
2.1.8 Site Adaptation Requirements3
2.2 Product Functions3
2.3 User Characteristics3
2.4 Constraints3
2.5 Assumptions and Dependencies4
2.6 Apportioning of Requirements4

3 Specific Requirements5

3.1 External Interface Requirements5
3.1.1 User Interfaces6
3.1.2 Hardware Interfaces6
3.1.3 Software Interfaces6
3.1.4 Communications Interfaces6
3.2 Software Product Features6
3.2.1 Feature 16
Purpose6
Stimulus/Response Sequence6
Associated Functional Requirements6
3.3 Performance Requirements6
3.4 Design Constraints7
3.5 Software System Attributes7
3.5.1 Reliability7
3.5.2 Availability7
3.5.3 Security7
3.5.4 Maintainability7
3.6 Logical Database Requirements7
3.7 Other Requirements8

Introduction

This section should provide an overview of the entire document.

1 Purpose

Describe the purpose of this specification and its intended audience.

2 Scope

Identify the software product(s) to be produced by name. Explain what the products will and will not do. Describe how the software will be used, and identify relevant benefits, objectives, and goals.

3 Definitions, Acronyms, and Abbreviations

Define all terms, acronyms, and abbreviations used in this document.

4 References

List all the documents and other materials referenced in this document. This section is like the bibliography in a published book.

5 Overview

Describe the content and organization of the rest of this document.

Overall Description...
tracking img