COEPD Forum

Business Analyst => Business Analyst Concepts Discussion => Topic started by: Vasantharaj on September 22, 2016, 04:17:51 pm

Title: How we draw a usecase diagram from a case study?
Post by: Vasantharaj on September 22, 2016, 04:17:51 pm
The following steps are followed
1. Information which we do not model in use case diagrams are
    (i) Name of the systems
    (ii) Architectures
   (iii) Database names
   (iv) Networks
   (v) Brand names
   (vi) Technology names
2. Differentiate information against actions.
3. Write all sequence of actions.
4. Try to find out which actor is performing the above section.
5. Try to identify essential use cases and supporting use cases.
6. Try to identify some modules with respect to functionality.
7. Try to draw the diagram appropriately between use cases and actors
Title: Re: How we draw a usecase diagram from a case study?
Post by: Swathi894 on November 18, 2016, 02:56:46 am
Use Case Diagram is a high-level diagram of all other UML diagrams.
- The main focus of the UCD will be on how the external interfaces (end users, support systems, special databases and third party) interacts with the proposed IT System.
- This interaction initiates a Business function/functionality called as a 'Use Case' shown with an ellipse symbol.
- Use cases are used to describe the functionality of a system in a horizontal way, rather than representing the details of individual features
   in the system, UCDs can show all necessary functionalities.
- UCDs are not sequence diagrams or flow charts because they do not show the order(sequence) of action or the number of times the 
   system actions and sub-actions are to be executed and also doesn't mention the time frame.
4 Major Elements of UCDs:[/b]
1.   Actors (can be a living or non-living things) (Actors are NOUNS)
2.   The system itself (rectangular box)
3.   The Use Cases (Essential UC – Makes sense and completeness to end users, and Supporting UCs – Makes sense and support
        Essential UCs) (UCs are VERBS)
4.   The lines that represent the relationship between the elements. (Generalize -> Generalization refers to “A kind of”
        Here there are parent class and child class. A parent class cannot exist without child class.
        Include -> Compulsory-> Parent class cannot exist without child class.
        Extend -> Optional -> Child class exists without Parent class.
5.   System clock (Automation):  The system clock refers to the automatic responses from the system to the end users to perform
         function in the desired way.

Guidelines to draw a UCD from a case study:
1.   Information that is not covered in the UCD is as follows,
•   Names of the systems (laptop, desktops, Workstations).
•   Architectures (2 tier, 3 tier, ‘n’ tier, client server.
•   Names of DB (DB2, SQL Server, My SQL).
•   Networks (LAN, WAN, Internet).
•   Names of the brands (HP, Lenovo, Wipro, Sony).
•   Names of the technologies (Java, Net, Mainframes)
2.   Differentiate Actions from Information.
3.   Write the sequence of actions.
4.   Try to match action with an actor.
5.   Identify Essential use cases and Supporting use cases.
6.   Identify modules in relation to usage or functionality.
7.   Draw appropriate relationships (generalize, include, extend) between Actors and Use cases.
Title: Re: How we draw a usecase diagram from a case study?
Post by: rakesh chary on November 30, 2016, 11:50:08 am
The following steps are followed
1. Information which we do not model inuse case diagrams (http://use case diagrams) are
    (i) Name of the systems
    (ii) Architectures
   (iii) Database names
   (iv) Networks
   (v) Brand names
   (vi) Technology names
2. Differentiate information against actions.
3. Write all sequence of actions.
4. Try to find out which actor is performing the above section.
5. Try to identify essential use cases and supporting use cases.
6. Try to identify some modules with respect to functionality.
7. Try to draw the diagram appropriately between use cases and actors
Title: Re: How we draw a usecase diagram from a case study?
Post by: vardhini on December 10, 2016, 07:32:30 pm
Use case can be indirectly called as mother of all diagrams.
First and most important thing is that go thoroughly the case study and identify the following parameters.
a)Actors
b)system(what they want to develop)
c)Use cases
d)lines(Represents the relationship between them)
Step -1
Differentiate the Actors information and their  assigned work in that particular case study.
NOTE:Actors they may be living or non living things
They should represent by noun
Actors always stay away from system boundary.
Step-2
Write  actions according to sequence.
step-3
Make sure which actor is performing there particular actions.
Step-4
Identify the Essential use cases and supporting use cases.
NOTE:
Essential use cases make sense and gives completeness to end user
Supporting use case supports the essential use case.
step-5
Draw the relationship appropriately between the identify   actors and use cases.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 171525904 on July 04, 2017, 02:35:32 pm
Steps To draw Use case Diagram.

