Requirements Modelling
Building models of the requirements can one of the fastest ways of obtaining a view of the requirements.
At the analysis stage, it is important to remember that the models are generally a means to an end rather than an end in themselves; more precise models on which to base a design can subsequently be developed.
It is important to develop the models as a team typically working 'in the large' on a whiteboard or similar surface. Once a modelling session is complete, one member of the team can capture it on a purpose built modelling tool. The subsequent modelling session can beging with a projection of the diagrams from the tool onto a screen. Models should normally be developed iteratively, but quickly; this allows time for consensus and reflection, whilst at the same time maintaining pace and motivation.
Users in particular may be demotivated if they do not see something definite in a reasonably short period of time. Prototypes may satisfy this need. They can be generated from the models, either automatically or manually. This allows users to check their understanding of the requirements and to ensure that there is mutual agreement.
At Capiro, we believe that it is important that the analyst is flexible in their use of models. Informal models can be very effective and perhaps less intimidating to certain users. Always use modelling techniques that are appropriate to the problem at hand, rather than always applying the same technique just because you are familiar with it or because it is part of a standard methodology.
Capiro offers support for modelling in the form of consultancy, training and direct project involvement.
See also
- UML2 (Unified Modelling Language)
- Business process modelling
- Use case modelling
- Class modelling
- State modelling
- Activity modelling