UML Weekend Crash Course™ - To Parent Directory

44
Friday Evening
In the effort to understand a problem statement, you were cautioned to watch out for some
common pitfalls:
Avoid making assumptions of any kind. Always challenge and confirm.
Be careful not to mistake user preferences for true requirements.
Watch out for the possibility that you are simply replacing the old system with a
duplicate in new attire (that is, a new platform or technology).
QUIZ YOURSELF
1. What is a problem statement (See “The Case Study Problem Statement.”)
2. What is a constraint (See “Constraints.”)
3. What is a rule (See “Rules.”)
4. When talking about requirements, what is a user (See “Identifying
requirements.”)
5. When talking about requirements, what is functionality (See “Identifying
requirements.”)
6. Why should you be skeptical of user preferences (See “Avoiding early pitfalls.”)