Difference between revisions of "Test"
Line 5: | Line 5: | ||
is concerned with the elicitation, analysis, specification, and validation of software requirements | is concerned with the elicitation, analysis, specification, and validation of software requirements | ||
as well as the management of requirements during the whole life cycle of the software product. | as well as the management of requirements during the whole life cycle of the software product. | ||
+ | |||
It is widely acknowledged amongst researchers | It is widely acknowledged amongst researchers | ||
and industry practitioners that software projects | and industry practitioners that software projects | ||
Line 11: | Line 12: | ||
constraints placed on a software product that | constraints placed on a software product that | ||
contribute to the solution of some real-world | contribute to the solution of some real-world | ||
− | problem.}} | + | problem. |
+ | |||
+ | The term “requirements engineering” is widely | ||
+ | used in the field to denote the systematic handling | ||
+ | of requirements. For reasons of consistency, the | ||
+ | term “engineering” will not be used in this KA | ||
+ | other than for software engineering per se. | ||
+ | For the same reason, “requirements engineer,” | ||
+ | a term which appears in some of the literature, | ||
+ | will not be used either. Instead, the term “software | ||
+ | engineer” or, in some specific cases, “require- | ||
+ | ments specialist” will be used, the latter where | ||
+ | the role in question is usually performed by an | ||
+ | individual other than a software engineer. This | ||
+ | }} | ||
== Section 1 == | == Section 1 == | ||
=== Subsection === | === Subsection === |
Revision as of 22:02, 14 July 2015
Contents
The Software Requirements knowledge area (KA) is concerned with the elicitation, analysis, specification, and validation of software requirements as well as the management of requirements during the whole life cycle of the software product.
It is widely acknowledged amongst researchers and industry practitioners that software projects are critically vulnerable when the requirements-related activities are poorly performed. Software requirements express the needs and constraints placed on a software product that contribute to the solution of some real-world problem.
The term “requirements engineering” is widely used in the field to denote the systematic handling of requirements. For reasons of consistency, the term “engineering” will not be used in this KA other than for software engineering per se. For the same reason, “requirements engineer,” a term which appears in some of the literature, will not be used either. Instead, the term “software engineer” or, in some specific cases, “require- ments specialist” will be used, the latter where the role in question is usually performed by an individual other than a software engineer. This