TEXAS DEPARTMENT OF I NFORMATI ON RESOURCES

Software
Requirements
Specification
Template
Version 1.2 14 JAN 2008
NOTE: Please remove this page when creating a Software Requirements Specification deliverable.
Teas Pro!ect "eliver# $ramewor% SO$T&'RE RE()*RE+ENTS SPE,*$*,'T*ON
Using This Template
The companion tool- Software Requirements Specification Instructions- provides detailed direction for
completing this template. This and other $ramewor% Etension tools are available on the $ramewor% &eb
site.
To create a deliverable from this template:
.. "elete the template title page /previous page0 and this page.
1. Replace 2brac%eted tet3 on the cover page /net page0 with #our pro!ect and agenc# information.
4. Replace 2brac%eted tet3 in the tool header area at the top of page i /,ontents page0 with the
same pro!ect and agenc# information as on the cover page.
Note: Please do not remove or modif# content in the footer area.
5. ,omplete the entire template. Each section contains abbreviated instructions- shown in italics-
and a content area. The content area is mar%ed with a placeholder s#mbol /0 or with a table.
Relevant tet from other pro!ect deliverables ma# be pasted into content areas.
Note: Please do not remove the italici6ed instructions.
7. )pdate the table of contents b# right8clic%ing and selecting 9)pdate $ield-: then 9)pdate entire
table.:
NOTE: Please remove this page when creating a Software Requirements Specification deliverable.
"*R "ocument 17SR8T.81
TEXAS PROJECT DEI VER! FRAME"OR#
SOFTWARE
REQUIREMETS S!E"IFI"ATIO
[Agency/Organization Name]
#!RO$E"T AME%
;ERS*ON: 2;ersion Number3 RE;*S*ON "'TE: 2"ate3
Approver Name Title Signature Date
2'genc#<Organi6ation Name3 SO$T&'RE RE()*RE+ENTS SPE,*$*,'T*ON
2Pro!ect Name3 2;ersion Number3 = 2Revision "ate3
"ontents
Section .. Overview.............................................................................................. .
Section 1. 'ssumptions- "ependencies- ,onstraints............................................1
Section 4. Requirements....................................................................................... 4
Section 5. Requirements Traceabilit# +atri.........................................................>
Section 7. References........................................................................................... ?
Section >. @lossar#............................................................................................... A
Section ?. Revision Bistor#................................................................................... C
Section A. 'ppendices......................................................................................... .D
Eased on
"*R "ocument 17SR8T.81 Page i
2'genc#<Organi6ation Name3 SO$T&'RE RE()*RE+ENTS SPE,*$*,'T*ON
2Pro!ect Name3 2;ersion Number3 = 2Revision "ate3
Section &' O(er(iew
1.1 Purpose
Specify the purpose of this Software Requirements Specification (SRS) and its intended
audience.

1.2 Business Context

Provide an overview of the business organization sponsoring the development of the software
application, including the mission statement and organizational obectives of the business unit.

1.3 Scope
!escribe the scope of the software application to be produced.

1. !ser C"aracteristics
"dentify each type of user of the software by function, location, and type of device. Specify the
number of users in each group and the nature of their use of the software.

Eased on
"*R "ocument 17SR8T.81 Page .
2'genc#<Organi6ation Name3 SO$T&'RE RE()*RE+ENTS SPE,*$*,'T*ON
2Pro!ect Name3 2;ersion Number3 = 2Revision "ate3
Section )' Assumptions* +epen,encies* "onstraints
2.1 Assumptions
!escribe the assumptions that can affect the requirements specified in this SRS.

2.2 #epen$encies
!escribe the dependencies that can affect the requirements specified in this SRS.

2.3 Constraints
!escribe the constraints that can affect the requirements specified in this SRS.

Eased on
"*R "ocument 17SR8T.81 Page 1
2'genc#<Organi6ation Name3 SO$T&'RE RE()*RE+ENTS SPE,*$*,'T*ON
2Pro!ect Name3 2;ersion Number3 = 2Revision "ate3
Section -' Requirements
3.1 Business %e&uirements
!escribe all business requirements for the software.

3.2 'unctiona( %e&uirements