1)Define Primary actors
2)Define if any actor generalization exist
3)Define secondary actor
4)Define essential use cases (Action)
5)Define specialize use cases
6)Define associations
7)Define include relationship
8)Define exclude relationship
9)Define Automation   
Title: Re: How we draw a usecase diagram from a case study?
Post by: 170123204 on July 07, 2017, 11:48:56 am
The following steps are followed
1. Information which we do not model in use case diagrams are
    (i) Name of the systems
    (ii) Architectures
   (iii) Database names
   (iv) Networks
   (v) Brand names
   (vi) Technology names
2. Differentiate information against actions.
3. Write all sequence of actions.
4. Try to find out which actor is performing the above section.
5. Try to identify essential use cases and supporting use cases.
6. Try to identify some modules with respect to functionality.
7. Try to draw the diagram appropriately between use cases and actors

Title: Re: How we draw a usecase diagram from a case study?
Post by: 172031605 on August 02, 2017, 04:37:26 pm
Use case diagrams are considered for high level requirement analysis of a system. When the requirements of a system are analyzed, the functionalities are captured in use cases.

We can say that use cases are nothing but the system functionalities written in an organized manner. The second thing which is relevant to use cases are the actors. Actors can be defined as something that interacts with the system.

Actors can be a human user, some internal applications, or may be some external applications. When we are planning to draw a use case diagram, we should have the following items identified.

    Functionalities to be represented as use case

    Actors

    Relationships among the use cases and actors.

Use case diagrams are drawn to capture the functional requirements of a system. After identifying the above items, we have to use the following guidelines to draw an efficient use case diagram

    The name of a use case is very important. 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, as the main purpose of the diagram is to identify the requirements.

    Use notes whenever required to clarify some important points.

Following is a sample use case diagram representing the order management system. Hence, if we look into the diagram then we will find three use cases (Order, SpecialOrder, and NormalOrder) and one actor which is the customer.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 171035406 on August 27, 2017, 04:36:24 pm
Steps to draw Use case diagrams:

      Information which we do not model in use case diagrams are:
         Name of the systems,architectures,databases names,networks,brand names.

      Differentiate information against actions.

      Write all sequence of actions.

      Find out which actor is performing the above action.

      Indentify essential use case and supporting use cases.

      Identify some modules with respect to functionality or usage.

      Draw the relationship appropriately between the identified actors and use cases.
Title: How we draw a usecase diagram from a case study?
Post by: Pranjal Dutta on August 29, 2017, 03:58:27 pm
Use case Diagram is the most important and essential tool for Business Analyst. In layman, Use case Diagram is a medium for the business owner to understand how the proposed system will work and for the developer to understand what they need to prepare.
So to draw the Use case Diagram from a case study, we need to follow the below steps:
1. Need to identify the actor(s) from the information given in the case study. (Actors are those who interact with system).
2. Need to write all sequence of Actions.
3. Need to identify which actor is performing what action(s).
4. Need to identify the essential and supporting Use Cases (use case are the services that system knows how to perform).
5. Need to draw appropriate relationship between the identified Actor(s) and Use-Case(s).
6. And yes, some information we need to keep in mind that cannot be used in the Use case Diagram:
    a. Name of the system, Type of Database, Type of Network, Name of the technologies, Brand name.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1170220109 on October 18, 2017, 05:34:35 pm
1)The information which we do not model in use case diagrams are
Name of the systems, architectures, database names, networks, brand names, technology names.
2)Differentiate among different actors
3)Write all sequences of actions
4)Try to find out which actor is performing above action
5)Try to identify Essential use cases and Supporting use cases
6)Try to identify some modules with respect to the functionality
7)Try to draw the relationships appropriately in between the identified actors and Use cases.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1171429410 on January 01, 2018, 03:03:17 pm
The steps involved in drawing a usecase diagram from a case study are:
1. Analyze the different actions to be performed as per the case study.
2. Put all the actions in a sequential order.
3. Analyze the actor who is performing the actions in case study.
4. Figure out essential use case and supporting use case.
5. Identify some modules with respect to functionality or usage.
6. Formulate the relationship between Actors and Usecases.

