Application requirements must be
captured in a way that they can be read, understood and signed off by the user,
but at the same time be in a format that can be passed through to analysis and
To meet this demand, requirements
are captured using use case methodology. The system is broken
down into business processes called 'use cases'. These use cases describe the
business processes in a logical manner and in a way that provides visibility to
the user and allows them to confidently sign off the system specification.
The use cases along with
supporting documents form the Use Case Model. This acts as the contract with
the user, describing the complete functionality of the system. The Use Case
Model also forms the basis for design, and later in the iteration is used to
define test cases and test procedures to ensure developed functionality meets
business and user requirements.