Powerpoint Use Case Diagram Template

Create your presentation by reusing a template from our community or transition your PowerPoint deck into a visually compelling Prezi presentation.

USE CASE DIAGRAM & USE CASE GLOSSARY

Transcript: A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. The use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal. Users (known in Unified Modeling Language (UML) as an "actor") can be a human, an external system, or time. What is UML (Unified Modeling Language)? Use Case Glossary Model scenario with flow of events, not directly on diagram What are the rules in User Case Diagram? USE CASE DIAGRAM & USE CASE GLOSSARY What is Use Case? The Unified Modeling Language (UML) is a general-purpose modeling language in the field of software engineering, which is designed to provide a standard way to visualize the design of a system. Model exceptional behavior with <<extend>> Actor is a role, not a real person. Used to gather requirements of a system. Used to get an outside view of a system. Identify external and internal factors influencing the system. Show the interacting among the requirements are actors. Use Case Sample Diagram Use Case Sample Diagram Think from end user’s perspective - It is clear that you need to know users’ expectation in order to build a software system that works, and this principle is particular important in use case modeling. A use case diagram at its simplest is a representation of a user's interaction with the system and depicting the specifications of a use case. A use case diagram contains four components. The boundary, which defines the system of interest in relation to the world around it. The actors, usually individuals involved with the system defined according to their roles. The use cases, which are the specific roles played by the actors within and around the system. The relationships between and among the actors and the use cases. Model common use case with <<include>> relationship Abogado, Viron P. Abueva, Kizza D. Liguan, Earl John Y. Sac, Timothy John G. Model detailed system flow with sequence diagram - Sequence diagram allows you to model the system behavior by representing the communication and interchange of messages between objects over time. Apply same width on use cases when appropriate - Since the names of use cases are different in length, it is normal to have the use cases in different width. To make the diagram more pretty and easier to read, it would be nice to resize them to same width. Position actors and use cases in a meaningful way - A use case diagram with randomly placed actors and use cases is definitely a nightmare for readers. What is Use Case Diagram? Make good use of stereotype for categorization Avoid long use case name What are its purpose?

UML Use Case Diagram

Transcript: Use Case - Summary Slide The purpose for using use cases is to: Uncover and describe all tasks that need doing in a system (of both human and system actors) To analyse what functionality that need developing for the system The use of use cases must mean that the right functional requirements are made of the IT system (the requirements of the business!) Use cases are documented in two ways Use Case diagrams Give an overview of visible use scenarios in the system Describes what actors that interact with the system Describes any linkages between use cases Verbal description Describes the content of each use case Typically uses a pre-defined template A Use Case is a way of using a system A scenario that describes limited interaction between a system and actors in the field In a Use Case, you describe the use of a system for a given work task You consider a complete work task, initiated by an actor You utilise ”company language” in describing the work task The aggregate Use Cases display the aggregate actor use of the system Use Cases – Definition The purpose of use cases Use case strengths are That they work well as an analytical tool That the notation is simple and easy to pick up That they are easy to understand, both for the business and from the technological aspect It is a widely recognised market standard That customer and supplier – or operators and technicians – can jointly work out and understand the operational functionality They bring structure, and ensure complete analysis The challenge, then, is to find and describe all use cases! Use Cases – Definition The purpose of use cases Why use use cases? UML - Use case diagram UML use cases – Actors Example of use case diagram Use case definition + description - the process Draw use case packages Grouping of business functionality – Use case packages Draw use case diagrams Identify actors Complete verbal description Use cases – Verbal description Identify variants and exceptions Audit business process and term model Why use use cases?

Use Case Diagram

