Requirements engineering
From apppm
(Difference between revisions)
(Created page with " = Overview = == Where is requirements engineering used? == == How do i do requirements engineering? == == Summary == = Description = = Example of requirements engineer...") |
|||
| Line 1: | Line 1: | ||
| + | Requirements engineering refers to the development process of specifying and documenting a system or product under development. The requirements creates an common understanding among all parties involved in developing an system or product. The process of specifying the 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 | ||
| + | * Requirements QA | ||
| + | * Requirements Management | ||
| Line 5: | Line 16: | ||
== Where is requirements engineering used? == | == Where is requirements engineering used? == | ||
| − | == How | + | == How to do requirements engineering == |
== Summary == | == Summary == | ||
Revision as of 20:36, 13 November 2014
Requirements engineering refers to the development process of specifying and documenting a system or product under development. The requirements creates an common understanding among all parties involved in developing an system or product. The process of specifying the 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
- Requirements QA
- Requirements Management
Contents |
