Posted by cadsmith on December 5, 2007
“Use Case Modeling”, Bittner and Spence, 2002, 368pp, shows how a system will work in an understandable fashion. These are defined in addition to detailed, but less clear, requirements and features. They include procedures, actors and relationships and are often illustrated, e.g. by UML charts. Basic components include actors such as anything that cannot be controlled, use case interactions to achieve a goal, and descriptions of the event flow, exception and error conditions, and optional behaviors. A vision is created by finding out who the stakeholders are that are affected by the system outcome, selecting a representative and involving them in the project, then issuing a problem statement and description of the features, requirements and constraints. Detail is applied to finding actors and cases possibly in a workshop. The use case is reviewed and used in each phase of a software life cycle including requirements, development and testing. There are techniques that a team can use for these and to agree on system scope issues concerning customer priority, architectural significance, and operational capability. Areas of instability can be authored using supplementary specifications. Authors are skilled at synthesis, systematic approaches to problem-solving, a level of domain knowledge, some understanding of software development, and writing. Tips, traps and techniques are shown for definition, writing and review, such as storyboards of screenshots. The rational unified process is discussed under iterative development. Cases can be evaluated for completeness, coverage and traceability. Wiki page. There are tools for this available, e.g. free UML editor, requirements specification, or open-source verification. Also see UModel video.