Made with
ConceptDraw
DIAGRAM 17

Jacobson Use Cases Diagram

In systems engineering as well as in software engineering, a “use case” is a list of event steps or actions, typically defining the interactions between a “role” and a system in order to achieve a goal. The “actor” can be some person or any other representative of the external system. In the systems engineering, use cases are usually deployed at a higher level than within the software engineering itself, representing missions or goals, so-called “stakeholder goals”. The requirements after can be captured in the SysML or as the contractual statements. The analysis of the “use cases” in a very important technique, which is used in the software engineering since 1992. “Use case driven development” is the main characteristic of so many different process models as well as the frameworks, for example, the Unified Process (UP), ICONIX, the IBM Rational Unified Process known as RUP, as well as the method called “Oracle Unified Method” or “OUM”.

The textual, visual and structural modelling techniques were first formulated by Ivar Jacobson in 1986 for the purpose of specifying the term of the “use cases”. In 1992 Ivar Jacobson’s co-authored the book called “Object-Oriented Software Engineering - A Use Case Driven Approach” that helped him to popularize the technique for capturing the so-called “functional requirements”, partially used in the software engineering development. Since then, other experts have also contributed their additions to the technique. Among them there were Larry Constantine, Alistar Cockburn, Dean Leffingwell, Gunnar Overgaard and Kurt Bittner.

In 2011, Jacobson published an update to his work and he called it “Use Case 2.0”. His intention was to incorporate different practical experiences of him in applying use cases since the original inception of the concept. Jacobson’s partner Cockburn describes a better, more detailed structure, for a use case, although he permits it to be more simplified in case there are fewer details, which might be needed to mention. His use case template can be applied in the fields, such as “Primary Actor”, “Title: "an active-verb goal phrase that names the goal of the primary actor", “Goal in Context”, “Scope”, “Level”, “Stakeholders and Interests”, “Precondition”, “Minimal Guarantees”, “Success Guarantees”, “Trigger”, “Main Success Scenario”, “Extensions” and “Technology and Data Variations List”.

Cockburn also suggested using two devices for the nature of each use case indication, such as icons for goal level and design scope. Cockburn approach has also influenced the other authors, such as Beus-Dukic, who develops the so called “fully dressed use case” template. But their fields were different from Cockburn and they were “Variation scenarios”, “Exceptions” (for example, the exception events as well as their exception-handling scenarios), etc. They insisted on the use cases being not only texts but also diagrams, in case it is needed. The relationships between use cases and actors in the Unified Modelling Language are represented in a way of the use case diagrams, which are originally based upon Ivar Jacobson’s so-called “Objectory notation”.

In order to visualize use cases, the other UML diagrams can be used. Among them there are “sequence diagrams”, “communication diagrams”, “state machine diagrams” and “activity diagrams”. In general, a so-called “System Sequence Diagram” or “SSD” is the one being used in order to show the interactions between the system under design (SuD) and the external actors. The most common reason for showing that is visualizing a particular scenario of a use case or use cases.

Conducting the use case analysis means drawing the use case diagrams as the first step of this process. For simple and small project use a model of a few UML diagrams can be used. Such diagrams may depict the use cases as well as a few textual descriptions. The visual diagram representations of use cases are also very effective in terms of facilitating the better understanding, design of some complex system and communication.

There are many benefits of using the use cases as they, first of all, constitute a user-centric tool for the software requirements specification processes. Their modelling usually starts from identifying the key stakeholder roles or actors, interacting with the system. The goals and objectives, which the system must fulfill, have to be clarified at the very first stage. Such goals and objectives become the ideal candidates for the titles of the use cases afterwards, representing the desired functional features provided by the system.

Use cases are often written in natural languages with the structured templates as this narrative textual form foster better communications among all stakeholders (including end-users, customers, developers, managers as well as testers). The better way of communication results in quality requirements and thus these quality systems are delivered. Another powerful thing about use cases resides in the formats of the use case samples, the main success scenario known as “basic flow” and the extension scenario fragments in particular. Analyzing any use case step by step, as well as investigating and exploring every action step of the use case flows from its very basic form to the different extensions, for identifying those tricky and often costly requirements, is one of the structured and beneficial ways to get clear, as well as stable and quality requirements on a systematic basis.

Using ConceptDraw DIAGRAM software for making the previously described in detail use case diagrams is one of the best options available nowadays. The reason of this software being so popular today is that it allows having the examples of already previously created diagrams which all can be used while creating your own ones. For example, if you have no idea of where to start from and what to do in order to make a great looking use case diagram, then you can simply find the template of it in one of the solutions, available for all of the ConceptDraw DIAGRAM users. In this case the “Rapid UML solution” from “Software Development area” of “ConceptDraw Solution Park” from this site can match your needs in the best way. Having it means, apart from having the samples of all pre-made diagrams, getting the vector stencils library “UML Use Case”, which contains the specific design symbols of the UML notation (such as actors, actions, associations and relationships) in order to use while working in the ConceptDraw DIAGRAM diagramming and vector drawing software.

Rapid UML Solution

Example 1. UML Solution in ConceptDraw STORE

