Requirements analysis
The requirements analysis (English requirements analysis) is in the computer science part of the system development process (including in addition to the requirements management ), as well as a part of business analysis. The aim is to identify the requirements of the client to the system to be developed to structure and consider.
- 2.1 identify, analyze
- 2.2 Structuring and vote
- 2.3 Testing and evaluation
Definitions
IEEE
According to IEEE, the requirements engineering in requirements elicitation ( requirements elicitation ), requirements analysis ( requirements analysis), requirements specification ( requirements specification ) and request evaluation ( requirements validation ) are divided. These steps overlap each other and are often several times - iteratively - performed.
SEI, Carnegie Mellon
The Software Engineering Institute of Carnegie Mellon University distinguishes the management of requirements and the development of requirements in its Capability Maturity Model Integration.
Volere
In the process model developed by Robertson Volere requirements specification, stakeholder analysis, requirements analysis, analysis of the prioritization and the recording of the elementary requirements exist.
IIBA
The International Institute of Business Analysis leads to this issue in the Business Analysis Body of Knowledge three chapters on: requirements analysis ( requirements of the stakeholders determine ), Requirements Management Manage & communication (requests and communicate, identifying reusable requirements, put together requirements, prepare requests for approval change to Requirements manage ), prioritize requirements analysis (requirements, structuring, documenting requirements in text form, document requirements with graphics / models, check for content quality, inspected for compliance with the objectives ).
Procedure
In all the above models, the following steps, in one form or another exist. It needs to be collected (English elicitation ), it is by analyzing a common understanding can be established, the requirements have written down or recorded in models, that is to be specified. After that is usually examined whether the whole thing is still consistent (English validation ). Around these steps, there is a management of the process, management.
Identification, analysis
When collecting requirements (English elicitation ) is the translation process between technical side and developers of special importance. The following criteria must be met:
The result of the requirements analysis is a list of requirements. This can, for example, be converted into a specification.
Structuring and coordination
After detection of a structure and classification of the requirements must be made. This is achieved, that the requirements are clearer. This in turn increases the understanding of the relationships between the requirements. Relevant criteria are:
Further structuring possibilities are functional and non-functional requirements as well as professionally motivated ( professional and technical ) and technically motivated (only technical ) requirements. The so structured requirements must then be agreed between customer and developer. This coordination may be optionally to an iterative process that results in the refinement of requests.
Testing and evaluation
After patterning, partly parallel to the quality assurance of requirements is done according to these quality features:
The result of the examination is the basis for the specification represents the ratings are partly competing with each other. A high prioritization of tasks provides only this is not automatically a productive system in realization. When evaluating not only the single function for themselves, but also their interaction in the overall system is considered.