WHAT IS A Use Case Diagram?

Slides:



Advertisements
Similar presentations
Requirements Diagrams With UML Models
Advertisements

Use Case Diagrams.
Day 11 – UML and Use Case Diagrams
Michael C. Daconta Chief Technology Officer, AIM.
Stimulate 2005 Instructor: Luz M. Quiroga University of Hawaii Information and Computer Science / Library and information Science POST.
Appendix Object-Oriented Analysis and Design: Use Cases Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Systems Analysis and Design 8th Edition
Object-Oriented Analysis and Design
Object-Oriented Analysis and Design
Drawing System Sequence Diagrams
Chapter 18 Object-Oriented Systems Analysis and Design Using UML
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Analyzing systems process: Use Case Diagram.
© 2005 Prentice Hall4-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Use Case Modeling.
Marcelo Santos – OOAD-CDT309, Spring 2008, IDE-MdH 1 Object-Oriented Analysis and Design - CDT309 Period 4, Spring 2008 More on use cases System sequence.
Chapter 3 : Software Process and Other Models Juthawut Chantharamalee Curriculum of Computer Science Faculty of Science and Technology, Suan Dusit University.
Unified Modeling Language
Use Case Diagrams Week 1 – Lab 1.
USE Case Model.
程建群 博士(Dr. Jason Cheng) 年03月
Data Flow Diagram A method used to analyze a system in a structured way Used during: Analysis stage: to describe the current system Design stage: to describe.
Entity Relationship Diagrams Objectives s Learn the Elements of the E-R model (entities, attributes, and relationships) s Show how to apply the E-R model.
Requirements Determining the requirements of software involves determining the needs of the users of the software. Determining the requirements of software.
SWEN 5130 REQUIREMENTS ENGINEERING Unified Modeling Language Short Tutorial By Yuvaraj Mani Teaching Assistant SWEN 5130 Spring semester 2006.
ICONIX P ROCESS FOR S OFTWARE D EVELOPMENT Hoang Huu Hanh, Hue University hanh-at-hueuni.edu.vn 1.
Chapter 18 Object-Oriented Systems Analysis and Design Using UML
UML What Is the UML? The Unified Modeling Language (UML) is the successor to the wave of object- oriented analysis and design (OOA&D) methods.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts UML UML: Unified Modeling Language UML has many components to graphically model different.
Systems Analysis & Design 7 th Edition Chapter 5.
Systems Analysis and Design 8 th Edition Chapter 6 Object Modeling.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Slide 1 Use Case Diagrams.
♦ Use Case Model  Detailled use case - Important  Use case diagram- Refactoring Use case diagram  > 1 Last Lectures.
Carmen David, Senior BA Business Analysis Carmen David, Senior BA Business Analysis Foundation in Business Analysis Session 7 MODELLING REQUIREMENTS.
Use Cases, Part I Understanding the Business Dynamics  Understand the business workflow  Identify system support points the system 'use cases'
Drawing System Sequence Diagrams
COMP-350 Object-Oriented Analysis and Design Drawing System Sequence Diagrams Reference: Larman, Chapter 9.
 An entity-relationship diagram (ERD) is a specialized graphic that illustrates the interrelationships between entities in a database.
Use Case Diagrams.
Business Process and Functional Modeling Teguh Sutanto, S.Kom.,M.Kom.
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
 What to do if you want to build a new house? › Buy a bunch of wood and nails and start immediately. › Or, put some blueprints to follow, and plan of.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Ondřej Přibyl Faculty of Transportation Sciences, CTU DESIGN OF ITS SYSTEMS Project support 1 3 PROJECT SUPPORT Use cases.
TA: Shreya Rawal.  A use case is a description of a system’s behavior as it responds to a request that originates from outside of that system (Usually.
George Wang, Ph.D. COMP 380/L Lesson 2. Use Case Use cases are a way to capture system functionalities (i.e., functional requirements) Based on use case.
WHAT IS A Context Diagram?
Business Process and Functional Modeling
WHAT IS A Process Map? Illustration of the sequence of activities, inputs and outputs to the activities, and relationship across multiple functions, or.
UML Diagrams By Daniel Damaris Novarianto S..
Entity Relationship Diagram
Storyboarding and Game Design SBG, MBG620 Full Sail University
Objectives Importance of Requirement Engineering
M.M. Pickard, PhD A Primer on Use Cases (Reference: UML Superstructure Specification, v2.1.1)
Use Case Model.
Rob Gleasure IS3320 Developing and Using Management Information Systems Lecture 8: Use Cases and Scenarios Rob Gleasure.
Start at 17th March 2012 end at 31th March 2012
UML Diagrams Jung Woo.
UML PPt by: Hong Qing Yu.
CH#3 Software Designing (Object Oriented Design)
Concepts, Specifications, and Diagrams
Secondary Cause / Effect 1 Tertiary Cause / Effect 1 Primary Effect
Chapter 9 Use Cases.
COP 4331 Recitation #1 University of Central Florida
Unified Modeling Language
COP 4331 Recitation #1 University of Central Florida
What is a Relationship Map?
Chapter 5.
COP 4331 Recitation #1.
Secondary Cause / Effect 1 Tertiary Cause / Effect 1 Primary Effect
Presentation transcript:

WHAT IS A Use Case Diagram? An illustration of a system’s intended functions (user goals), its surroundings (actors), and relationships between the user goals and actors Unified Modeling Language

EXAMPLE

EXAMPLE

Step 1: Identify System Domain Select an entity as a focal point Draw a box Label the system domain

Step 2: Identify Actors Identify the entities that have direct interaction with the system domain Draw a stick figure for each actor

What is a Primary or Secondary Actor? Primary actors initiate interaction with the System Domain to achieve a goal Who “Knocks”? Secondary actors are called by the System Domain for assistance to achieve the primary actor’s goal Tip: Position Primary Actors on the left side and Secondary Actors on the right side of the System Domain

Step 3: Name user goals Identify WHY an actor would initiate interaction with the System Domain Draw a horizontal ellipse or oval Goal is stated in verb-noun format Example Goals: Search for Account Apply Payment Open New Account Search for Account

Step 4: Connect Actors to Goals Primary actors initiate interaction with the System Domain to achieve a goal Secondary actors are called by the System Domain for assistance to achieve the primary actor’s goal Primary Actor Secondary Actor