The case is further detailed with a textual description or with additional graphical models that explain the general sequence of activities and events, as well as variants such as special conditions, exceptions, or error situations.Īccording to the Software Engineering Body of Knowledge (SWEBOK), use cases belong to the scenario-based requirement elicitation techniques, as well as the model-based analysis, techniques. In the requirement analysis, at their identification, a use case is named according to the specific user goal that it represents for its primary actor. Actors represent the role that human users or other systems have in the interaction. A use case corresponds to a set of behaviors that the system may perform in interaction with its actors, and which produces an observable result that contributes to its goals. Use cases are a technique for capturing, modeling, and specifying the requirements of a system. In 2011, Jacobson published with Ian Spence and Kurt Bittner the ebook Use Case 2.0 to adapt the technique to an agile context, enriching it with incremental use case "slices", and promoting its use across the full development lifecycle after having presented the renewed approach at the annual IIBA conference. Since then, many authors have contributed to the development of the technique, notably: Larry Constantine developed in 1995, in the context of usage-centered design, so called "essential use-cases" that aim to describe user intents rather than sequences of actions or scenarios which might constrain or bias the design of user interface Alistair Cockburn published in 2000 a goal-oriented use case practice based on text narratives and tabular specifications Kurt Bittner and Ian Spence developed in 2002 advanced practices for analyzing functional requirements with use cases Dean Leffingwell and Don Widrig proposed to apply use cases to change management and stakeholder communication activities Gunnar Overgaard proposed in 2004 to extend the principles of design patterns to use cases. The resulting Unified Process was published in 1999 and promoted a use case driven approach. Jacobson, Booch and Rumbaugh also worked on a refinement of the Objectory software development process. UML was standardized by the Object Management Group (OMG) in 1997. In 1995 Ivar Jacobson joined them and together they created the Unified Modelling Language (UML), which includes use case modeling. Īt the same time, Grady Booch and James Rumbaugh worked at unifying their object-oriented analysis and design methods, the Booch method and Object Modeling Technique (OMT) respectively. In 1994 he published a book about use cases and object-oriented techniques applied to business models and business process reengineering. In 1992 he co-authored the book Object-Oriented Software Engineering - A Use Case Driven Approach, which laid the foundation of the OOSE system engineering method and helped to popularize use cases for capturing functional requirements, especially in software development. Originally he had used the terms usage scenarios and usage case – the latter a direct translation of his Swedish term användningsfall – but found that neither of these terms sounded natural in English, and eventually he settled on use case. He described how this technique was used at Ericsson to capture and specify requirements of a system using textual, structural, and visual modeling techniques to drive object-oriented analysis and design. In 1987, Ivar Jacobson presented the first article on use cases at the OOPSLA'87 conference. The detailed requirements may then be captured in the Systems Modeling Language (SysML) or as contractual statements. In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals. The actor can be a human or another external system. A potential scenario in which a system receives an external request (such as user input) and responds to it.Ī use case is a list of actions or event steps typically defining the interactions between a role (known in the Unified Modeling Language (UML) as an actor) and a system to achieve a goal.A usage scenario for a piece of software often used in the plural to suggest situations where a piece of software may be useful.In software and systems engineering, the phrase use case is a polyseme with two senses:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |