UseCase

Collect requirements centred on ways that the system is to be used

Definition

Collect requirements centred on ways that the system is to be used. Each distinct reason that a user has to turn to the system and get it to do something to aid his work is a potential UseCase.

Source

Discussion

Whole books have been written on Use Cases and how to write them effectively. An important point to remember is that ‘Use requirements’ are only one of about 6 forms of requirement that need to be elicited and collected; the list will vary with differing taxonomy. In addition to Use requirements, there are Non-functional requirements, Business Rules, Design Preferences, Standards and Domain Invariants. UseCases are tailored for collecting Use requirements, and are particularly appropriate as a major form of requirements capture because they readily transform to SessionFacade scripts. See also IntentStatement.