Scribd
Upload
47 views4 pages

18CS2009 - 20CS2050 L-Software Engineering Lab2021-1-BIII: Use Case Diagram

The document discusses use case diagrams, which identify system functionality (use cases), users (actors), and their associations. Use cases describe what a system does at a high level and are used in analysis to define requirements. The key components of use case diagrams are actors, use cases, and associations connecting actors to use cases. An example diagram is provided showing a library information system with actors like members and clerks connected to use cases like search content and review content.

Uploaded by

D ALAN DANIELS URK20CS2065
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
47 views4 pages

18CS2009 - 20CS2050 L-Software Engineering Lab2021-1-BIII: Use Case Diagram

The document discusses use case diagrams, which identify system functionality (use cases), users (actors), and their associations. Use cases describe what a system does at a high level and are used in analysis to define requirements. The key components of use case diagrams are actors, use cases, and associations connecting actors to use cases. An example diagram is provided showing a library information system with actors like members and clerks connected to use cases like search content and review content.

Uploaded by

D ALAN DANIELS URK20CS2065
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

18CS2009 – 20CS2050 L-Software Engineering URK20CS2065

Lab2021-1-BIII
Ex No: 3
Date : 31/07/2021 USE CASE DIAGRAM

AIM:
Use case diagrams identify the functionality provided by the system (use cases), the users who
interact with the system (actors), and the association between the users and the functionality. Use
cases are used in the Analysis phase of software development to articulate the high level
requirements of the system. The primary goals of Use case diagrams include:

• Providing a high-level view of what the system does.


• Identifying the users (actors) of the system.
• Determining areas needing human-computer interfaces.

Use cases extend beyond pictorial diagrams. In fact, text-based use case descriptions are often used
to supplement diagrams, and explore use case functionality in detail.

DESCRIPTION
The basic components of Use case diagrams are the Actor, the Use case and the
Association.

Actor
An Actor, as mentioned, is a user of the system, and is depicted using a stick figure. The
role of the user is written beneath the icon. Actors are not limited to users. If a system
communicates with another application and expects input or delivers output then that application
can also be considered an actor.
18CS2009 – 20CS2050 L-Software Engineering URK20CS2065
Lab2021-1-BIII

Use Case
A Use Case is functionality provided by the system, typically described as verb + object
(eg: Register Car, Delete User). Use cases are depicted with an ellipse. The name of the use case
is written within the ellipse.

Association
Associations are used to link Actors with Use cases, and indicate that an Actor participates
in the Use case in some form. A line connecting the Actor and Use case depicts associations.

The following image shows how these three basic elements work together to form a use case
diagram.
18CS2009 – 20CS2050 L-Software Engineering URK20CS2065
Lab2021-1-BIII

ALGORITHM

Step 1: Define the actors like member, circulation clerk and supplier for the Library Information
System.

Step 2: Determine the events that are necessary for developing a system.

Step 3: Represent the communication relationship of an actor in the system by connecting the
actor symbol to the Use-Case symbol with a solid path.

Step 4: Represent the ‘Uses’ and ‘Extends’ relationship if required.

Step 5: Use the necessary tools for developing the Library Information System.

OUTPUT:
18CS2009 – 20CS2050 L-Software Engineering URK20CS2065
Lab2021-1-BIII

USE CASE SPECIFICATION:

• Private Login: User can login using API’s of Google or Facebook.


• Liked Content: Shows the most liked content based on other’s review.
• Search Content: Allows the user to search for a particular content interested.
• Review Content: Allows the user to write reviews.
• Rate Content: Allows the user to give star rating.
• Trending Page: Based on the reviews and rating given by the users, a page with top 10
best content will be shown.

RESULT:

The Use cases are used in the Analysis phase of software development to articulate the high-
level requirements of the system are drawn successfully.

You might also like