Editing Use case (section)

=== Variations ===
There are different kinds of use cases and variations in the technique:

* System use cases specify the requirements of a system to be developed.<ref name=":2" /> They identify in their detailed description not only the interactions with the actors but also the entities that are involved in the processing. They are the starting point for further analysis models and design activities. 
* Business use cases focus on a business organization instead of a software system. They are used to specify business models and business process requirements in the context of business process reengineering initiatives.<ref name=":4" /> 
* Essential use cases, also called abstract use cases, describe the potential intents of the actors and how the system addresses these, without defining any sequence or describing a scenario.<ref name=":6" /> This practice was developed with the aim of supporting the user-centric design and avoiding to induce bias about the user interface in the early stage of the system specifications.<ref name=":5" /> 
* Use Case 2.0 to adapt the technique for the context of agile development methods.<ref name=":1" /> This technique enriches the requirement-gathering practice with support for user-story narratives. It also provides use case "slices" to facilitate incremental elicitation of requirements and enable incremental implementation.