Title Software Requirements Specification

Version <1.0>

<Title> Software Requirements Specification

Version: <1.0> Date: <dd/mmm/yyyy>

Revision History
Date <dd/mmm/yy> Version <x.x> <details> Description <name> Author

Confidential

<Company Name>, 2007

Page 2

<Title> Software Requirements Specification

Version: <1.0> Date: <dd/mmm/yyyy>

Table of Contents
1. Introduction 1.1 Purpose 1.2 Scope 2. Functional Requirements 3. Non-Functional Requirements 4. Actors 5. External Interfaces 6. Data Flow Diagram 7. Assumptions 8. References 9. Glossary 10. Appendix 4 4 4 4 5 5 5 5 5 5 5 5

Confidential

<Company Name>, 2007

Page 3

<Title> Software Requirements Specification

Version: <1.0> Date: <dd/mmm/yyyy>

Software Requirements Specification

1. Introduction
[The introduction should provide an overview of the entire document. It should include the purpose and scope for the document] 1.1 Purpose [This document fully describes the behavior of the<<module name>>. It also describes nonfunctional requirements, constraints and the external interface requirements necessary to provide a complete and comprehensive description of the requirements for the integrated ERP solution] 1.2 Scope [Write down the major features related to your module shortly. Also specify the interfaces to other modules in the ERP application assigned to your group fellows. ]

2.

Functional Requirements
[This section should describe all the functional requirements of the module assigned to you in the following format: 1. System shall provide <<Actor>> the ability to <<Task>>. The <<Actor>> shall provide following information (if any) a. b. Etc. For example: 1. System shall provide customer the ability to place an order. The customer shall provide following information : a. b. c. Etc. Product name : String Order Placement Date: Date, System Generated and MM/DD/YY Customer name : String Information # 1:<<Data Type>>,<< format>> Information # 2: <<Data Type>>,<< format>>

Confidential

<Company Name>, 2007

Page 4

<Title> Software Requirements Specification

Version: <1.0> Date: <dd/mmm/yyyy>

3.

Non-Functional Requirements
[This section should describe all the non-functional requirements including but not limited to Usability, Performance, Security Safety, Business rules, etc. applicable to the software].

4.

Actors
[ List down all the actors interacting with the system. Actor can either be a user or some other software application. Provide a detailed description of their roles and ways they can interact with the system]

5.

External Interfaces
<Describe the connections between this module and other specific modules in the ERP solution, including databases, operating systems, tools, libraries, and integrated commercial components(if any). Identify the data items or messages coming into the system and going out and describe the purpose of each. Describe the services needed and the nature of communications. Identify data that will be shared across software components. >

6.

Data Flow Diagram

[Illustrate the data flow using a context level data flow diagram, also show the data flow to the external modules of the ERP system]

7.

Assumptions
[List down all the assumptions, made for the specification]

8.

References
[List down all the references used in the document, list down all resources from where requirements are being gathered. Provide working links to all web resources as well]

9.

Glossary
[Provide the definitions of all the terms used in the document. [Glossary is a useful tool to address the ambiguity and understandability in the document, therefore all the domain-specific terms or those carrying ambiguous meanings need to be properly defined ]

10.

Appendix
[Provide any appendices, if necessary]

Confidential

<Company Name>, 2007

Page 5