Use the UML Use Case library to draw use case models for your business documents, presentations and websites.

Jacobson Use Cases Diagram *

Example 2. Jacobson Use Cases Diagram — Restaurant System

The example above shows an use case model of a restaurant business.




See also samples:






NINE RELATED HOW TO's:
When it comes to system construction, a class diagram is the most widely used diagram. UML Class Diagrams is a type of static structure diagram that is used for general conceptual modeling of the systematics of the application. Such a diagram would illustrate the object-oriented view of a system. The object orientation of a system is indicated by a class diagram. It describes the structure of a system by showing the general issues,classes of a system, attributes, operations, interfaces, inheritance, and the relationships between them.UML Class Diagram Notation *
Picture: UML Class Diagram Notation
Related Solution:
ConceptDraw DIAGRAM is a powerful tool for business and technical diagramming. Software Development area of ConceptDraw Solution Park provides 5 solutions: Data Flow Diagrams, Entity-Relationship Diagram (ERD), Graphic User Interface, IDEFO Diagrams, Rapid UML.Software Diagram Examples and Templates *
Picture: Software Diagram Examples and Templates
Related Solution:
Use ConceptDraw DIAGRAM diagramming and business graphics software to draw your own flowcharts of computer algorithms.Process Flow app for macOS *
Picture: Process Flow app for macOS
Related Solution:
Create bar charts for business management problem solving and data comparison using the ConceptDraw DIAGRAM diagramming and vector drawing software extended with the Bar Graphs Solution from the Graphs and Charts area of ConceptDraw Solition Park.Bar Diagrams for Problem Solving.<br>Create business management bar charts with Bar Graphs Solution *
Picture: Bar Diagrams for Problem Solving.Create business management bar charts with Bar Graphs Solution
Related Solution:
When trying to figure out the nature of the problems occurring within a project, there are many ways to develop such understanding. One of the most common ways to document processes for further improvement is to draw a process flowchart, which depicts the activities of the process arranged in sequential order — this is business process management. ConceptDraw DIAGRAM is business process mapping software with impressive range of productivity features for business process management and classic project management. This business process management software is helpful for many purposes from different payment processes, or manufacturing processes to chemical processes. Business process mapping flowcharts helps clarify the actual workflow of different people engaged in the same process. This samples were made with ConceptDraw DIAGRAM — business process mapping software for flowcharting and used as classic visio alternative because its briefly named "visio for mac" and for windows, this sort of software named the business process management tools. This flowchart diagram shows a process flow of project management. The diagram that is presented here depicts the project life cycle that is basic for the most of project management methods. Breaking a project into phases allows to track it in the proper manner. Through separation on phases, the total workflow of a project is divided into some foreseeable components, thus making it easier to follow the project status. A project life cycle commonly includes: initiation, definition, design, development and implementation phases. Distinguished method to show parallel and interdependent processes, as well as project life cycle relationships. A flowchart diagram is often used as visual guide to project. For instance, it used by marketing project management software for visualizing stages of marketing activities or as project management workflow tools. Created with ConceptDraw DIAGRAM — business process mapping software which is flowcharting visio alternative or shortly its visio for mac, this sort of software platform often named the business process management tools.Process Flowchart
Picture: Process Flowchart
Related Solution:
Thanks to the Soccer solution you can design your own soccer-related drawings, diagrams, schemes in seconds. It’s very simple and convenient because Soccer solution contains incredible quantity of ready-to-use predesigned vector objects, professional templates and samples.2014 FIFA World Cup *
Picture: 2014 FIFA World Cup
Related Solution:
Computer networks nowadays are spread all across the world. The large number of parameters, such as geographic scale or communication protocols, can divide networks. One of the most common types of networks is called local area network (LAN). It convenient to represent network examples by means of diagrams. This local area network (LAN) diagram provides an easy way to see the way the devices in a local network are interacted. The diagram uses a library containing specific symbols to represent network equipment , media and the end-user devices such as computers (PC, mac, laptop) , network printer, hubs, server and finally a modem. There are two types of network topologies: physical and logical. The current diagram represents precisely a physical type of LAN topology because it refers to the physical layout of a local network equipment.Local area network (LAN) diagram
Picture: Local area network (LAN). Computer and Network Examples
Related Solution:
There are a lot of tutorials that get you familiar with emergency situations. If you want to know how to create emergency plans and fire evacuation schemes then you must be concerned about safety. There is a list of rules that you should follow to set the fire safety equipment properly. Discover this precise and accurate fire emergency evacuation plan. This sample drawing demonstrate facilities of ConceptDraw DIAGRAM together with its Fire and Emergency Plans solution. The evacuation plan is designed to provide employees and visitors with a map depicting the ways they may use to escape the building in emergency situations. The telephone sets, first aid boxes and extinguisher are also marked on this plan. The evacuation plan should contain a legend for readers. The similar plans are commonly hang on the wall on the building's floors.How To Create Emergency Plans and Fire Evacuation
Picture: How To Create Emergency Plans and Fire Evacuation
Related Solution:
ConceptDraw
DIAGRAM 17