Requirements Engineering Activities
The sub-processes that are part of a general requirements engineering process vary widely, depending on the type of system being developed and the specific practice of the organization developing the requirements. Activities within the RE process may include:
- Requirements inception -
- Requirements identification - identifying new requirements
- Requirements analysis and negotiation - checking requirements and resolving stakeholder conflicts
- Requirements specification (Software Requirements Specification)- documenting the requirements in a requirements document
- System modeling - deriving models of the system, often using a notation such as the Unified Modeling Language
- Requirements validation - checking that the documented requirements and models are consistent and meet stakeholder needs
- Requirements management - managing changes to the requirements as the system is developed and put into use
These are sometimes presented as chronological stages although, in practice, there is considerable interleaving of these activities.
Read more about this topic: Requirements Engineering
Famous quotes containing the words engineering and/or activities:
“Mining today is an affair of mathematics, of finance, of the latest in engineering skill. Cautious men behind polished desks in San Francisco figure out in advance the amount of metal to a cubic yard, the number of yards washed a day, the cost of each operation. They have no need of grubstakes.”
—Merle Colby, U.S. public relief program (1935-1943)
“That is the real pivot of all bourgeois consciousness in all countries: fear and hate of the instinctive, intuitional, procreative body in man or woman. But of course this fear and hate had to take on a righteous appearance, so it became moral, said that the instincts, intuitions and all the activities of the procreative body were evil, and promised a reward for their suppression. That is the great clue to bourgeois psychology: the reward business.”
—D.H. (David Herbert)