Transcript: 1. Include Include is a Directed Relationship between two use cases, implying that the behavior of the included use case is inserted into the behavior of the including use case. When a use case is depicted as using the functionality of another use case in a diagram, this relationship between the use cases is named as an include relationship. An include relationship is depicted with a directed arrow having a dotted shaft. The tip of the arrowhead points to the child use case and the parent use case is connected at the base of the arrow. A key here is that the included use case cannot stand alone. The stereotype "<<include>>" identifies the relationship as an include relationship. 2. Extend This relationship specifies that the behavior of a use case may be extended by the behavior of another (usually supplementary) use case. The extension takes place at one or more specific extension points defined in the extended use case. In an extend relationship between two use cases, the child use case adds to the existing functionality and characteristics of the parent use case. An extend relationship is depicted with a directed arrow having a dotted shaft, similar to the include relationship. The tip of the arrowhead points to the parent use case and the child use case is connected at the base of the arrow. The stereotype "<<extend>>" identifies the relationship as an extend relationship. 3. Generalization A generalization relationship is also a parent-child relationship between use cases. The child use case in the generalization relationship has the underlying business process meaning, but is an enhancement of the parent use case. In a use case diagram, generalization is shown as a directed arrow with a triangle arrowhead. The child use case is connected at the base of the arrow. The tip of the arrow is connected to the parent use case. • First, name your system. Draw a rectangular shape. Benefits of Use Case Lastly, for other actors repeat steps 2 to 4. Actor Definition These diagrams are yet another way the use case approach differs from traditional methods of gathering requirements. The use case diagram is a roadmap, a high-level view of the requirements that exist in the system. No other approach to gathering requirements has this element. Benefits of Use Case End of Our Report Use case diagrams make requirements more approachable and understandable by allowing someone to quickly visualize what the system needs to do. They allow you to brainstorm at a whiteboard as you decide what major functions your system needs to perform. In short, use case diagrams make it easier to communicate your requirements. Association Then, connect those use cases with the association symbol to the actor. To show the interaction and relationship between the actor and use case. Benefits of Use Case Elements of Use Case  Use cases focus on the users of the system, not the system itself, thus the real system needs are brought to light early on. • Your system (4) is whatever you are developing. It might be a small software component, whose actors are just other software components; or it might be a complete application; or it might be a large distributed suite of applications deployed over many computers and devices. Benefits of Use Case Thank You and God bless!!! Third, identify what goals that the actor will have to interact with the system. That goal becomes the use case. Use cases are represented by spherical shape symbol. Elements of Use Case Second, identify an actor who wants to interact with the system. Draw a stick figure that represents the actor and name it. A subject describes a business system that has one or more business use cases attached to it. A subject is represented by a rectangle that surrounds attached business use cases and is tagged with a name: It adds value because they explain how the system should behave and in the process, they also help brainstorm what could go wrong. Depending on how in depth and complex you want or need to get, use cases describe a combination of the following elements: • A use case (2) represents the actions that are performed by one or more actors in the pursuit of a particular goal. Example use cases are Order Meal, Update Menu, Process Payment. On a use case diagram, use cases are associated (3) with the actors that perform them. Elements of a Use Case Diagram An association is the relationship between an actor and a business use case. It indicates that an actor can use a certain functionality of the business system—the business use case: Use case modeling is also describes all of the things that might go wrong. Provide a list of goals and this list can be used to establish the cost and complexity of the system and project teams can then negotiate which functions become requirements and are built. What Use Cases Include Reading Use Case Diagrams A use case diagram is a diagram that is written using the use case method. This diagram shows in the simplest form the graphical representation

USE CASE DIAGRAM

Transcript: How to draw Use Case Diagram? Where to Use Case Diagrams? Use case diagrams are considered for high level requirement analysis of a system. So when the requirements of a system are analyzed the functionalities are captured in use cases. In a brief when we are planning to draw an use case diagram we should have the following items identified. Functionalities to be represented as an use case Actors Relationships among the use cases and actors. The following are the places where use case diagrams are used: Requirement analysis and high level design. Model the context of a system. Reverse engineering. Forward engineering. USE CASE DIAGRAM Use case diagram is dynamic in nature there should be some internal or external factors for making the interaction. These internal and external agents are known as actors. So use case diagrams are consists of actors, use cases and their relationships. The diagram is used to model the system/subsystem of an application. A single use case diagram captures a particular functionality of a system. So to model the entire system numbers of use case diagrams are used. OVERVIEW Use case diagrams are used to gather the requirements of a system including internal and external influences. These requirements are mostly design requirements. So when a system is analyzed to gather its functionalities use cases are prepared and actors are identified. So in brief, the purposes of use case diagrams can be as follows Used to gather requirements of a system. Used to get an outside view of a system. Identify external and internal factors influencing the system. Show the interacting among the requirements are actors. Use case diagrams are drawn to capture the functional requirements of a system. So after identifying the above items we have to follow the following guidelines to draw an efficient use case diagram. The name of a use case is very important. So the name should be chosen in such a way so that it can identify the functionalities performed. Give a suitable name for actors. Show relationships and dependencies clearly in the diagram. Do not try to include all types of relationships. Because the main purpose of the diagram is to identify requirements. JAVERIA ARIF & TALAL NASIR UML Use Case Diagram PURPOSE WE ARE

