Scribd
Upload
2 views

Use case Modelling

Use case modeling is a technique used to describe the functional requirements of a system by identifying actors, scenarios, and use cases. For example, in a library system, the primary actor could be a Librarian, with a scenario of issuing a book, where the goal is to successfully lend a book to a patron. Use case relationships, such as include, extend, and generalization, help to define the interactions and dependencies between different use cases.

Uploaded by

vedaraj
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
2 views

Use case Modelling

Use case modeling is a technique used to describe the functional requirements of a system by identifying actors, scenarios, and use cases. For example, in a library system, the primary actor could be a Librarian, with a scenario of issuing a book, where the goal is to successfully lend a book to a patron. Use case relationships, such as include, extend, and generalization, help to define the interactions and dependencies between different use cases.

Uploaded by

vedaraj
Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

Explain with an example, how use case modeling is used to describe functional requirements?

Identify the actors, scenario and use cases for the example

 The Use Case Model describes the proposed functionality of the new system.
 During requirement gathering, the primary requirements of the system are understood. These
basic requirements of the system are called the functional requirements.
 The use cases are the text stories that are designed in order to understand the functionality
of the system.

Use Case template:

Use case Write the name of the scenario.


Primary actor Specify the role of the entity who interacts with the system.
Goal in context Specify the purpose of this use case scenario.
Preconditions The condition that is to be satisfied before the use case start.
Scenario Sequence of steps that describe the main scenario.
Triggers The triggering event due to which the function starts is described.
Extension points The extension points describe the external relationship
Exceptions Describe the exceptional situations that may occur during the execution of the use
case.
Priority Describe the necessity of the system to be implemented.
Open issues Certain additional issues that are required for execution of the scenario.

Use Case Example:


Actors ,Scenarios and Use Case

Actors:

 An Actor is a user of the system. This includes both human users and other computer systems.
 An Actor uses a Use Case to perform some piece of work
 Example : Customer, Inventory database, Accountant

Primary actor - The primary actors are the actors that interact with the system in order to achieve the
user goals. Eg. Librarian is the primary actor for the use case issuing of books.

Supporting actor – The supporting actors are used in conjunction with the primary actors in order to
support for the main services.

Scenario:

 A scenario is a specific sequence of actions or interactions between actors and the system.
 It is also called a use case instance.
 Eg. Scenario of successfully purchasing items, issuing a book from library

Use case and Use case modeling:

 Use case modeling is done during the requirement analysis phase.


 Use cases are the text documents and the use case modeling is an act of writing the text and not
the diagram.
 Use case modeling may include UML diagrams optionally. The use case diagram shows the
actors and related functionalities.

USE CASE RELATIONSHIPS

Use case relationships is divided into three types


1. Include relationship
2. Extend relationship
3. Generalization

1. Include relationship:
 In UML modeling, an include relationship is a relationship in which one use case (the base use
case) includes the functionality of another use case (the inclusion use case).
 The include relationship supports the reuse of functionality in a use-case model.
 Include relationship between use cases is shown by a dashed arrow with an open arrowhead from
the including (base) use case to the included (common part) use case. The arrow is labeled with
the keyword «include».

 Few things to consider when using the <<include>> relationship.


1. The base use case is incomplete without the included use case.
2. The included use case is mandatory and not optional.

2. Extend relationships

 In UML modeling, you can use an extend relationship to specify that one use case (extension)
extends the behavior of another use case (base).
 Extend relationship between use cases is shown by a dashed arrow with an open arrowhead from
the extending use case to the extended (base) use case. The arrow is labeled with the keyword
<<extend>>.
 Here are a few things to consider when using the <<extend>> relationship.
1. The extending use case is dependent on the extended (base) use case.
2. The extending use case is usually optional
3. The extended (base) use case must be meaningful on its own

3.Generalization

 In this relationship there are two types of use cases – the parent use case and the child use case.
 A parent use case may be specialized into one or more child use case that represent more specific
forms of the parent. The child use case inherits all the behavior, structures and relationships of
parents.
 The text word used for generalization relationship is “ kind-of”

You might also like