Difference between revisions of "Software requirements"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) (First) |
Karl Jones (Talk | contribs) (Software development process) |
||
| Line 7: | Line 7: | ||
The activities related to working with software requirements can broadly be broken up into Elicitation, Analysis, Specification, and Management. | The activities related to working with software requirements can broadly be broken up into Elicitation, Analysis, Specification, and Management. | ||
| + | == See also == | ||
| + | |||
| + | * [[Software development process]] | ||
== External links == | == External links == | ||
* [https://en.wikipedia.org/wiki/Software_requirements Software requirements] @ Wikipedia | * [https://en.wikipedia.org/wiki/Software_requirements Software requirements] @ Wikipedia | ||
Revision as of 08:45, 4 June 2015
Software Requirements is a field within software engineering that 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