Note: Information need not to be included in usecase are:
1. Database names
2. Brand names
3. Technology names
4. Architectures
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1172540111 on January 02, 2018, 10:52:28 pm
First, list out all the actions that you think are necessary, then see if the actions really meet the objective, and take out unnecessary actions. Do the same with Actors. After finalizing the Actions and Actors, start mapping, use Generalization, Include and Extend relations where ever necessary according to the case study(Include for mandatory fields, Extend for optional fields and generalization for either-or cases). If any actor generalization is necessary then connect them.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1173025009 on January 03, 2018, 08:28:10 pm
What is a Use Case Diagram?
•   A use case diagram is a dynamic or behaviour diagram in UML.
•   Use case diagrams 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.
Why Make Use Case Diagrams?
The purpose of use case diagram is to capture the dynamic aspect of a system. However, this definition is too generic to describe the purpose, as other four diagrams (activity, sequence, collaboration, and Statechart) also have the same purpose. They also help identify any internal or external factors that may influence the system and should be taken into consideration.
They provide a good high level analysis from outside the system. Use case diagrams specify how the system interacts with actors without worrying about the details of how that functionality is implemented.

Basic Use Case Diagram Symbols and Notations

System
Draw your system's boundaries using a rectangle that contains use cases. Place actors outside the system's boundaries.
 

Use Case
Draw use cases using ovals. Label the ovals with verbs that represent the system's functions.
 

Actors
Actors are the users of a system. When one system is the actor of another system, label the actor system with the actor stereotype.
 

Relationships
There can be 5 relationship types in a use case diagram.
•   Association between actor and use case
•   Generalization of an actor
•   Extend between two use cases
•   Include between two use cases
•   Generalization of a use case
Association Between Actor and Use Case
This one is straightforward and present in every use case diagram. Few things to note.
•   An actor must be associated with at least one use case.
•   An actor can be associated with multiple use cases.
•   Multiple actors can be associated with a single use case.
 
Different ways association relationship appears in use case diagrams
Generalization of an Actor
Generalization of an actor means that one actor can inherit the role of the other actor. The descendant inherits all the use cases of the ancestor. The descendant has one or more use cases that are specific to that role. Let’s expand the previous use case diagram to show the generalization of an actor.
 
A generalized actor in an use case diagram
Extend Relationship Between Two Use Cases
Many people confuse the extend relationship in use cases. As the name implies it extends the base use case and adds more functionality to the system. Here are few things to consider when using the <<extend>> relationship.
•   The extending use case is dependent on the extended (base) use case. In the below diagram the “Calculate Bonus” use case doesn’t make much sense without the “Deposit Funds” use case.
•   The extending use case is usually optional and can be triggered conditionally. In the diagram, you can see that the extending use case is triggered only for deposits over 10,000 or when the age is over 55.
•   The extended (base) use case must be meaningful on its own. This means it should be independent and must not rely on the behavior of the extending use case.
Lets expand our current example to show the <<extend>> relationship.
 
Extend relationship in use case diagrams
Include Relationship Between Two Use Cases
Include relationship show that the behavior of the included use case is part of the including (base) use case. The main reason for this is to reuse the common actions across multiple use cases. In some situations, this is done to simplify complex behaviors. Few things to consider when using the <<include>> relationship.
•   The base use case is incomplete without the included use case.
•   The included use case is mandatory and not optional.
Lest expand our banking system use case diagram to show include relationships as well.
 
Includes is usually used to model common behavior
Generalization of a Use Case
This is similar to the generalization of an actor. The behavior of the ancestor is inherited by the descendant. This is used when there is common behavior between two use cases and also specialized behavior specific to each use case.
For example, in the previous banking example, there might be a use case called “Pay Bills”. This can be generalized to “Pay by Credit Card”, “Pay by Bank Balance” etc.

How to Draw a Use Case Diagram?
Use case diagrams are considered for high level requirement analysis of a system. When the requirements of a system are analyzed, the functionalities are captured in use cases.
We can say that use cases are nothing but the system functionalities written in an organized manner. The second thing which is relevant to use cases are the actors. Actors can be defined as something that interacts with the system.
Actors can be a human user, some internal applications, or may be some external applications. When we are planning to draw a use case diagram, we should have the following items identified.
•   Functionalities to be represented as use case
•   Actors
•   Relationships among the use cases and actors.

