Requirements engineering
| Line 1: | Line 1: | ||
| − | + | As part of systems engineering - requirements engineering is an important phase of the developing process of creating a new product, system or service. Often for a project to begin, a document specifying the formalities needs to be created in order to create common understanding among involved parties in a project. | |
| + | The requirements specify the needs and conditions from a client to help developers understand the goal of the product and the need it is fulfilling. | ||
| + | The developers creates the requirements on the basis of the needs, to specific what the product is suppose to do and how it is going to do it. | ||
| + | Requirements engineering is regarded as crucial in the development of product, because the outcome often creates the basis to get financial support. It’s basically the formal link between stakeholders and developers. | ||
| + | The requirements can be created either by the stakeholder who wants something built as well as it can be the developer’s responsibility. Requirements engineering is considered a iterative process, so the requirements reflect a product best possible. | ||
| + | |||
| + | The process of specifying a document with requirement is as follows: | ||
* Requirements Elicitation | * Requirements Elicitation | ||
| Line 8: | Line 14: | ||
* System structre modeling | * System structre modeling | ||
* Function and process modeling | * Function and process modeling | ||
| − | * | + | * Requirement Quality Assurance |
| − | * | + | * Requirement Management |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 11:36, 14 November 2014
As part of systems engineering - requirements engineering is an important phase of the developing process of creating a new product, system or service. Often for a project to begin, a document specifying the formalities needs to be created in order to create common understanding among involved parties in a project. The requirements specify the needs and conditions from a client to help developers understand the goal of the product and the need it is fulfilling. The developers creates the requirements on the basis of the needs, to specific what the product is suppose to do and how it is going to do it. Requirements engineering is regarded as crucial in the development of product, because the outcome often creates the basis to get financial support. It’s basically the formal link between stakeholders and developers. The requirements can be created either by the stakeholder who wants something built as well as it can be the developer’s responsibility. Requirements engineering is considered a iterative process, so the requirements reflect a product best possible.
The process of specifying a document with requirement is as follows:
- Requirements Elicitation
- Design and validation
- Context
- Specifying features (functional requirements)
- Specifying quality attributes (non-functional requirements)
- System structre modeling
- Function and process modeling
- Requirement Quality Assurance
- Requirement Management
