Browse Definitions :
Definition

use case diagram (UML use case diagram)

Contributor(s): Stan Gibilisco

A use case diagram is a graphic depiction of the interactions among the elements of a system. 

A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. In this context, the term "system" refers to something being developed or operated, such as a mail-order product sales and service Web site. Use case diagrams are employed in UML (Unified Modeling Language), a standard notation for the modeling of real-world objects and systems.

System objectives can include planning overall requirements, validating a hardware design, testing and debugging a software product under development, creating an online help reference, or performing a consumer-service-oriented task. For example, use cases in a product sales environment would include item ordering, catalog updating, payment processing, and customer relations. A use case diagram contains four components.

  • The boundary, which defines the system of interest in relation to the world around it.
  • The actors, usually individuals involved with the system defined according to their roles.
  • The use cases, which are the specific roles played by the actors within and around the system.
  • The relationships between and among the actors and the use cases.

A use case diagram looks something like a flowchart. Intuitive symbols represent the system elements. Here's a simple example:

Use case diagram restaurant model

This was last updated in January 2015

Continue Reading About use case diagram (UML use case diagram)

Join the conversation

5 comments

Send me notifications when other members comment.

Please create a username to comment.

Good topic!
Cancel
Had a good exposure for the topic. Thanks for the post.
Cancel
UML is nothing necessarily new. I learned about them when i was in college, as part of ways to visualize requirements and fleshing out designs. The reality is, I haven't seen much UML in use in the last five years. They can still be useful for helping to visualize scenarios in an application, and I believe that many of the feature stories you'll find in agile teams, that the process of making the UML use case diagram is still there behind the scenes, we just don't always draw them out.
Cancel
Hi, I have a question. When do we use stereotype 'private' and 'subtype' in visio for stereotyping uses arrows. Can someone help please?
Cancel
I'm sure you meant "Use case". Everything was mentioned above.

Use cases help to define functional requirements. Functional requirement define WHAT a system must do, but NOT HOW it must be done.

Use cases describe the system functions from the perspective of system users and in a manner and terminology they understand.

Use cases are the beginning of a USE CASE DRIVEN approach to systems analysis and design. They have impact on the analysis, programming, testing and documentation. Use cases are very important.
Cancel

-ADS BY GOOGLE

File Extensions and File Formats

Powered by:

SearchCompliance

  • risk management

    Risk management is the process of identifying, assessing and controlling threats to an organization's capital and earnings.

  • compliance as a service (CaaS)

    Compliance as a Service (CaaS) is a cloud service service level agreement (SLA) that specified how a managed service provider (...

  • data protection impact assessment (DPIA)

    A data protection impact assessment (DPIA) is a process designed to help organizations determine how data processing systems, ...

SearchSecurity

  • cybersecurity insurance (cybersecurity liability insurance)

    Cybersecurity insurance, also called cyber liability insurance or cyber insurance, is a contract that an entity can purchase to ...

  • phishing

    Phishing is a form of fraud in which an attacker masquerades as a reputable entity or person in email or other communication ...

  • cybercrime

    Cybercrime is any criminal activity that involves a computer, networked device or a network.

SearchHealthIT

SearchDisasterRecovery

  • business continuity plan (BCP)

    A business continuity plan (BCP) is a document that consists of the critical information an organization needs to continue ...

  • disaster recovery team

    A disaster recovery team is a group of individuals focused on planning, implementing, maintaining, auditing and testing an ...

  • cloud insurance

    Cloud insurance is any type of financial or data protection obtained by a cloud service provider. 

SearchStorage

  • NVMe over Fabrics (NVMe-oF)

    NVMe over Fabrics, also known as NVMe-oF and non-volatile memory express over fabrics, is a protocol specification designed to ...

  • logical unit number (LUN)

    A logical unit number (LUN) is a unique identifier for designating an individual or collection of physical or virtual storage ...

  • CIFS (Common Internet File System)

    CIFS (Common Internet File System) is a protocol that gained popularity around the year 2000, as vendors worked to establish an ...

Close