Final answer:
The answer is A. Including data definitions in the use cases. Use case traps are common mistakes or pitfalls when developing use cases. Examples of use case traps include including design in use cases, highly complex use cases, use cases that users don't understand, too many use cases, and depicting too much detail in the use case story.
Step-by-step explanation:
The correct answer is A. Including data definitions in the use cases.
Use case traps are common mistakes or pitfalls that can occur when developing use cases, which are a way to capture functional requirements in software development projects.
Some examples of use case traps include:
- Including design in the use cases: Use cases should focus on describing the desired functionality of the system, not the implementation details.
- Highly complex use cases: Use cases should be simple and represent a single, clear action or interaction with the system.
- Use cases that users don't understand: Use cases should be written in a way that is easily understandable by the intended users of the system.
- Too many use cases: Use cases should be kept to a manageable number and not become overwhelming or difficult to maintain.
- Depicting too much detail in the use case story: Use case stories should focus on the main steps and interactions without going into unnecessary detail.