Use case diagrams are drawn to capture the functional requirements of a system. After identifying the above items, we have to use the following guidelines to draw an efficient use case diagram
•   The name of a use case is very important. 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.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1173025809 on January 12, 2018, 12:10:22 am
The various steps involved in creating a use case diagram from a case study can be stated as -
1. Read the case carefully to find out all the actions to be performed.
2. Identifying Actors, who are the external entities that interact with the system.
3. Identifying the usecases, to identify what the actors need from the system.
4. Looking for the common functionality that can be reused across the system.
5. Generalize the Actors and usecases to show the inheritance of the functions (where actors are associated with similar use cases while triggering few use cases unique only to them).
6. There are optional functions as well as additional functions - If some functions are triggered optionally, then we can use extend relationship.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1171921109 on January 21, 2018, 08:39:06 pm
They also help identify any internal or external factors that may influence the system and should be taken into consideration.
When thinking of use cases, think of the end goal of a user. They don't want to "login" or "sign up." That's not a use case. The use case is more like "make a purchase."
Actors don't have names. They're not "Bob." They represent the role of someone interacting with the system.
Keep your names short and the size of your use cases consistent with a professional look.
For a detailed implementation of a user's goal using a sequence diagram.They provide a good high-level analysis from outside the system. Use case diagrams specify how the system interacts with actors without worrying about the details of how that functionality is implemented.
Draw your system's boundaries using a rectangle that contains use cases. Place actors outside the system's boundaries.
Use Case
Draw use cases using ovals. Label the ovals with verbs that represent the system's functions.
Actors
Actors are the users of a system. When one system is the actor of another system, label the actor system with the actor stereotype.
Relationships
Illustrate relationships between an actor and a use case with a simple line. For relationships among use cases, use arrows labeled either "uses" or "extends." A "uses" relationship indicates that one use case is needed by another in order to perform a task. An "extends" relationship indicates alternative options under a certain use case
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1171948312 on February 14, 2018, 06:50:21 am
1.Read the case study thoroughly 2-10 times.
2.Understand the actors and actions who are involved in the case study.
3.Write down the primary actors(End User/who interacts with the system) and secondary actors(On whom system dependent on)and the actions involved in the case. Generalize actors and actions involved in the case.
4. Draw a system boundary- usecase
5.Place the primary actors on the left-hand side of the system boundary.
6.Place the secondary actors on the right side.
7. Place the Actions inside the system boundary. Connect the actors and actions in the system and connect the actions which are dependent on secondary actor.
8.Hence we draw Usecase diagram.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1170944412 on March 10, 2018, 12:58:54 pm
Use case diagrams are used to describe the functionality of a system from a top-down perspective. They represent only the positive flow and all the available functionality of the system are shown. There are essentially four major elements of UCDs
The actors, the system, the use cases and the lines that represent the relationship between these elements.
We use the following rules to draw use case diagram
•   Information that we do not model in the use case diagrams are
             Architecture names (2 tier, 3 tier, client server etc)
             Names of the systems (laptop, desktop)
             Brand names (HP, Lenovo etc.)
             Technology used (java, .net etc.)
             Networks (LAN, WAN)
             Databases (SQL, MySQL, etc.)
•   Differentiate between information and actions
•   Write all sequence of actions
•   Try to identify the actors performing the above mentioned actions
•   Try to differentiate between essential use cases and supporting use cases
•   Try to identify some modules with respect to functionality or usage
•   Try to identify the relationships appropriately between the identified actors and the use cases
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1180650901 on March 25, 2018, 11:07:35 pm
First and last
Read the case study 2 -3 times because that will give you a picture .

In a very simple or layman :

1. Mark primary actors column
2. Secondary actors column
3. supporting use case
4. essential  use case

Then try to relate it with the case study
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1172831810 on April 07, 2018, 04:59:16 pm
The following checklist shows the steps necessary for the construction of use case diagrams from the external view.


Title: Re: How we draw a usecase diagram from a case study?
Post by: Satish kumar Gajula on April 24, 2018, 04:46:58 pm
Steps to follow to draw a Use Case diagram from a case study:
1.   Information which we Do Not model in Use Case diagrams are
a)   Name of the systems (Laptops, Desktops, Workstations),
b)   Architectures (2 Tier, 3 Tier, n Tier, Client Server),
c)   Databases Names (DB2, SQL Server, My SQL),
d)   Networks (LAN, WAN, Internet),
e)   Brand Names (HP, Lenovo, Wipro, Sony)
f)   Technology Names (Java, .Net, Mainframes)
2.   Differentiate information against actions
3.   Write all sequence of actions
4.   Try to find out which actor is performing the above action
5.   Try to identity Essential Use Cases and Supporting Use Cases
6.   Try to identity some modules with respect to functionality or usage
7.   Try to draw the relationships appropriately between the identified actors and use cases.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1180654601 on June 06, 2018, 10:26:24 pm
The purpose of use case diagram is to capture the dynamic aspect of a system.Use case diagrams are used to gather the requirements of a system including internal and external influences. These requirements are mostly design requirements. Hence, when a system is analyzed to gather its functionalities, use cases are prepared and actors are identified.