#ustomize this subfunction to contain the subfunctions necessary to comprehensively define the
fundamental actions that must ta$e place within the software to accept and process the inputs
and to process and generate the outputs.
Subfunction templates for each of the means of specifying functional requirements are provided
below.
3.2.xf Function X
%hen functional decomposition is used as the means of specifying the functional requirements
provide a &.'.(f subfunction for each function. )ach &.'.(f subfunction should be labeled and
titled appropriately for a specific function, where (f is the appropriate sequential subfunction
number and * is the name of the specific function.
3.2.xf. Function ! "urpose
!escribe the intent of the function.

3.2.xf.2 Function ! Inputs

!escribe the inputs to the function.

3.2.xf.3 Function ! #perations

!escribe the operations to be performed within the function.

3.2.xf.$ Function ! #utputs

!escribe the outputs from the function.

Eased on
"*R "ocument 17SR8T.81 Page 4
2'genc#<Organi6ation Name3 SO$T&'RE RE()*RE+ENTS SPE,*$*,'T*ON
2Pro!ect Name3 2;ersion Number3 = 2Revision "ate3
3.2.xu %se &ase Y
%hen use cases are used as the means of specifying the functional requirements, provide a
&.'.(u subfunction for each use case. )ach &.'.(u subfunction should be labeled and titled
appropriately for a specific use case, where (u is the appropriate sequential subfunction number
and + is the name of the specific use case.
%ithin each use case subfunction, specify the use case information, including the actor, pre,
conditions, post,conditions, scenarios, and alternate scenarios.

3.3 )ogica( #ata %e&uirements

!escribe the logical data requirements for the software.

3. !ser %e&uirements
!escribe the user requirements for the software.

3.* +n,ormation -anagement %e&uirements

!escribe the information management requirements for the software.

3.. Systems %e&uirements

3.'. "erformance Requirements
!escribe the performance conditions and their associated capabilities.

3.'.2 (ualit) Requirements

!escribe requirements for the quality characteristics of the software.

3./ +nter,aces
!escribe the logical characteristics of each interface between the application and other hardware,
software, and communication protocols.
Eased on
"*R "ocument 17SR8T.81 Page 5
2'genc#<Organi6ation Name3 SO$T&'RE RE()*RE+ENTS SPE,*$*,'T*ON
2Pro!ect Name3 2;ersion Number3 = 2Revision "ate3

3.0 Ot"er %e&uirements

"dentify any other requirements that do not fit appropriately into the preceding requirement
sections.

Eased on
"*R "ocument 17SR8T.81 Page 7
2'genc#<Organi6ation Name3 SO$T&'RE RE()*RE+ENTS SPE,*$*,'T*ON
2Pro!ect Name3 2;ersion Number3 = 2Revision "ate3
Section .' Requirements Tracea/ilit0 Matri1
Provide reference to the location of the Requirements -raceability .atri( that indicates traceabilty
from the system requirements documented in the System Requirements Specification to the
design elements documented in the System !esign !escription to the software requirements
documented in this Software Requirements Specification (SRS).

Eased on
"*R "ocument 17SR8T.81 Page >
2'genc#<Organi6ation Name3 SO$T&'RE RE()*RE+ENTS SPE,*$*,'T*ON
2Pro!ect Name3 2;ersion Number3 = 2Revision "ate3
Section 2' References
Provide a list of all documents and other sources of information referenced in the SRS and
utilized in developing the SRS. "nclude for each the document number, title, date, and author.
Document No. Document Title Date Aut*or
Eased on
"*R "ocument 17SR8T.81 Page ?
2'genc#<Organi6ation Name3 SO$T&'RE RE()*RE+ENTS SPE,*$*,'T*ON
2Pro!ect Name3 2;ersion Number3 = 2Revision "ate3
Section 3' 4lossar0
!efine of all terms and acronyms required to interpret the SRS properly.

Eased on
"*R "ocument 17SR8T.81 Page A
2'genc#<Organi6ation Name3 SO$T&'RE RE()*RE+ENTS SPE,*$*,'T*ON
2Pro!ect Name3 2;ersion Number3 = 2Revision "ate3
Section 5' Re(ision 6istor0
"dentify changes to the SRS.
+ersion Date Name Description
Eased on
"*R "ocument 17SR8T.81 Page C
2'genc#<Organi6ation Name3 SO$T&'RE RE()*RE+ENTS SPE,*$*,'T*ON
2Pro!ect Name3 2;ersion Number3 = 2Revision "ate3
Section 7' Appen,ices
"nclude any relevant appendices.

Eased on
"*R "ocument 17SR8T.81 Page .D