Software Requirements Specification Template

Business RequirementsDocument

for

Version 1.0 approved

Prepared by

Approvals

Approval Decision:

( Approved, development of detailed project plan is authorized

( Approved, project execution is authorized

( Approved, but project is on hold until future notice

( Revise document and resubmit for approval

( Document and project proposal are rejected

Role or TitleName and SignatureDate

Revision History

NameDateReason For ChangesVersion

Table of Contents

iiiApprovals

Revision HistoryivTable of Contentsv1.Introduction11.1Purpose11.2References12.Overall Description22.1Product Perspective22.2Product Features22.3User Classes and Characteristics22.4Design and Implementation Constraints22.5Assumptions and Dependencies23.Functional Requirements33.1Solution Context Diagram33.2Actor Descriptions43.3Master Events List63.4Event Name 183.5Event Name n104.Data Requirements115.Non-functional Requirements125.1Performance Requirements125.2Safety Requirements125.3Security Requirements125.4Software Quality Attributes125.5User Documentation125.6Operating Environment126.Transition Requirements137.Change Management14Appendix A: Glossary15Appendix B: Traceability Matrix15Appendix C: Issues List15

1. Introduction

1.1 Purpose

1.2 References

2. Overall Description

2.1 Product Perspective

2.2 Product Features

2.3 User Classes and Characteristics

2.4 Design and Implementation Constraints

2.5 Assumptions and Dependencies

3. Functional Requirements

3.1 Solution Context Diagram

10) leave them out and show Actors only An example is provided.>

3.2 Actor Descriptions

Actor NameA name that describes the role the actor plays in relation to the system (one or two words).

DescriptionA brief description of who or what the actor is.

User and Shareholder MappingMap this actor to stakeholders and uses of the system by listing the job functions corresponding to these actors. For each user and stakeholder type, identify the number of users.

TypeNumberTypeNumber

Goals and Relationships with the SystemDescribe what the actor expects from the system. If the use case is successful, what will be the result for this actor? What will the result if the use case is unsuccessful?

Frequency of UseHow often this actor will use the system (once weekly? 20 times per day? For every transaction?)

Physical EnvironmentDescribe the physical environment in which the actor will be using the system. Also include other applications used by this actor, operating systems, and so on.

General CharacteristicsInclude level of expertise at job task, computer literacy, language, age, and so on.

3.3 Master Events ListEvent NameProcess Name

3.4 Event Name 1

Process Name 1

Process Description

Use Case Diagram

Use Case Scenarios

Interfaces

Workflow

Non-Functional Requirements

3.5 Event Name n

4. Data Requirements

5. Non-functional Requirements

5.1 Performance Requirements

5.2 Safety Requirements

5.3 Security Requirements

5.4 Software Quality Attributes

5.5 User Documentation

5.6 Operating Environment

6. Transition Requirements

7. Change Management

Appendix A: Glossary

Appendix B: Traceability Matrix

Appendix C: Issues List

< This is a dynamic list of the open requirements issues that remain to be resolved, including TBDs, pending decisions, information that is needed, conflicts awaiting resolution, and the like.>

Actor

Use Case

Product Description

Product Price

Quantity on Hand

Product Number

PRODUCT

Customer Name

Customer Address

Customer Number

CUSTOMER

buys

is bought by