To conclude an use case is used for;'
-Used to gather the requirements of a system.
-Used to get an outside view of a system.
-Identify the external and internal factors influencing the system.
-Show the interaction among the requirements are actors.

Steps to be followed to draw Use case Diagram;
(1) Information which we do not model in Use case diagram are:
Names of the systems (Laptops, Desktops, Work stations).
Architectures (2 Tier, 3 Tier, Client server).
Databases names (DB2, SQL Server, My SQL).
Networks (LAN, WAN, Internet).
Brand Names (Lenovo, Intel, Sony, HP).
Technology Names (Java, C++, Dot Net).
(2) Differentiate information against actions.
(3) Write all sequence of actions.
(4) Try to find out which actor is performing the above action.
(5) Try to identify essential use cases and supporting use cases.
(6) Try to find out modules with respect to functionality or usage.
(7) Try to draw the relationships appropriately between identified actors and use cases.

Title: Re: How we draw a usecase diagram from a case study?
Post by: 1183170103 on June 15, 2018, 02:18:54 pm
This is typically my approach ( keeping in mind the step mentioned in the book - i.e., dont model databases, tech, brand names etc)

compile actors and actions into a list. Then, you draw connectors between actors and actions. What you end up with, is a clear visual representation of the relationship between actors and actions. It's really easy after this.

The difficulty lies in identifying the actions and actors without missing anything.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1180364903 on June 22, 2018, 08:20:33 pm

Below are the steps for drawing use case

 - First identify the Actors
 - Second define use case
 - Third define use case behaviour
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1181471104 on June 27, 2018, 11:39:03 am
The following steps are followed
1. Information which we do not model in use case diagrams are
    (i) Name of the systems
    (ii) Architectures
   (iii) Database names
   (iv) Networks
   (v) Brand names
   (vi) Technology names
2. Differentiate information against actions.
3. Write all sequence of actions.
4. Try to find out which actor is performing the above section.
5. Try to identify essential use cases and supporting use cases.
6. Try to identify some modules with respect to functionality.
7. Try to draw the diagram appropriately between use cases and actors
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1181278305 on July 11, 2018, 09:46:30 pm





Use case diagram will be drawn in perspective of user behavior with the system .The following steps are followed
1. Information which we do not model in use case diagrams are
    (i) Name of the systems
    (ii) Architectures
   (iii) Database names
   (iv) Networks
   (v) Brand names
   (vi) Technology names
2. Differentiate information against actions.
3. Write all sequence of actions.
4. Try to find out which actor is performing the above section.
5. Try to identify essential use cases and supporting use cases.
6. Try to identify some modules with respect to functionality.
7. Try to draw the diagram appropriately between use cases and actors
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1170505308 on July 15, 2018, 11:23:18 pm
Information which we do not model in use case diagrams are:
Name of the systems,architectures,databases,networks,systems, brand names

Identifying Actors *

Actors are external entities that interact with system. Actor can be a person, another system or an organization.

Example : In a banking system, the most obvious actor is the customer. Other actors can be bank employee or cashier depending on the role that is planned to be presented in the use case



Identifying Use Cases *

After identifying actors and the next step would be identification of use cases. A good way to do this is to identify that how actors  interact with the system.

Identify Essential use cases and Supporting use cases

Top level use cases should always provide a complete function required by an actor. We can extend or include use cases depending on the complexity of the system.
Once you identify the actors and the top level use case you have a basic idea of the system.

and then we need to draw the relationship appropriately between the identified actors and use cases.

AND ALSO PERFORMING SOME ROLE PLAYS HELPS US IN IDENTIFYING THE REQUIREMENTS WHICH IN TURN HELPS IN DESIGNING THE USE CASE DIAGRAM

FOR understanding of business processes AND POTENTIAL REQUIREMENTS TO BE IDENTIFIED/ANALYSED WE CAN PRACTICE THE FOLLOWING :
 
Brainstorming, Surveys, Role plays, Communicating with the domain matter and subject matter experts, Tools used.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1181280005 on July 31, 2018, 02:08:00 pm
The major elements of use case diagram is after reading the case study.
Actor
Actors are usually individuals involved with the system defined according to their roles. The actor can be a human or other external system.

Use Case
A use case describes how actors uses a system to accomplish a particular goal. Use cases are typically initiated by a user to fulfill goals describing the activities and variants involved in attaining the goal.

Relationship
The relationships between and among the actors and the use cases.

