Requirements Analysis Checklist - Form RAC: Name: Team #: Company Name: Project Name: Date: Phase: Analysis
Requirements Analysis Checklist - Form RAC: Name: Team #: Company Name: Project Name: Date: Phase: Analysis
Req. #:
Yes No, Explanations (report the Req. in the
Negotiation/Conflict Resolution Template)
Does the requirement adequate with the
business goal of the project?
Does the requirement conflict with some
domain constraint, policies or regulation?
Does the requirement include premature
design or implementation information?
Is the requirement necessary?
Does the requirement require non-standard
hardware or must software be used?
Is the requirement ambiguous, could
different persons read it in different ways?
What are the different interpretations for
the requirement?
Is the requirement realistic given the
technology that will used to implement the
system?
Does the description of a requirement
describe a single requirement or could it be
broken into several different requirements?
Has each requirement been assigned a
priority?
Are the system boundaries well defined?
Have the portability, reliability, usability
and maintainability requirements for the
system been respected?
Did you create a System Architecture
Model?
Did you develop a behavioral or structural
model for the system?
Is the Data Dictionary implemented and
correctly updated?
Is the requirement testable by the test
engineers?
Has the Interaction Matrix been filled out and the overlaps or conflicts reported in the
NCR form?
http://www.software-engineer.org
Requirements Analysis Checklist Instructions – Form RACI
http://www.software-engineer.org