Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
20 views4 pages

CCC2143 Lab 2

This document provides an overview of use case diagrams in software engineering. It defines a use case diagram as a way to summarize user interactions with a system using UML. Key components of a use case diagram are described, including actors, use cases, relationships, and system boundaries. Guidelines for creating use case diagrams are outlined, like naming conventions for use cases. Examples of use case diagrams for a website and online shopping system are included. The document concludes with instructions for an exercise to design a use case diagram for a chosen system.

Uploaded by

Park Ugyen
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
20 views4 pages

CCC2143 Lab 2

This document provides an overview of use case diagrams in software engineering. It defines a use case diagram as a way to summarize user interactions with a system using UML. Key components of a use case diagram are described, including actors, use cases, relationships, and system boundaries. Guidelines for creating use case diagrams are outlined, like naming conventions for use cases. Examples of use case diagrams for a website and online shopping system are included. The document concludes with instructions for an exercise to design a use case diagram for a chosen system.

Uploaded by

Park Ugyen
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

CCC2143

SOFTWARE ENGINEERING
LAB 2 - USE CASE DIAGRAM

What is a use case diagram?


In the Unified Modeling Language (UML), a use case diagram can summarize
the details of the system's users and their interactions with the system. An
effective use case diagram can help the team discuss and represent:

○ Scenarios in which a system or application interacts with people,


organizations, or external systems
○ Goals that the system or application helps those entities (actors)
achieve
○ The scope of the system

UML use case diagrams are ideal for:


○ Representing the goals of system-user interactions
○ Defining and organizing functional requirements in a system
○ Specifying the context and requirements of a system
○ Modeling the basic flow of events in a use case

Actors in the process, who may be human or other systems, are represented
as stick figures. Each class of interaction is represented as a named ellipse.
Lines link the actors with the interaction. To depict the system boundary, draw
a box around the use case itself. Optionally, arrowheads may be added to
lines to show how the interaction is initiated.

Use case diagram components, symbols and notations:


1. Use cases: Horizontally shaped ovals that represent the different uses
that a user might have.
2. Actors: Stick figures that represent the people actually employing the
use cases.

1
3. Associations: A line between actors and use cases. In complex
diagrams, it is important to know which actors are associated with
which use cases.
4. System boundary boxes: A box that sets a system scope to use cases.
All use cases outside the box would be considered outside the scope
of that system.
5. Packages: A UML shape that allows you to put different elements into
groups. Just as with component diagrams, these groupings are
represented as file folders

Use Case Diagram Guidelines:


1. Use Cases:
- Names begin with a verb
- Make the name descriptive
- Place included use cases to the right of the invoking use case
2. Relationships:
- Arrow points to the base use case when using <<extend>>
- <<extend>> can have optional extension conditions
- Arrow points to the included use case when using <<include>>
- Both <<extend>> and <<include>> are shown as dashed arrows
3. Systems:
- Use them sparingly and only when necessary
- Give meaningful and descriptive names to these objects

2
Example 1 Website Development

Example 2 Online Shopping System

3
How to create a Use Case Diagram?
1. Identify Actors
2. Identify Use Cases
3. Look for Common Functionality to use <<include>>

Exercise
1. Choose one of the following system applications:
a. ATM system
b. Food delivery service
c. Student course registration system
d. Bus booking system
e. Library system
2. Write one (1) user requirement definition for the chosen system
3. Write at lease three (3) system requirements specification (functional
requirements) based on user requirement in no. 3.
4. Draw a use case diagram for the proposed system based on the
requirements above. You need to:
a. identify the actors involved in the system
b. show the actors’ interactions with the system
c. indicate clearly the functions which the actors interact with
5. Save the diagram in Word document/Google Docs format
6. Submit your work at the end of the lab session to Moodle

Note:
Use Case Diagram using LucidChart.
Video to create a Use Case Diagram.

You might also like