Define Requirements
Requirements for the new business system need to be gathered and will come in many forms from a range of sources, including stakeholders. They will often need to be ‘cleansed’ as they can be ambiguous, conflicting or vague. It is best practice to document and store them in a standard way across the organisation. The level of detail and specific content will depend on a number of factors, including local policy, lifecycle for delivery, structure of development team, the level to which requirements apply, the relationships between requirements and any supporting models. Requirements documentation can be long or short, but will often include:
- Introduction and background;
- Process maps;
- Function models (e.g. use case diagrams);
- Data models (e.g. class models);
- Requirements catalogue; and
- Glossary of terms.
Related Content