Author Topic: use case actors  (Read 21092 times)

12205210302

  • Guest
Re: use case actors
« Reply #90 on: July 14, 2022, 01:14:14 pm »
The primary actor is the one that initiates a use case.
A secondary actor is the one that helps completion of the use case through his specific support.
The Primary actor is usually placed at the left side to the boundary of the system and the secondary actor is placed to the right of the boundary of the system.

12215201301

  • Guest
Re: use case actors
« Reply #91 on: July 15, 2022, 03:36:09 pm »
Actors are classified into primary actors (also called active actors) and secondary actors (also called passive actors). Primary actors initiate

a use case and hence are somewhat independent. Secondary actors, on the other hand, are used by the system but they do not interact with the system on their own.

12228280305

  • Guest
Re: use case actors
« Reply #92 on: July 26, 2022, 12:59:45 pm »
Primary Actor - Primary actors are the one who initiates or perform some action .

Secondary Actor - Secondary actors are the one who support system action .

Eg :   customer is making payment through online to bank
 
          Here Customer is primary Actor and Bank will be the Secondary actor .

12212216902

  • Guest
Re: use case actors
« Reply #93 on: August 03, 2022, 03:37:19 pm »
An actor in use case modeling specifies a role played by a user or any other system that interacts with the subject.
An Actor models a type of role played by an entity that interacts with the subject (e.g., by exchanging signals and data), but which is external to the subject.
Actors may represent roles played by human users, external hardware, or other subjects.
Actors do not necessarily represent specific physical entities but merely particular facets (i.e., ?roles?) of some entities that are relevant to the specification of its associated use cases.
A single physical instance may play the role of several different actors and a given actor may be played by multiple different instances.
Types of actors include:

Users
database systems
clients and servers
cloud platforms
devices

12230256704

  • Guest
Re: use case actors
« Reply #94 on: August 06, 2022, 07:28:31 am »

A use case diagram shows the interaction between the system and entities external to the system. These external entities are referred to as actors. Actors represent roles that may include human users, external hardware, or other systems

12217235602

  • Guest
Re: use case actors
« Reply #95 on: August 06, 2022, 11:46:33 am »
1)Primary/principle Actor: People who use the main system functions are referred to as primary or principle actors. For example: in an ATM system primary actor is the customer.
2)Secondary Actor: People who perform administratively or maintenance tasks are referred to as secondary actors
The primary actor of a use case is the actor who specifies the user goal and usually also initiates an interaction with the use case. The secondary actor (also called the supporting actor) never initiates an interaction with the use case, and it does not trigger it in any way.

12202253104

  • Guest
Re: use case actors
« Reply #96 on: August 06, 2022, 01:49:00 pm »
USE CASE
What is a use case? Use cases explained
A use case is a description of the ways in which a user interacts with a system or product. A use case may establish the success scenarios, the failure scenarios, and any critical variations or exceptions. A use case can be written or made visual with the help of a use case model tool.
What is the purpose of a use case?
The purpose of a use case is to:
?   Manage scope
?   Establish requirements
?   Outline the ways a user will interact with the system
?   Visualize system architecture
?   Communicate technical requirements to business stakeholders
?   Risk management
Why do project managers need to know about use cases?
Project managers need to know about use cases because they help communicate strategy to stakeholders and bridge the gap between business justification and technical requirements.
PMI also notes that ?use cases provide a structure for gathering customer requirements and setting the project scope.? But what does that mean in practical terms?
Let?s say that you are a project manager for an education tech firm. Your company?s latest product idea is an app for students where they can receive live tuition for a monthly subscription fee. Creating a use case for this application can tell stakeholders and the project team who the customer is, how the customer will interact with the product, and what the scope gap meaning and requirements of the project will be.
How to write a use case for a project
When presented in written form, a use case can be a helpful piece of project documentation. Use cases are a common requirements artifact, and they can smoothen communication across technical and business stakeholders.
Depending on the intended audience and system under discussion, the use case can be as detailed or basic as needed. A use case document should establish and identify a few key components ? these are:
?   System: A system is the product, service, or software under discussion. 
?   Actors: An actor is a user or anything else that exhibits behavior when interacting with the system. The actor could be another system, a piece of hardware, or an entire organization. There are four types of actors: a system under discussion, an internal actor, a primary actor, and a secondary actor. The most commonly referred to are the latter two systems. A primary actor initiates the interaction with the system, while a secondary actor may provide a service to the system.
?   Scenario: In ?Applying UML and Patterns,? Larman notes that ?a scenario is a specific sequence of actions and interactions between actors and the system under discussion; it is also called a use case instance.?
?   Use case: A use case outlines the success and failure scenarios that can occur when the actor(s) interact with the system. In this section, you?d establish the main success scenario.
Let?s take a look at a simple use case example:
?   Use case for meal delivery application: Individuals can use an app to place food orders directly to restaurants. When the user places an order, they are prompted to pay through the app or pay when the food arrives. Once that is confirmed, the restaurant will receive a request through their system. The food will then be prepared, packaged, and delivered to the individual. In this case, the app must be able to receive orders, process payments, and communicate with the restaurant electronically.
?   System: Food delivery application
?   Primary actor: Customer ordering a meal
?   Scenario: The user browses restaurant options. Once the preferred restaurant is selected, they place an order through the application. The user pays online or verifies they will pay in person. The order is sent from the app to the restaurant?s internal system. The restaurant worker receives and processes the electronic order.

