Next: State Models Up: Use Cases Previous: Use Case descriptions edition Contents
Selection of Use Case Validation in theValidate menu launches the current Use Case model validation. Use Case model validation checks the following.
- Use case model elements must be unique. There shouldn't be any duplicate use case or actor.
- All include and extend relation must refer to normal use cases
- There must not be cycles of use cases inclusion.
- A use case Primary Actor must be a domain Concept.
- A use case Precondition must be a valid condition.
- the syntax must conform to condition syntax,
- the entities used must be present in the domain model (as System Concepts, Concepts or Attributes),
- the discrete values used in must be defined as possible values of the corresponding entities,
- if a general comparison is used as value in a condition, the entity in that condition must have no possible value defined.
- A use case Postcondition must be a valid condition (same as preconditions).
- Use Case steps must follow the use case syntax.
- When an after delay and a before delay are used in conjunction, the delay value of the before delay must be greater than the delay value of the after delay.
- Step conditions must be valid conditions.
- Operation instances must be present in the domain model.
- Use case inclusion operations must refer to normal use cases.
Next: State Models Up: Use Cases Previous: Use Case descriptions edition Contents