Use Case Diagram

Get Started. It's Free
or sign up with your email address
Use Case Diagram by Mind Map: Use Case Diagram

1. Actors

1.1. An actor specifies a role that some external entity adopts when interacting with the system DIRECTLY.

1.1.1. Primary Actor A user role. Actors are stakeholders who trigger the user cases Customer triggers the "place order" use case Student triggers the "book squash court" use case Account holder triggers the "withdraw money" use case

1.1.2. Supporting Actor A role played by another system, also known as external actors. Actor that interacts with the use case after it has been triggered. It is often a computer system that may be an organization or person that provides a server to the system Credit card system that provides a server to the "place order" use case to authenticate the customer's credit card and make the necessary deduction "print receipt" will use the Printer (supporting actor) to print the receipt.

2. Naming Conventions

2.1. Actors

2.1.1. Use a singular "noun" phrase

2.1.2. Start each word with an Uppercase letter

2.2. Use Cases

2.2.1. Start with a verb (represents the action) followed by some nouns (the object that the action is directed) E.g. borrow item, return item, renew item

2.2.2. Use present tense for verb, do not use continuous tense

3. Relationships

3.1. Association

3.1.1. Line drawn between an actor and a use case.

3.1.2. Represents the communication link between an instance of the use case and an instance of the actor

3.2. <<include>>

3.2.1. Writing use cases can be repetitive at times There are usually common steps/tasks across use cases of the same system.

3.2.2. Allows you to include the behaviour of one use case into the flow of another use case

3.2.3. Should not be used to create a hierarchical functional decomposition of the system.

3.2.4. Base use case MUST ALWAYS include the behaviour of the inclusion use case.

3.3. <<extend>>

3.3.1. Provides a way to insert new behaviour into an existing use case.

3.3.2. Extension use cases are generally not complete use cases and therefore cannot be triggered by an actor.

3.3.3. You can perceive extension use cases as OPTIONS that the system can branch to from the base use case.

3.3.4. Base use case has the option to call the extension use case.

3.4. Generalization

3.4.1. Shows that one actor can participate in all the associations with use cases that the more general actor can, plus some additional use cases

3.4.2. Shows that one use case provides all the functionality of the more general use case, and some additional functionality.

4. UML

4.1. A family of graphical notations that help in describing and designing software systems, particularly OO systems.

5. Use Case Descriptions

5.1. A simple paragraph to describe what the use case does.

5.1.1. What are the inputs and outputs?

5.1.2. What is recorded?

5.1.3. Are there any conditions to take note of?

5.2. For example, "Assign staff to work on a campaign".

5.2.1. This use case allows the campaign manager to record which staff are working on a particular campaign. A staff should not be assigned to work on more than two campaigns.

6. Prototyping

6.1. Use case modelling can be supported with prototyping.

6.2. Prototypes can be used to help elicit requirements.

6.3. Prototypes can be used to test out system architectures based on the use cases in order to meet the non-functional requirements.

6.4. Uses interface prototypes

6.4.1. Storyboarding can be used with hand-drawn designs.

6.4.2. Can be implemented using languages other than the one that the system will be developed in.

7. Purpose

7.1. To provide an overview of all or part of the usage requirements for a system

7.2. To communicate the scope of a project

7.3. To model the analysis of sage requirements in the form of a system use-case model

8. Formal Definition

8.1. It is used to present a graphical overview of the functionality provided by a system in terms of actors, their goals (use cases) - and any dependencies between those use cases.

9. Use Cases

9.1. A use case is something that an actor wants the system to do.

9.1.1. Primarily Functional Requirement that indicate WHAT the system will do, not HOW to do it.

9.2. Identifying use cases

9.2.1. Find out what each actor wants to use the system for.

9.2.2. Helps to ask What can the system do? What does the actor want the system to do?

9.3. Use case modeling is iterative

9.3.1. You begin with just a name for a use case and fill the details later.

10. Steps in Drawing Use Case Diagrams

10.1. 1. Identify the actors and use cases

10.2. 2. Prioritize the use cases

10.3. 3. Develop each uses case, starting with the priority ones, writing a description for each

10.4. 4. Add structure to the use case model: generalization, include and extend relationships and subsystems