System Boundary
The system boundary defines the system of interest in relation to the world around it.

Home Tutorials Use Case Diagram
What is a Use Case Diagram in UML?
Use Case Diagram Notations
Actor
Use Case
Relationship
System Boundary
Benefits of Use Case Diagram
How to Draw Use Case Diagram?
Structuring Use Cases
Include
Extend
Abstract & Generalization
Business Use Case
Use Case Diagram Examples
Use Case Diagram Tutorial
A use case describes how a user uses a system to accomplish a particular goal. A use case diagram consists of the system, the related use cases and actors and relates these to each other to visualize: what is being described? (system), who is using the system? (actors) and what do the actors want to achieve? (use cases), thus, use cases help ensure that the correct system is developed by capturing the requirements from the user's point of view.

Use Case Diagram Example
What is a Use Case Diagram in UML?
A use case is a list of actions or event steps typically defining the interactions between a role of an actor and a system to achieve a goal. A use case is a useful technique for identifying, clarifying, and organizing system requirements. A use case is made up of a set of possible sequences of interactions between systems and users that defines the features to be implemented and the resolution of any errors that may be encountered.

While a use case itself might drill into a lot of detail (such as, flow of events and scenarios) about every possibility, a use-case diagram can help provide a higher-level view of the system, providing the simplified and graphical representation of what the system must actually do.

A use case (or set of use cases) has these characteristics:

Organizes functional requirements
Models the goals of system/actor (user) interactions
Describes one main flow of events (main scenarios) and possibly other exceptional flows (alternatives), also called paths or user scenarios
Try it!
Finding an online Use Case Diagram tool? Just click the Draw button below to create your Use Case Diagram online. Visual Paradigm Online is free* and intuitive. You can also go through this Use Case Diagram tutorial to learn about Use Case Diagram before you get started.

Draw Now
Use Case Diagram Notations
Use cases define interactions between external actors and the system to attain particular goals. A use case diagram contains four main components

Use Case Diagram Notations
Actor
Actors are usually individuals involved with the system defined according to their roles. The actor can be a human or other external system.

Use Case
A use case describes how actors uses a system to accomplish a particular goal. Use cases are typically initiated by a user to fulfill goals describing the activities and variants involved in attaining the goal.

Relationship
The relationships between and among the actors and the use cases.

System Boundary
The system boundary defines the system of interest in relation to the world around it.

Benefits of Use Case Diagram
Use cases is a powerful technique for the elicitation and documentation of black-box functional requirements.
Because, use cases are easy to understand and provide an excellent way for communicating with customers and users as they are written in natural language.
Use cases can help manage the complexity of large projects by partitioning the problem into major user features (i.e., use cases) and by specifying applications from the users' perspective.
A use case scenario, often represented by a sequence diagram, involves the collaboration of multiple objects and classes, use cases help identify the messages (operations and the information or data required - parameters) that glue the objects and classes together.
Use cases provide a good basis to link between the verification of the higher-level models (i.e. interaction between actors and a set of collaborative objects), and subsequently, for the validation of the functional requirements (i.e. blueprint of white-box test).
Use case driven approach provides an traceable links for project tracking in which the key development activities such as the use cases implemented, tested, and delivered fulfilling the goals and objectives from the user point of views.

A Use Case diagram can be developed by following the steps below.

Identify the Actors (role of users) of the system.
For each category of users, identify all roles played by the users relevant to the system.
Identify what are the users required the system to be performed to achieve these goals.
Create use cases for every goal.
Structure the use cases.
Prioritize, review, estimate and validate the users.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1181279905 on August 27, 2018, 07:43:45 pm
First we have to read the case study properly. Find all the actors and differentiate the information against each actors. Make a sequence of all actors. Then we have to find out the actions performed by each actors from case study. Then try to identify essential use case and supporting use case. Identify some modules with respect to functionality or usage. Then we have to dry the relationship appropriately between the identified actors and use case. We have to identify the information which we don’t model in use case, like name of the system, networks, technology names, brands name.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1180986106 on August 29, 2018, 07:02:56 pm
Initially we need to identify the system, who are all the different actors relating to primary or secondary actor, use cases itself and the lines representing different relationships between elements.
Title: Re: How we draw a usecase diagram from a case study?
Post by: viswanathan on September 04, 2018, 12:40:48 pm
First thoroughly read the business case study or paper which is given by the project management team or sometimes it will given by your senior BA or business client.
Secondly,make some research or you all well know google it on that domain get in touch with domain expert or so called SME   
Have a good understanding of that domain it is speaking about
•   Make a list of actors i.e. end user of the system and supporting system
•   Think of features of system i.e. function of system so called use case or goals of end user
•   Try to make relationship with actors and use case
•   Mandatory fields i.e. include ex:banking mobile number, Id
•   Optional fields i.e. extend temporary address, alternate number

