Sample Checklist for Use Case Diagrams Completeness Are

Sample Checklist for Use Case Diagrams Completeness - Are all business scenarios captured by use cases? - Are gaps in the activity graph, i. e. missing action states / transitions? - Is a pre- and post-condition defined for each use case and each action? - Are all affected classes contained in the class scope of an action? Correctness - Does the pre- and post-condition of each use capture a legal business situation? - Does the specification of each use case comply with the corresponding business rule(s)? - Is the expected outcome of a scenario reflected correctly by the postcondition(s) of the final action(s)? Consistency - Do different scenarios exist for the same initial object constellation? - Does the post-condition of each action imply the disjunction of the guards of its outgoing edges?

Sample Checklist for Class Diagrams Completeness - Is every class contained in at least one class scope? - Is every interaction mapped to a root operation? - Are all classes in the signature of a root operation contained in the class scope of the corresponding interaction(s)? Correctness - Does the pre-condition of the interaction imply the pre-condition of the root operation? - Does the post-condition of the root operation imply the post-condition of the interaction? - If an edge e of an activity graph is traversed by a scenario, does its guard c(e) hold for the actual object constellation? - Is the class scope of the macro action a subset of the class scope of the referenced activity graph? Consistency - Are the interaction specifications compatible with the class scopes and the specifications of the root operations? - Does an interaction and a concrete object constellation allow different interaction sequences? - Is an operation a root operation for different interactions? - Does the post-condition of each non-final interaction imply the disjunction of its outgoing edge guards? - Does an object constellation violate an association multiplicity? - Are there usage anomalies in interaction sequences (create-delete, write-write, deleteread, . . . )?