World Library  
Flag as Inappropriate
Email this Article

Software requirements

Article Id: WHEBN0021168501
Reproduction Date:

Title: Software requirements  
Author: World Heritage Encyclopedia
Language: English
Subject: Software Engineering Body of Knowledge, Software construction, Requirements engineering, Software testability, Top development
Publisher: World Heritage Encyclopedia

Software requirements

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:[1]

  1. A condition or capability needed by a user to solve a problem or achieve an objective.
  2. 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.
  3. 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.[2]


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 can be used.[3] Issue trackers implementing the Volere requirements template have been used successfully in distributed environments.[4]

See also

Software Requirements Specification


  1. ^ IEEE Computer Society (1990). "IEEE Standard Glossary of Software Engineering Terminology". IEEE Standard. 
  2. ^ "Guide to the Software Engineering Body of Knowledge". IEEE Computer Society. Retrieved 11 January 2013. 
  3. ^ Laplante, Phillip A. (2009). "Requirements Engineering for Software and Systems". CRC Press. 
  4. ^ Prause, Christian; et al. (2008). "Managing the Iterative Requirements Process in a Multi-National Project using an Issue Tracker". IEEE Computer Society. Retrieved February 5, 2013. 

Further reading

External links

This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.

Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.