Scribd
Upload
49 views2 pages

Use Case Requirements Validation Checklist

The document provides a checklist for validating use case requirements. It includes items to check for the general description of the use case, pre-conditions, basic flow, alternate flows, exception flows, and post-conditions. Finally, it lists follow-on activities after sign-off, such as updating traceability, resolving issues, and making final documentation available.

Uploaded by

cloudtraining2023
Copyright
© © All Rights Reserved
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
49 views2 pages

Use Case Requirements Validation Checklist

The document provides a checklist for validating use case requirements. It includes items to check for the general description of the use case, pre-conditions, basic flow, alternate flows, exception flows, and post-conditions. Finally, it lists follow-on activities after sign-off, such as updating traceability, resolving issues, and making final documentation available.

Uploaded by

cloudtraining2023
Copyright
© © All Rights Reserved
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

Use Case Requirements Validation Checklist

General

□ Unique name

□ Reflects the functional role and purpose of the use case

□ Includes all relevant actors

□ Avoids ambiguities, omissions, and impreciseness

Pre-Conditions

□ Explicit

□ Describes the state of the system when the use case begins, including data that must exist as well
as data that must not exist

□ Captures a valid business situation

Basic Flow

□ Consistent and compliant with relevant business rules

□ Includes only information that is relevant to the use case

□ Includes no references to other use cases that include this use case

□ Includes events in the correct order

□ References named alternate and exception flows at the appropriate points

□ References non-functional requirements that are specific to the use case, as applicable

□ Uses actor names instead of pronouns

□ Avoids the use of adverbs, adjectives, pronouns, synonyms, and negatives

□ Uses the present tense throughout

□ Avoids the use of design terms, such as user interface design or database design terms, including
but not limited to: click, button, screen, record, table, database, process, data, information

Corporate Education Group • 1 Executive Drive, Suite 301 • Chelmsford, MA 01824-2558 • USA
1.800.288.7246 (US only) or +1.978.649.8200 • www.corpedgroup.com
© 2012 Corporate Education Group, operated by Vatterott Educational Centers, Inc. All Rights Reserved.
Alternate Flows

□ Named

□ Comprehensive

□ Correctly state its starting point in the basic flow

□ Last step indicates the returning point within the basic flow

Exception Flows

□ Named

□ Correctly states starting point in the basic flow

□ Comprehensive

Post-Conditions

□ Explicit

□ Captures a valid business situation

□ Describes the state of the system when the use case ends, including data that must exist as well as
data that must not exist

Process: Follow-On Activities

□ Use case and associated documents are considered “final documentation” after sign-off has
occurred
 Traceability is updated, up to the applicable test case/script

 Issues are assigned to appropriate parties and if necessary added to the project issue
database
 Final documentation is copied and made available in a document repository

Extracted from BA112: Plan, Manage, and Communicate Requirements

Corporate Education Group • 1 Executive Drive, Suite 301 • Chelmsford, MA 01824-2558 • USA
1.800.288.7246 (US only) or +1.978.649.8200 • www.corpedgroup.com
© 2012 Corporate Education Group, operated by Vatterott Educational Centers, Inc. All Rights Reserved.

You might also like