Requirements Template v1 0 en

Public/Confidential/Secret DRAFT/PROPOSAL/APPROVED
[choose confidentiality level] [choose document status] v0.1en

[version number + language]
[Your company’s name here] 1(13)
[Enter application name here]

Requirement Specification
Status Draft/Proposal/Approved [choose document status]

Author [Your name]
Approve [Name of the approver]
r
[Application XXX] ©[Your company’s name here] 1

TABLE OF CONTENTS
1 [Application name] Requirement Specification Changes............................................3
2 Open issues.......................................................................................................................4
3 Introduction.......................................................................................................................5
3.1 Glossary.......................................................................................................................5
4 Functional Requirements.................................................................................................6
4.1 [Requirement name].....................................................................................................6
4.2.1 [Sub-requirement name]........................................................................................6
5 Non-functional Requirements..........................................................................................8
5.2.1 [Sub-requirement name]........................................................................................8
6 Constraints......................................................................................................................10
6.1 [Requirement name]...................................................................................................10
6.2.1 [Sub-requirement name]......................................................................................10
7 Interface Requirements..................................................................................................12
7.2.1 [Sub-requirement name]......................................................................................12

1 [Application name] Requirement Specification Changes
Document Document Date Editor Changes

version status
V1.1 APPROVED 27-Mar- Edith Editorial changes

2006 Example
V1.0 APPROVED 15-Mar- Edith First approved

2006 Example version, changes
made according to
the requirement
statement review
comments.
V0.3 PROPOSAL 10-Mar- Edith Added the

2006 Example “Changing the
message image”
requirement.
V0.2 DRAFT 05-Mar- Edith Removed the

2006 Example “Delayed timing for
message sending”
requirement.
V0.1 DRAFT 1-Mar- Edith First draft version

2006 Example created on the
basis of the market
data.

2 Open issues
[The following issues related to requirement specification are still open:
1. Issue 1 – explanation of why this issue is still open
2. Issue 2 – explanation of why this issue is still open
3. Issue 3 – explanation of why this issue is still open]

3 Introduction
[Insert text here]
[What is the purpose of this document?

Who are the target readers of this document?]
3.1 Glossary
[Insert text here]
Term Explanation
[Insert term, acronym or [Insert explanation of term]
abbreviation]
Table x. Terms and definitions

4 Functional Requirements
4.1 [Requirement name]
Requirement
name:
ID:
Description: [Insert information from the use case]
Persona:
Impact: [choose priority: MUST HAVE, SHOULD HAVE, or NICE

TO HAVE]
Criteria:
Type:
Dependencies: [Insert IDs and names of related requirements]
Requirement
name:
ID:
Persona:

TO HAVE]
Criteria:
Type:
4.2.1 [Sub-requirement name]

Requirement
name:
ID:

Persona:

TO HAVE]
Criteria:
Type:

5 Non-functional Requirements
Requirement
name:
ID:
Persona:

TO HAVE]
Criteria:
Type:
Requirement
name:
ID:
Persona:

TO HAVE]
Criteria:
Type:

Requirement
name:
ID:

Persona:

TO HAVE]
Criteria:
Type:

6 Constraints
Requirement
name:
ID:
Persona:

TO HAVE]
Criteria:
Type:
Requirement
name:
ID:
Persona:

TO HAVE]
Criteria:
Type:

Requirement
name:
ID:

Persona:

TO HAVE]
Criteria:
Type:

7 Interface Requirements
Requirement
name:
ID:
Persona:

TO HAVE]
Criteria:
Type:
Requirement
name:
ID:
Persona:

TO HAVE]
Criteria:
Type:

Requirement
name:
ID:

Persona:

TO HAVE]
Criteria:
Type:

Requirements Template v1 0 en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Requirements Template v1 0 en

Uploaded by

Copyright:

Available Formats

Public/Confidential/Secret DRAFT/PROPOSAL/APPROVED

[choose confidentiality level] [choose document status] v0.1en

[Enter application name here]

Status Draft/Proposal/Approved [choose document status]

[Application XXX] ©[Your company’s name here] 1

[Application XXX] ©[Your company’s name here] 2

1 [Application name] Requirement Specification Changes

Document Document Date Editor Changes

V1.1 APPROVED 27-Mar- Edith Editorial changes

V1.0 APPROVED 15-Mar- Edith First approved

V0.3 PROPOSAL 10-Mar- Edith Added the

V0.2 DRAFT 05-Mar- Edith Removed the

V0.1 DRAFT 1-Mar- Edith First draft version

[Application XXX] ©[Your company’s name here] 3

[Application XXX] ©[Your company’s name here] 4

[What is the purpose of this document?

[Insert text here]

Table x. Terms and definitions

[Application XXX] ©[Your company’s name here] 5

4.1 [Requirement name]

Description: [Insert information from the use case]

Impact: [choose priority: MUST HAVE, SHOULD HAVE, or NICE

Dependencies: [Insert IDs and names of related requirements]

4.2 [Requirement name]

Description: [Insert information from the use case]

Impact: [choose priority: MUST HAVE, SHOULD HAVE, or NICE

Dependencies: [Insert IDs and names of related requirements]

4.2.1 [Sub-requirement name]

[Application XXX] ©[Your company’s name here] 6

Description: [Insert information from the use case]

Impact: [choose priority: MUST HAVE, SHOULD HAVE, or NICE

Dependencies: [Insert IDs and names of related requirements]

[Application XXX] ©[Your company’s name here] 7

Description: [Insert information from the use case]

Impact: [choose priority: MUST HAVE, SHOULD HAVE, or NICE

Dependencies: [Insert IDs and names of related requirements]

5.2 [Requirement name]

Description: [Insert information from the use case]

Impact: [choose priority: MUST HAVE, SHOULD HAVE, or NICE

Dependencies: [Insert IDs and names of related requirements]

5.2.1 [Sub-requirement name]

Description: [Insert information from the use case]

[Application XXX] ©[Your company’s name here] 8

Impact: [choose priority: MUST HAVE, SHOULD HAVE, or NICE

Dependencies: [Insert IDs and names of related requirements]

[Application XXX] ©[Your company’s name here] 9

Description: [Insert information from the use case]

Impact: [choose priority: MUST HAVE, SHOULD HAVE, or NICE

Dependencies: [Insert IDs and names of related requirements]

6.2 [Requirement name]

Description: [Insert information from the use case]

Impact: [choose priority: MUST HAVE, SHOULD HAVE, or NICE

Dependencies: [Insert IDs and names of related requirements]

6.2.1 [Sub-requirement name]

Description: [Insert information from the use case]

[Application XXX] ©[Your company’s name here] 10

Impact: [choose priority: MUST HAVE, SHOULD HAVE, or NICE

Dependencies: [Insert IDs and names of related requirements]

[Application XXX] ©[Your company’s name here] 11

Description: [Insert information from the use case]

Impact: [choose priority: MUST HAVE, SHOULD HAVE, or NICE

Dependencies: [Insert IDs and names of related requirements]

7.2 [Requirement name]