Please respond to the following two questions about use cases: 1. In a complex s

Question

Please respond to the following two questions about use cases: 1. In a complex software-based project, the number of use cases can be daunting to document within the time constraints of the project. How would you decide how to prioritize the breadth and depth of what use cases to document? What factors most impact that decision? 2. Below are some use case traps to avoid. Choose one of them to discuss why you think it should be avoided - or if you disagree, why so. Too many use cases - one use case can be 2-3 person months to implement and often spans several screens/pages Use cases that are too complex - Use state diagrams for complex descriptions Attempting to associate every requirement with a use case Including user interface details- Concentrate on what the actor does, not how. Leave out things like confirmation steps. Use activity models to cross- check functionality

Explanation / Answer

Answer.) In complex software based project, it is really painfull and daunting to document each use cases, within the time frame of the project. In such cases we need to prioritize the depth of the project goal, to figure out what cases need to be prioritised and documented. The focus should be on the complete result and the milestone to be achieved. Based on these conditions, use cases can be documented and prioritised depending upon the time constraint. Use cases fulfilling the final goal, followed by partial goals should be documented and validated that, as per the outcomes, the goal is met and the milestone is complete. The key factors of effective use case documentation are time constraint, goal orientation, in depth problem prioritization and final outcome. These are the main key factors of an effective use case documentation.

Related Questions

Navigate

• Browse (All)
• Browse P
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.