Use case Diagram

Transcript: send force data displacement Screen give mechanical instructions listen to movement send force data Ask for position data Haptic Arm inform haptic Send processed Restrains displacement to 1 axis send movement data Use case diagram movement data data matrix of tool Interface Visual interface: Robotic model of the tool Proximity of the tool to the pipe by color change Quantifed display of force Accoustic interface : Accoustic feedback (« parking sensor ») Warning sound when maximum force reachs Interface Calibrating Robot Ask for force data (cutting) Ask for force data (cutting) Virtual Simulation Virtual output Code arm about force increase User data force feedbacks Client

Use Case Diagram

Transcript: Relasi Use Case Bisnis Use Case Sistem Komponen Pendahuluan Penggunaan Use Case Diagram Abstrak Konkrit Jenis Penggunaan Actor Use Case Relation Boundary Thank you for your attention!

Use Case Diagram Presentation

Transcript: Other relations : Inculde and Extend relationships Relationship between classifiers Represented by solid lines Arrowheads indicate invocations Behavior Classifier Specifies a Role An Interaction with the subject Behavior Classifier Sequence of actions performed by one or more subjects Collaboration with one or more actions Provides a result Definition By Galiano Folco, Jeannette Antoine, Demogue Anthony, Gasparini Leandro, Da Silva Mathieu Unified Modeling Language (UML): General-purpose, developmental, modeling language.​ It specifies:​ Requirements ​ Functionality​ Environment PROJECT BASED LEARNING Use Case Diagram Actors​ System boundary / Subject​​ Multiplicity​ Associations Inculde and extend relationship Specialization of class diagrams Two functions Behavior Diagram : User interaction with system Structure Diagram : User and use cases relationship​ ​ Diagram elements Associations "Use case diagrams, are used to define and analyze a set of actions that one or many systems should perform in collaboration with external users."​ (uml-diagrams.org) Generalization sub classes inherit proprieties and behaviors sub classes can override behaviors Use Cases Actors Can be a : Human User System Hardware

USE CASE DIAGRAM

Transcript: USE CASE DIAGRAM An association specifies a semantic relationship that can occur between typed instances. It has at least two ends represented by properties, each of which is connected to the type of the end. More than one end of the association may have the same type. An end property of an association that is owned by an end class or that is a navigable owned end of the association indicates that the association is navigable from the opposite ends; otherwise, the association is not navigable from the opposite ends. Represents the actions performed by one or more actors in the pursuit of a particular goal. A use case is a kind of type. A use case is a list of steps, typically defining interactions between a role (known in Unified Modeling Language (UML) as an "actor") and a system, to achieve a goal. ACTORS TIPS A condition or restriction expressed in natural language text or in a machine readable language for the purpose of declaring some of the semantics of an element. USE CASE EXAMPLE Example of Actor Example of Dependency Example of Association J4 Presentation of Use Case Diagram DEPENDENCY USE CASE Example of Constraint CONSTRAINT A use case diagram is a graphic depiction of the interactions among the elements of a system. A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. In this context, the term "system" refers to something being developed or operated, such as a mail-order product sales and service Web site. EXTEND A use case defines the interactions between external actors and the system under consideration to accomplish a goal. Actors must be able to make decisions, but need not be human: "An actor might be a person, a company or organization, a computer program, or a computer system — hardware, software, or both. Actors are always stakeholders, but not all stakeholders are actors, since they "never interact directly with the system, even though they have the right to care how the system behaves Primary Actor: The primary actor of a use case is the stakeholder that calls on the system to deliver one of its services. It has a goal with respect to the system – one that can be satisfied by its operation. Supporting Actors: A supporting actor in a use case in an external actor that provides a service to the system under design. It might be a high-speed printer, a web service, or humans that have to do some research and get back to us. Use case Example ASSOCIATION A dependency is a relationship that signifies that a single or a set of model elements requires other model elements for their specification or implementation. This means that the complete semantics of the depending elements is either semantically or structurally dependent on the definition of the supplier element(s).