Difference between revisions of "Test"
From SWEBOK
| Line 3: | Line 3: | ||
{{IntroSection|title=Introduction|body= | {{IntroSection|title=Introduction|body= | ||
The Software Requirements knowledge area (KA) | The Software Requirements knowledge area (KA) | ||
| − | is concerned with the elicitation, analysis, | + | 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 | + | |
| − | + | ||
It is widely acknowledged amongst researchers | It is widely acknowledged amongst researchers | ||
and industry practitioners that software projects | and industry practitioners that software projects | ||
| − | are critically vulnerable when the requirements- | + | are critically vulnerable when the requirements-related activities are poorly performed. |
| − | related activities are poorly performed. | + | |
Software requirements express the needs and | Software requirements express the needs and | ||
constraints placed on a software product that | constraints placed on a software product that | ||
Revision as of 22:01, 14 July 2015
Contents
Introduction
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.
