Scribd
Upload
383 views2 pages

Requirements Analysis Checklist - Form RAC: Name: Team #: Company Name: Project Name: Date: Phase: Analysis

The document is a requirements analysis checklist used to ensure requirements elicitation and analysis phases are completed thoroughly for each requirement. It includes questions to determine if requirements are adequately defined, testable, realistic given available technology, and do not conflict with other system aspects. Project teams are instructed to fill out the checklist for each requirement before finalizing requirements documentation.

Uploaded by

Bhargava Sreenivasan
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
383 views2 pages

Requirements Analysis Checklist - Form RAC: Name: Team #: Company Name: Project Name: Date: Phase: Analysis

The document is a requirements analysis checklist used to ensure requirements elicitation and analysis phases are completed thoroughly for each requirement. It includes questions to determine if requirements are adequately defined, testable, realistic given available technology, and do not conflict with other system aspects. Project teams are instructed to fill out the checklist for each requirement before finalizing requirements documentation.

Uploaded by

Bhargava Sreenivasan
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

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

Purpose • Helps the requirement engineer to make sure that the


Elicitation/Analysis phases have been correctly carried out and that
these phases are complete for each requirement.
General • Fill this form before starting the document redaction.
• Use one form for each requirement.
Header Enter
• Your name, the team number, the company’s name.
• The project name, the date and the phase
Req. # • Enter the requirement number you are referring to
List of • Answer to each one of the questions
questions
Yes • If the answer is YES, you can go to the next question.
No • If the answer is NO, you must explain why and report the reason for
the contradiction in the Negotiation/Conflict Resolution Template.

http://www.software-engineer.org

You might also like