01.11.2017 Views

BABOK_Guide_v3_member_copy

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Validate Requirements<br />

Requirements Analysis and Design Definition<br />

• adding examples where appropriate for clarification.<br />

.3 Checklists<br />

Checklists are used for quality control when verifying requirements and designs.<br />

Checklists may include a standard set of quality elements that business analysts<br />

use to verify the requirements, or they may be specifically developed to capture<br />

issues of concern. The purpose of a checklist is to ensure that items determined to<br />

be important are included in the final requirements deliverables, or that steps<br />

required for the verification process are followed.<br />

7.2.5 <strong>Guide</strong>lines and Tools<br />

Complimentary IIBA® Member Copy. Not for Distribution or Resale.<br />

7.2.6 Techniques<br />

7.2.7 Stakeholders<br />

• Requirements Life Cycle Management Tools: some tools have functionality<br />

to check for issues related to many of the characteristics, such as atomic,<br />

unambiguous, and prioritized.<br />

• Acceptance and Evaluation Criteria: used to ensure that requirements are<br />

stated clearly enough to devise a set of tests that can prove that the<br />

requirements have been met.<br />

•Item Tracking: used to ensure that any problems or issues identified during<br />

verification are managed and resolved.<br />

• Metrics and Key Performance Indicators (KPIs): used to identify how to<br />

evaluate the quality of the requirements.<br />

•Reviews: used to inspect requirements documentation to identify requirements<br />

that are not of acceptable quality.<br />

• All stakeholders: the business analyst, in conjunction with the domain and<br />

implementation subject matter experts, has the primary responsibility for<br />

determining that this task has been completed. Other stakeholders may<br />

discover problematic requirements during requirements communication.<br />

Therefore, all stakeholders could be involved in this task.<br />

7.2.8 Outputs<br />

• Requirements (verified): a set of requirements or designs that is of sufficient<br />

quality to be used as a basis for further work.<br />

7.3 Validate Requirements<br />

7.3.1 Purpose<br />

The purpose of Validate Requirements is to ensure that all requirements and<br />

144

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!