Srs Templet

Only available on StudyMode
  • Download(s) : 55
  • Published : December 13, 2012
Open Document
Text Preview


Software Requirements Specification

Version

[Note: The following template is provided for use with CS310 – Software Engineering. Text enclosed in square brackets and displayed in blue italics is included to provide guidance to the author and should be deleted before publishing the document. In addition to the sections given below, you may also add index and list of figures but that is optional]

Revision History
|Date |Version |Description |Author | | | | | | | | | | | | | | | | | | | | |

[Place your revision history in here. Your instructor wants to see how you have been working on this document during this term, and who’s done what and when.]

Table of Contents

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

2.Overall Description1
2.1Product Perspective1
2.2Product Features1
2.3User Characteristics1
2.4Operating Environment1

3.Specific Requirements1
3.1Functional Requirements2
3.2Non Functional Requirements2

4.System Interfaces2
4.1User Interfaces2
4.2Hardware Interfaces2
4.3Software Interfaces2
4.4Communications Interfaces2
Software Requirements Specification

Introduction

[The introduction of the Software Requirements Specification (SRS) provides an overview of the entire document. It includes the purpose, scope, definitions, acronyms, abbreviations, and references.]

1 Purpose

[Specify the purpose of this Software Requirements Specification. The SRS fully describes the external behavior of the application or subsystem identified. It also describes nonfunctional requirements, design constraints, and other factors necessary to provide a complete and comprehensive description of the requirements for the software.]

2 Scope

[Identify SW product(s) to be produced by name. Describe the application of the software being specified, including benefits, objectives, goals. What is the application domain? (e.g., embedded system for automotive systems, graphical modeling utility). Explain what your product will, and if necessary, will not do.]

3 Definitions, Acronyms, and Abbreviations

[Define all terns, acronyms, and abbreviations need to understand the SRS. If this section is extensive, then move it to an appendix. It is also possible to provide a link to other resources for extensive terminology explanation.]

4 References

[This subsection provides a complete list of all documents referenced elsewhere in the SRS. Identify each document by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. Harvard referencing system to be used].

5 Overview

[This subsection describes what the rest of the SRS contains and explains how the document is organized.]

Overall Description

[This section of the Software Requirements Specification describes the general product requirements.]

1 Product Perspective

[Give and describe a high-level diagram for the basic design of your system]

2 Product Features

[Summarize the major functions that software will perform. These function descriptions should be easily understandable by the customer or by any general reader.]

3 User Characteristics

[Who are the users of the system and what is each of them...
tracking img