Simulation Requirements Review:
Requirement Analysis Review Checklist
Nov
2010
DATA COLLECTION: Requirements Analysis Review Checklist
Simulation Technology: _________________________
Reviewer Name: _______________________________
Date: _________________
For each topic in the checklist, document any issues, comments or concerns, reference the document page
number or other source and provide an estimate of the severity of the issue.
Severity 1=Severe, 2=High, 3=Moderate, 4=Low
Requirements Analysis Checklist
Requirements Elicitation
Requirements elicitation process is clearly
documented
Requirements are traceable to identified
legitimate needs
Requirements elicitation process follows a
systematic approach to analysis.
For instance, was one of the following
approaches employed: Literature review,
observations or interviews, training scenarios
development, or use cases development?
The process did not just focus on identifying
technology needs, but includes training and/or
training context needs.
Requirements documentation
Requirements address functional and nonfunctional system needs
Functional requirements define what a system
is supposed to do whereas
Non-functional requirements define how a
system is supposed to be...qualities of a
system (e.g., usability)
Requirements are complete
The domain is fully represented.
Requirements are concise
Requirements are correct
Requirements reflect an accurate
understanding of the domain.
Requirements are consistent
Requirements are modular and can accommodate
Issue
Reference
Severity
Simulation Requirements Review:
Requirement Analysis Review Checklist
Requirements Analysis Checklist
change.
Requirements are realistic
Sufficient attention is given to measurable trainee
performance
If this is a simulation technology is being
developed specifically for R&D:
- the research problem/opportunity is clearly
stated and accurate
- the innovation is clearly described
- the objectives are clearly described along
with criteria for achieving those objectives
- assumptions that impact the success of the
project are clearly described
Contingency planning is included through risk
analysis
Issue
Reference
Nov
2010
Severity
Simulation Requirements Review:
Requirement Analysis Review Checklist
Nov
2010
Simulation Requirements Review:
Requirement Review Reporting Template
REPORTING: Requirements Review Reporting Template
Simulation Technology: _________________________
Reviewer Name: _______________________________
Date: _________________
In reporting the results of the Simulation Requirements Analysis Review:
1.
2.
3.
4.
5.
6.
Specify the requirements topic areas
Give each issue a unique identification number
Identify the source material toward which the comment is targeted - e.g. the page or line number, item
number, etc.
Define the specific issue or concern
Include a severity code from the severity rating scheme, or at least some indication which issues should
be made a priority
Summarize the potential resolution - Some feedback to be provided to contractors may involve general
or ‘cross-cutting’ observations.
Severity 1=Severe, 2=High, 3=Moderate, 4=Low
Requirements Analysis Checklist
Requirements Elicitation
Requirements elicitation process is clearly
documented
Requirements are traceable to identified
legitimate needs
Requirements elicitation process follows a
systematic approach to analysis.
For instance, was one of the following
approaches employed: Observations or
interviews, training scenarios development,
or use cases development?
The process did not just focus on identifying
technology needs, but includes training
and/or training context needs.
Requirements documentation
Requirements address functional and nonfunctional system needs
(Functional requirements define what a
system is supposed to do whereas
Non-functional requirements define how a
system is supposed to be...qualities of a
system such as usability)
Requirements are complete
The domain is fully represented.
Requirements are concise
Requirements are correct
Requirements reflect an accurate
understanding of the domain.
Requirements are consistent
ID#
Issue
Ref
Severity
Potential Resolution
Nov
2010
Simulation Requirements Review:
Requirement Review Reporting Template
Requirements Analysis Checklist
Requirements are modular Can
accommodate change.
Requirements are realistic
Sufficient attention is given to measurable
trainee performance
If this is a simulation technology is being
developed specifically for R&D:
- the research problem/opportunity is
clearly stated and accurate
- the innovation is clearly described
- the objectives are clearly described
along with criteria for achieving those
objectives
- assumptions that impact the success of
the project are clearly described
ID#
Issue
Ref
Severity
Potential Resolution
Nov
2010