Editing Use case (section)

=== Usage ===
Use cases are known to be applied in the following contexts:

* [[Object-oriented software engineering|Object Oriented Software Engineering (OOSE)]], as driving element;<ref name=":3" />  
* [[Unified Modeling Language]] (UML), as a behavioral modelling instrument;<ref name=":9" /> 
* [[Unified Process|Unified Software Development Process (UP)]] and its fore-runner, the [[IBM]] [[Rational Unified Process|Rational Unified Process (RUP)]];<ref name=":5" />
* up-front documentation of [[software requirements specification]] (SRS), as an alternative structure for the functional requirements;<ref>{{Cite book|last=Wiegers, Karl Eugene|title=More about software requirements: thorny issues and practical advice|date=2010|publisher=Microsoft Press|isbn=978-0-7356-2267-8|pages=Chapter 11|oclc=73814167}}</ref>
* deriving the design from the requirements using the [[entity–control–boundary]] approach;<ref name=":5" />
* and [[agile software development|agile development]].<ref name=":1" /><ref>{{Cite web|last=Ambler, Scott|author-link=Scott Ambler|date=2004|title=System Use Cases: An Agile Introduction|url=http://agilemodeling.com/artifacts/systemUseCase.htm|access-date=16 August 2020|website=agilemodeling.com}}</ref>