Difference between revisions of "Software requirements"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) (→See also) |
Karl Jones (Talk | contribs) (→See also) |
||
| Line 11: | Line 11: | ||
== See also == | == See also == | ||
| + | * [[Quality assurance]] | ||
* [[Computer programming]] | * [[Computer programming]] | ||
* [[Software development process]] | * [[Software development process]] | ||
Revision as of 08:47, 28 August 2015
In software engineering, software requirements deals with establishing the needs of stakeholders that are to be solved by software.
The IEEE Standard Glossary of Software Engineering Technology defines a software requirement as:
- A condition or capability needed by a user to solve a problem or achieve an objective.
- A condition or capability that must be met or possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document.
- A documented representation of a condition or capability as in 1 or 2.
The activities related to working with software requirements can broadly be broken up into Elicitation, Analysis, Specification, and Management.
See also
External links
- Software requirements @ Wikipedia
