Editing Requirements analysis (section)

{{Multiple issues|
{{more citations needed|date=December 2011}}
{{Prose|date=July 2022}}
}}
{{Use American English|date = March 2019}}
{{Short description|Engineering process}}
{{broader|Requirements engineering}}
[[File:SE Process.jpg|thumb|320px|A [[systems engineering]] perspective on requirements analysis<ref name="SEF01">[http://www.dau.mil/pubscats/PubsCats/SEFGuide%2001-01.pdf ''Systems Engineering Fundamentals''] {{webarchive|url=https://web.archive.org/web/20110722184431/http://www.dau.mil/pubscats/PubsCats/SEFGuide%2001-01.pdf |date=2011-07-22 }} Defense Acquisition University Press, 2001</ref>]]
{{software development process|Core activities}}

In [[systems engineering]] and [[software engineering]], '''requirements analysis''' focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting [[requirement]]s of the various [[Stakeholder (corporate)|stakeholders]], ''analyzing'', ''documenting'', ''validating'', and ''managing'' software or [[system requirements]].<ref>{{cite book|isbn=9780471972082|title=Requirements Engineering: Processes and Techniques|url=https://archive.org/details/requirementsengi1998koto|url-access=registration|last1=Kotonya|first1=Gerald|last2=Sommerville|first2=Ian|year=1998|location=Chichester, UK|publisher=John Wiley and Sons}}</ref>

Requirements analysis is critical to the success or failure of systems or [[Software project management|software projects]].<ref>{{cite book
 |editor1= Alain Abran |editor2=James W. Moore |editor3=Pierre Bourque |editor4=Robert Dupuis
| title = Guide to the software engineering body of knowledge|url = http://www.swebok.org
|access-date = 2007-02-08|edition=2004 |date=March 2005
 | publisher = IEEE Computer Society Press | location = Los Alamitos, CA | isbn = 0-7695-2330-7
 | chapter = Chapter 2: Software Requirements | chapter-url = http://www.computer.org/portal/web/swebok/html/ch2
 | quote = It is widely acknowledged within the software industry that software engineering projects are ''critically vulnerable when these activities are performed poorly.''
}}</ref> The requirements should be documented, actionable, measurable, testable,{{sfn | Project Management Institute | 2015 | loc=§6.3.2 | p=158}} traceable,{{sfn | Project Management Institute | 2015 | loc=§6.3.2 | p=158}} related to identified business needs or opportunities, and defined to a level of detail sufficient for [[Systems design|system design]].