||It has been suggested that this article be merged into Requirements engineering. (Discuss) Proposed since February 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.
Elicitation is the gathering and discovery of requirements from stakeholders and other sources. A variety of techniques can be used such as joint application design (JAD) sessions, interviews, document analysis, focus groups, etc. Elicitation is the first step of requirements development.
Analysis is the logical breakdown that proceeds from elicitation. Analysis involves reaching a richer and more precise understanding of each requirement and representing sets of requirements in multiple, complementary ways.
Specification involves representing and storing the collected requirements knowledge in a persistent and well-organized fashion that facilitates effective communication and change management. Use cases, user stories, functional requirements, and visual analysis models are popular choices for requirements specification.
Validation involves techniques to confirm that the correct set of requirements has been specified to build a solution that satisfies the project's business objectives.
Requirements change during projects and there are often many of them. Management of this change becomes paramount to ensuring that the correct software is built for the stakeholders.
Tool support for requirements engineering
Specialized commercial tools for requirements engineering are Gatherspace, Rational RequisitePro, Doors, CaliberRM or QFDCapture, but also free tools like FreeMind and Concordion can be used. Issue trackers implementing the Volere requirements template have been used successfully in distributed environments.
- IEEE Computer Society (1990). "IEEE Standard Glossary of Software Engineering Terminology". IEEE Standard.
- "Guide to the Software Engineering Body of Knowledge". IEEE Computer Society. Retrieved 11 January 2013.
- Laplante, Phillip A. (2009). "Requirements Engineering for Software and Systems". CRC Press.
- Prause, Christian; et al. (2008). "Managing the Iterative Requirements Process in a Multi-National Project using an Issue Tracker" (PDF). IEEE Computer Society. Retrieved February 5, 2013.
- Wiegers, Karl (2002). Software Requirements (2nd ed.). Microsoft Press. ISBN 0-07-285059-0.
- Cockburn, Alistair (2001). Writing Effective Use Cases. Pearson Education. ISBN 0-201-70225-8.
- Leffingwell, Dean (2000). Managing Software Requirements: A Unified Approach. Addison-Wesley Professional. ISBN 0-201-61593-2.