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 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