REQUIREMENT ANALYSIS

NIST TRAINING & CONSULTANCY SERVICES
(A division of National Institute of Science & Technology)

HOME >> FOCUS AREA >> S/W ENGINEERING >> METHODOLOGY >> REQUIREMENT ANALYSIS

Requirement Analysis

Module: [Module Number / Module Name]

Overview Statement

[A one line description of the purpose of the module.]

Customers

[Name and short address of the customer.]

Goals of the Module

[Goals of the module and any future plans related to it must be explicitly stated.]

System Functions

[This section keeps track of all the system functions specified by the client.]

Ref #	Function	Category
[Reference number]	[List all the functions the system is required to do]	[Specify the category of the function here]
R 1.1	The system should produce bills on the counter.	Evident

[[[

System functions are what a system is supposed to do. To verify that some X is indeed a system function, it should make sense in the following sentence:

The system should do <X>

Every system function should be given a reference number so that it can be referred in the future while writing the use cases. Evident functions should be numbered with R 1.*, Hidden functions as R 2.* and Frill functions as R 3.*.

The category of the function should be explicitly stated under the category header. The three major function categories are as below:

Function Categories

Function Category	Meaning
Evident	Should perform and user should be cognizant that it is performed
Hidden	Should perform but not visible to users
Frill	Optional; adding it does not significantly affect cost of other functions

]]]

System Attributes

Attribute	Detail and Boundary Constraint
Software	[Software platform on which the application will run]
Hardware	[Hardware platform]
Network	[Network type]

HOME >> FOCUS AREA >> S/W ENGINEERING >> METHODOLOGY >> REQUIREMENT ANALYSIS