Finally use UCD is ready.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1180793807 on October 16, 2018, 11:27:17 pm
to draw a use case digram following things to be kept in mind-
1. make a rectangular box in which the actions have to be written.
 suppose for an atm machine has to be drawn so for that we have to first make a rectangular box on center top of which the name of the project has to be given.
2. make action boxes such as messages which has to be displayed, card insertion message, asking for a pin, asking to enter amount, checking the denominations available, checking for cash, etc has to be given, in short what the machine has to do things are generally written here.
3. next comes the actors- two kinds of actors are generally present. primary and secondary.
 for that primary actors will be the normal people who will be going to withdraw the cash and also the cashier who will be re filling the atm machine when the cash goes out. whereas the secondary actor will be the bank database where the records of  client will be there, also the printer which prints the receipt also comes in the category of secondary actors. hence it does not have to worry about whether only living things such as people will only be the actors, instead it will be non living things too can act as the actors. hence actors are those who direct or indirectly are involved in the using of the mechanism.
4. atlast will be the linking line between the actors and the action that means who will be doing what work.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1181278605 on October 25, 2018, 10:01:01 am
steps in drawing UCD=
1. identifying actor= play role in system.
2. usecase= it is elisp shape.define capabilities of system.
3.connector= defines interaction with the system.
4.generalization= used for further specification.
5.stereotype=common action.
6.include relation ship= implecit function.
7.exclude /extend relation ship= explicict function /optional.
8.draw system boundary.
9.name the system.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1182020910 on November 21, 2018, 03:28:31 pm
In a use case diagram, we prepare a basic flow chart or it is necessary to prepare alternate flow chart & exceptional flow chart together???


Kindly clarify.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1182916109 on December 14, 2018, 01:36:12 pm
1. Identify actions against information
2. Identify actors
3. Identify actors which perform above actions
4. Identify essential and support use case
5. Identify the relationship between identified actors and use case.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1191940101 on March 23, 2019, 09:35:56 am

Identify the Actors (role of users) of the system.
For each category of users, identify all roles played by the users relevant to the system.
Identify what are the users required the system to be performed to achieve these goals.
Create use cases for every goal.
Structure the use cases.
Prioritise, review, estimate and validate the users
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1191648502 on May 12, 2019, 07:03:03 pm
The following steps are followed
1. Information which we do not model in use case diagrams are
    (i) Name of the systems
    (ii) Architectures
   (iii) Database names
   (iv) Networks
   (v) Brand names
   (vi) Technology names
2. Differentiate information against actions.
3. Write all sequence of actions.
4. Try to find out which actor is performing the above section.
5. Try to identify essential use cases and supporting use cases.
6. Try to identify some modules with respect to functionality.
7. Try to draw the diagram appropriately between use cases and actors
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1193059603 on June 03, 2019, 01:54:08 pm
use case diagrams are one of the important and most used diagrams, which usually depicts how an external user interacts with the system.

there are some rules on how to draw an use case diagram from the case study, which are as follows.


1. information that neednot be mentioned in use case diagram is
names of the systems, architectures, databases, brand names, technology names,.

2. differentiate information against actions, information neednot be depicted in diagram.

3. write the sequence of all actions

4.identify primary and secondary actors

5. differentiate between essential and supporting use cases.

6.try to identify which user is performing particular action.

7. draw appropriate relationships between actors and use cases like generalization, include, exclude etc.

Title: Re: How we draw a usecase diagram from a case study?
Post by: 1192767805 on August 03, 2019, 10:05:53 am
Steps To draw Use case Diagram.

1.Define Primary actors
2.Define if any actor generalization exist
3.Define secondary actor
4.Define essential use cases (Action)
5.Define specialize use cases
6.Define associations
7.Define include relationship
8.Define exclude relationship
9.Define Automation   
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1190244102 on August 03, 2019, 07:56:54 pm
Use case can be indirectly called as mother of all diagrams.
First and most important thing is that go thoroughly the case study and identify the following parameters.
a)Actors
b)system(what they want to develop)
c)Use cases
d)lines(Represents the relationship between them)
Step -1
Differentiate the Actors information and their  assigned work in that particular case study.
NOTE:Actors they may be living or non living things
They should represent by noun
Actors always stay away from system boundary.
Step-2
Write  actions according to sequence.
step-3
Make sure which actor is performing there particular actions.
Step-4
Identify the Essential use cases and supporting use cases.
NOTE:
Essential use cases make sense and gives completeness to end user
Supporting use case supports the essential use case.
step-5
Draw the relationship appropriately between the identify   actors and use cases.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1190763804 on August 27, 2019, 06:52:38 pm
Use case diagrams are usually referred to as behavior diagrams used to describe a set of actions (use cases) that some system or systems (subject) should or can perform in collaboration with one or more external users of the system (actors).

