<p>Use Case Requirements Validation Checklist</p><p>General</p><p>□ Unique name </p><p>□ Reflects the functional role and purpose of the use case</p><p>□ Includes all relevant actors</p><p>□ Avoids ambiguities, omissions, and impreciseness</p><p>Pre-Conditions</p><p>□ Explicit</p><p>□ Describes the state of the system when the use case begins, including data that must exist as well as data that must not exist</p><p>□ Captures a valid business situation</p><p>Basic Flow</p><p>□ Consistent and compliant with relevant business rules</p><p>□ Includes only information that is relevant to the use case</p><p>□ Includes no references to other use cases that include this use case</p><p>□ Includes events in the correct order</p><p>□ References named alternate and exception flows at the appropriate points</p><p>□ References non-functional requirements that are specific to the use case, as applicable</p><p>□ Uses actor names instead of pronouns</p><p>□ Avoids the use of adverbs, adjectives, pronouns, synonyms, and negatives</p><p>□ Uses the present tense throughout</p><p>□ 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</p><p>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</p><p>□ Named</p><p>□ Comprehensive</p><p>□ Correctly state its starting point in the basic flow </p><p>□ Last step indicates the returning point within the basic flow</p><p>Exception Flows</p><p>□ Named</p><p>□ Correctly states starting point in the basic flow</p><p>□ Comprehensive</p><p>Post-Conditions</p><p>□ Explicit</p><p>□ Captures a valid business situation</p><p>□ Describes the state of the system when the use case ends, including data that must exist as well as data that must not exist</p><p>Process: Follow-On Activities</p><p>□ 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</p><p> Final documentation is copied and made available in a document repository</p><p>Extracted from BA112: Plan, Manage, and Communicate Requirements </p><p>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.</p>