Scribd
Upload
40 views14 pages

UML - Lec Use Case Diag

UML is a standardized modeling language used to design software systems. It defines 14 types of diagrams divided into structure, behavior, and interaction categories. Common diagrams include use case diagrams, which model interactions between users and a system, and class diagrams, which show the structure of and relationships between classes.

Uploaded by

JAYAKRISHNAN.K.R
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
40 views14 pages

UML - Lec Use Case Diag

UML is a standardized modeling language used to design software systems. It defines 14 types of diagrams divided into structure, behavior, and interaction categories. Common diagrams include use case diagrams, which model interactions between users and a system, and class diagrams, which show the structure of and relationships between classes.

Uploaded by

JAYAKRISHNAN.K.R
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/ 14

UML

Software Development- Systematic


approach
What is UML and Why we use UML?

 UML → “Unified Modeling Language”


 Language: express idea, not a methodology

 Modeling: Describing a software system at a high level of


abstraction

 Unified: UML has become a world standard


Object Management Group (OMG): www.omg.org
How to use UML diagrams to design software system?
UML 2.2 defines fourteen types of diagrams, divided into three
categories:
• Structure Diagrams- Class Diagram, Object Diagram,
Component Diagram, Composite Structure Diagram, Package
Diagram, Profile Diagram and Deployment Diagram.
• Behavior Diagrams- Use Case Diagram, Activity Diagram, and
State Machine Diagram.
• Interaction Diagrams- Sequence Diagram, Communication
Diagram, Timing Diagram, and Interaction Overview Diagram.
How to use UML diagrams to design software system?
Use Case and Use Case Diagram
• A use-case diagram is a set of use cases
• A use case is a model of the interaction between
 External users of a software product (actors) and
 The software product itself
 Actor is a user playing a specific role

• describing a set of user scenarios


• capturing user requirements
• contract between end user and software developers
Use-Case
Login
UC Name Login
Description Allows user to enter in the system
Primary Actor All Users of System
Stakeholders and Users wants to enter in the system
Interest
Precondition User is not logged into the system
Post condition User is in the system after successful login
Main Success 1. The User Enter Username and password
Scenario 2. System verifies the user
3. User is able to login if user is validated else system
doesn’t allow any anonymous user to enter into the
system
Frequency of Once
Occurrence
Miscellaneous None
Use-Case Diagrams

Boundary Use Case


Actor Library System

Borrow Employee
Client

Order Title

Fine Remittance

Supervisor
Use-Case Diagrams
• Actors: A role that a user plays with respect to the system, including human
users and other systems. e.g., inanimate physical objects (e.g. robot); an
external system that needs some information from the current system.

• Use case: A set of scenarios that describing an interaction between a user


and a system, including alternatives.

• System boundary: rectangle diagram representing the boundary between


the actors and the system.
Use-Case Diagrams
• Association:
communication between an actor and a use case; Represented by a solid line.

• Generalization: relationship between one general use case and a special use case
(used for defining special alternatives) Represented by a line with a triangular arrow
head toward the parent use case.
Use-Case Diagrams

Include: a dotted line labeled <<include>> beginning at base


use case and ending with an arrows pointing to the include use
case. The include relationship occurs when a chunk of
behavior is similar across more than one use case. Use
“include” in stead of copying the description of that behavior.
<<include>>

Extend: a dotted line labeled <<extend>> with an arrow toward


the base case. The extending use case may add behavior to the
base use case. The base class declares “extension points”.

<<extend>>
Use-Case Diagrams

Figure 16.12
The McGraw-Hill Companies, 2005
Use-Case Diagrams
• Both Make Appointment
and Request Medication
include Check Patient
Record as a subtask
(include)

• The extension point is


written inside the base
case Pay bill; the
extending class Defer
payment adds the
behavior of this extension
point. (extend)

• Pay Bill is a parent use


case and Bill Insurance
is the child use case.
(generalization)

(TogetherSoft, Inc)
What UML Modeling tools we use today?

• List of UML tools http://en.wikipedia.org/wiki/List_of_UML_tools


• StarUML
• Microsoft Visio
• ArgoUML
Acknowledgements
 Object-Oriented and Classical Software Engineering, Sixth Edition,
WCB/McGraw-Hill, 2005 Stephen R. Schach

 UML resource page http://www.uml.org/

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy