Requirements engineering: Difference between revisions

From DTU ProjectLab
Jump to navigation Jump to search
Joh (talk | contribs)
No edit summary
Joh (talk | contribs)
No edit summary
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 engineering refers to the 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
* Requirements Elicitation

Revision as of 19:37, 13 November 2014

Requirements engineering refers to the 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


Overview

Where is requirements engineering used?

How to do requirements engineering

Summary

Description

Example of requirements engineering

Implementation

Additional reading material