SDLC SystemRequirements Template

8/21/2019 SDLC SystemRequirements Template

1/16

TEXAS DEPARTMENT OF INFORMATION RESOURCES

System Requirements

Specification

Template

Version 1.2 14 JAN 2008

NOTE: Please remove this page whe !reatig a S"stem Re#$iremets Spe!i%i!atio &elivera'le


2/16

Te(as Pro)e!t Deliver" Framewor* S+STEM RE,UIREMENTS SPECIFICATION

Using This Template

The !ompaio tool- System Requirements SpecificationInstructions- provi&es &etaile& &ire!tio %or

!ompletig this template. This a& other Framewor* E(tesio tools are availa'le o the Framewor* /e'

site.

To !reate a &elivera'le %rom this template:

0. Delete the template title page 1previo$s page2 a& this page.

3. Repla!e 4'ra!*ete& te(t5 o the !over page 1e(t page2 with "o$r pro)e!t a& age!" i%ormatio.

6. Repla!e 4'ra!*ete& te(t5 i the tool hea&er area at the top o% page i 1Cotets page2 with the

same pro)e!t a& age!" i%ormatio as o the !over page.

Note: Please &o ot remove or mo&i%" !otet i the %ooter area.

7. Complete the etire template. Ea!h se!tio !otais a''reviate& istr$!tios- show i itali!s-a& a !otet area. The !otet area is mar*e& with a pla!ehol&er s"m'ol 12 or with a ta'le.

Relevat te(t %rom other pro)e!t &elivera'les ma" 'e paste& ito !otet areas.

Note: Please &o ot remove the itali!i8e& istr$!tios.

9. Up&ate the ta'le o% !otets '" right!li!*ig a& sele!tig ;Up&ate Fiel&-< the ;Up&ate etire

ta'le.Orgai8atio Name5 S+STEM RE,UIREMENTS SPECIFICATION

4Pro)e!t Name5 4=ersio N$m'er5 ? 4Revisio Date5

Section ,' System Capa-ilities. Con(itions. an(

Constraints

3.1 Business -euirements

!escribe all business requirements for the system.

3.2 unctiona' -euirements

%ustomize this subsection to contain the subsections necessary to comprehensively define the

fundamental actions that must ta&e place within the system to accept and process the inputs and

to process and generate the outputs.

Subsection templates for each of the means of specifying functional requirements are provided

below.

3.2.nf FunctionX

'hen functional decomposition is used as the means of specifying the functional requirements,

provide a ..nf subsection for each function. *ach ..nf subsection should be labeled and titled

appropriately for a specific function, where nf is the appropriate sequential subsection number

and + is the name of the specific function.

3.2.nf.1 FunctionXurpose

!escribe the intent of the function.

3.2.nf.2 FunctionXInputs

!escribe the inputs to the function, including sources, valid ranges of values, timing

considerations, operator requirements, and special interfaces.

3.2.nf.3 FunctionX!perations

!escribe the operations to be performed within the function, including validity chec&s,

responses to abnormal conditions, and types of processing required.

@ase& o

DIR Do!$met 39S+T03 Page 7


9/16

4Age!">Orgai8atio Name5 S+STEM RE,UIREMENTS SPECIFICATION


3.2.nf." FunctionX!utputs

!escribe the outputs from the function, including output destinations, valid ranges of values,

timing considerations, considerations for handling of illegal values, error messages, and

interfaces required.

3.2.nu#se $ase Y

'hen use cases are used as the means of specifying the functional requirements, provide a

..nu subsection for each use case. *ach ..nu subsection should be labeled and titled

appropriately for a specific use case, where nu is the appropriate sequential subsection number

and is the name of the specific use case.

'ithin each use case subsection, specify the use case information, including the actor, pre-

conditions, post-conditions, scenarios, and alternate scenarios.

3.3 P"ysica' -euirements

3.3.1 $onstruction

Specify the environmental characteristics of where the system will be installed.

3.3.2 Dura%ility

Specify the durability characteristics of the system.

3.3.3 A&apta%ility

Specify the growth, e#pansion, capability, and contraction characteristics of the system.

3.3." 'nvironmental $on&itions

Specify the environmental conditions to be encountered by the system.

3. 0ogica' +ata -euirements

!escribe the logical data requirements for the system.

@ase& o



10/16



3.( !ser -euirements

!escribe the user requirements for the system.

3.) normation #anagement -euirements

!escribe the information management requirements for the system.

3.* Systems -euirements

3.(.1 erformance Requirements

!escribe the performance conditions and their associated capabilities.

3.(.2 )uality Requirements

!escribe requirements for the quality characteristics of the system.

3., Po'icy an$ -egu'ation -euirements

!escribe policy and regulations for the system.

3. System 0ie Cyc'e Sustainment -euirements

!escribe the life cycle sustainment activities to be e#ecuted during the life cycle of the system.

@ase& o

DIR Do!$met 39S+T03 Page B


11/16



Section /' System Interfaces

Specify in detail the requirements and dependencies for interfaces among system components

and their e#ternal capabilities, including all users, both human and other systems. "ncludee#isting systems, systems under development, and future systems.

@ase& o

DIR Do!$met 39S+T03 Page


12/16



Section 0' Requirements Tracea-ility Matri1

Provide reference to the location of or provide the actual Requirements raceability /atri# that

will be completed during the life of the proect.

@ase& o



13/16



Section 2' References

Provide a list of all documents and other sources of information referenced in the SyRS and

utilized in developing the SyRS. "nclude for each the document number, title, date, and author.

Document No. Document Title Date Aut*or

@ase& o



14/16



Section 3' *lossary

!efine of all terms and acronyms required to interpret the SyRS properly.

@ase& o

DIR Do!$met 39S+T03 Page 0G


15/16



Section 4' Re5ision 6istory

"dentify changes to the SyRS.

+ersion Date Name Description

@ase& o



16/16



Section 7' !ppen(ices

"nclude any relevant appendices.

@ase& o

SDLC SystemRequirements Template

Documents

Transcript of SDLC SystemRequirements Template