This use case illustrates how both the customer and restaurant employee (the actors) interact with the food delivery application (the system) and the expected outcome of each interaction.

This helps sketch a framework for what is expected in the development stage. The app must be able to process payments, for example.

12228258603

  • Guest
Re: use case actors
« Reply #97 on: August 10, 2022, 11:31:17 am »
An actor specifies a role played by a user or any other system that interacts with the subject. It may represent roles played by human users, external hardware, or other subjects. Actors are always outside the system and interact directly with it by initiating a use case, provide input to it, and/or receive outputs from it. While a single physical instance may play the role of several different actors, an actor does not necessarily represent specific physical entities, i.e. a timer that triggers sending of an e-mail reminder.

12221291005

  • Guest
Re: use case actors
« Reply #98 on: August 10, 2022, 03:39:10 pm »

Can Anyone explain me Who are Use Case Actors

Use case actor is external entities which is out side of the system boundary i.e., human users, external hardware or other systems.


 i.e., Primary Use case Actors Vs Secondary Use case Actors
Primary actors are initiate a use case and hence are somewhat independent. secondary actors are used by the system but they do not ineract with the system on their own it means they are somewhat dependent.

12221277305

  • Guest
Re: use case actors
« Reply #99 on: August 11, 2022, 01:58:59 pm »
Actors. A use case diagram shows the interaction between the system and entities external to the system. These external entities are referred to as actors. Actors represent roles which may include human users, external hardware or other systems.
A use case must be connected to at least one actor or to at least one use case. Otherwise, the use case may stand alone which is not useful. If it is connected to an actor, the connection must be an association.

12223223904

  • Guest
Re: use case actors
« Reply #100 on: August 15, 2022, 12:37:12 am »
There are two type of actors,

Primary actors are those who directly interreact with the system for e.g., Customer
Secondary actors are those who support the system . for e.g., Database server

12210216801

  • Guest
Re: use case actors
« Reply #101 on: August 15, 2022, 11:34:11 pm »
in a use case diagram typically there are two actors, primary actor and a secondary actor. Primary actors initiate the use cases of the system that may be business processes or application functionality.  A use case within the system may have more than one primary actor, since more than one type of role may initiate the processes or functionality of the system. The system, and its use cases, often rely on other people, business processes, or applications in order to obtain a result or specific information required to achieve its goal.  These are called Secondary Actors.  A secondary actor is one from which the system requires assistance to complete the use case.

12202217304

  • Guest
Re: use case actors
« Reply #102 on: August 16, 2022, 05:19:21 pm »
Primary actors are the ones that directly interact with the system. They cause actions but secondary actors are the ones that help primary actors to get the action completed but they do not directly interact with the system.

12221283105

  • Guest
Re: use case actors
« Reply #103 on: August 19, 2022, 02:39:32 pm »
Primary Actor - Primary actors are the one who initiates or performs some action.

Secondary Actor - Secondary actors are the ones who support system action.

For example - the customer is making a payment through online.
Here, the Customer,is the primary Actor and Bank will be the Secondary actor.

pradip

  • Guest
Re: use case actors
« Reply #104 on: August 19, 2022, 09:30:28 pm »
Primary Actor - Primary actors are the one who initiates or perform some action .

Secondary Actor - Secondary actors are the one who support system action .

Example: Online payment :
a) Customer who making payment using payment function are called primary actor.
b)when customer choose credit card mode to make payment and action can to completed without Third party system or DB is called secondary actor. Here Bank is secondary actor