Use case diagram is a high level diagram and mother of all diagrams and is shown with an ellipse symbol.

To draw this from a Case Study, we follow below rules –
-   Specify Information against Actions
-   Define all sequence of Actions
-   Find out the Primary and Secondary Actors
-   Define Essential Use cases and Supporting Use cases.
-   Identify some modules with respect to functionality or usage.
-   Draw the relationships appropriately between the identified Actors and Use cases.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1190953311 on December 16, 2019, 07:12:51 pm
how we can define information and content in case study while drawing use case daigram?
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1190956211 on December 28, 2019, 12:24:14 pm
Use case diagram is a high level diagram.The main focus of this diagram will be on"how end users" are interacting with the proposed IT Solution. Use case diagrams can be drawn to give the positive flow of the system.

UCD's have 4 major elements.

1.Actors
2.The system
3. Kines that represent the relationship.
4. The use cases

Steps to Draw UCD:
1. Find the actors involved in the given case study
2.Write a sequence of actions
3.find out which actor is performing which action
4.Identify essential and support use cases.
5.Draw the relationship among the use case and action .
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1191364004 on March 02, 2020, 03:39:09 pm
A Use Case model can be developed by following the steps below.

Identify the Actors (role of users) of the system.
For each category of users, identify all roles played by the users relevant to the system.
Identify what are the users required the system to be performed to achieve these goals.
Create use cases for every goal.
Structure the use cases.
Prioritize, review, estimate and validate the users.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1190246302 on March 07, 2020, 03:13:31 pm
1.Differentiate information against actions.
2. write all the sequence actions.
3.try to find out which actor is performing the above action.
4.try to identify essential use cases and supporting use cases
5. try to identify primary and secondary actions.
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1190956511 on March 29, 2020, 04:26:51 pm
Use case consists of actors, system itself, use cases, the lines which represents the relationships

1.Information which we do not model in the use case diagram
      .Names of systems,data base names,networks , technology names, brand name
2.Differentiate information against actions
3.Write all sequence of actions
4.Try to find out which actor is performing the above action
5.Try to identify the essential use cases and supporting use cases
6.Try to identify some modules with respect to functionality or usage
7.Try to draw relationship appropriately between the identified actors and use cases

Title: Re: How we draw a usecase diagram from a case study?
Post by: 1200474101 on April 01, 2020, 11:26:50 am
Main pointers to be remembered while drawing a use case diagram are:
1. Have one round of overview on the case study and come up with the list of actors who will have interaction with the system.
2. For these actors, system should have use cases, and use cases are always "actions" that actors interact with the system.
3. So, taking point-2 as reference, break the case study into smaller chunks and try to analyze every point. Identify if they have interaction with the system or not.
4. If they have, notate them in verbal forms (as an action, Ex: Makes Payment, Generates Bill). These can be termed as 'use cases.'
5. Map them with the corresponding actors.
6. Try to identify include, extend and generalization relationships, if possible as they add more information to the diagram.
      a. include : When your child use case cannot exist without the parent use case, they have an <include> relationship established.
      b. extends : When your child use case can exist with/without the parent use case existence, they have <extends> relationship
                         established.
      c. Generalization : When the child use case exhibits the properties of a parent use case, then they can be exhibited by
                         generalization relation. It implies for actors also. Ex: When financial transaction is a parent use case, Pay by Credit
                         Card, Pay by Cash will fall as child use cases. Pay by Credit Card, Pay by Cash are type of financial transaction.

These are the major concerns to be considered while deriving a UCD from a case study. Hope it helps !!!!
Title: Re: How we draw a usecase diagram from a case study?
Post by: 1200182002 on April 11, 2020, 02:19:54 pm
identify the Actors (role of users) of the system.
For each category of users, identify all roles played by the users relevant to the system.
Identify what are the users required the system to be performed to achieve these goals.
Create use cases for every goal.
Structure the use cases.
Prioritize, review, estimate and validate the users.