Requirements Engineering


Also found in: Acronyms.

requirements engineering

[ri¦kwīr·məns ‚en·jə¦nir·iŋ]
(systems engineering)
The process of identifying and articulating needs for a new technology and applications.
McGraw-Hill Dictionary of Scientific & Technical Terms, 6E, Copyright © 2003 by The McGraw-Hill Companies, Inc.

Requirements Engineering

(programming)
The task of capturing, structuring, and accurately representing the user's requirements so that they can be correctly embodied in systems which meet those requirements (i.e. are of good quality).

DOORS is one product to help with this task.
This article is provided by FOLDOC - Free Online Dictionary of Computing (foldoc.org)
References in periodicals archive ?
However, researchers are actually attempting to utilize numerous techniques of requirements engineering to analyze the specification of data warehouse systems in order to avoid the risk of failure.
On the engineering of systems of systems: Key challenges for the requirements engineering community!
The requirements engineering community has classified the requirements of a software system into two main categories: functional requirements and nonfunctional requirements [8].
In the context of IT enabled urban governance, this paper attempts to address and answer the research question "to what extent does a generic requirements engineering process usefully support the identification of common user defined requirements for the development of generic IT-enabled urban policy-making, planning and collaborative decision-making solutions applicable to many cities?".
The third updated edition of Software Requirements provides proven techniques for requirements engineering processes and has been completely updated and expanded to reflect the latest engineering protocols and examples.
Moustapha Tadlaoui, this new US office will carry the leading requirements engineering solution, Visure Requirements, into both North and South America.
Requirements engineering is the practice of eliciting, analyzing, prioritizing, negotiating, and specifying the requirements for a software-intensive system (Roberts0n and Robertson 1999).

Full browser ?