Comparison between UML Activity Diagrams and Use Case Maps

Slides:



Advertisements
Similar presentations
Karolina Muszyńska Based on:
Advertisements

1 Review Visual System Modeling Tools Todd Bacastow Penn State University Geospatial System Analysis & Design.
Introduction to UML Todd Bacastow Penn State University Geography 583 Geospatial System Analysis & Design.
1 SWE Introduction to Software Engineering Lecture 16 – System Modeling An Example.
Activity Diagrams [Arlow and Neustadt, 2005] CS 425 / 625 Seminar on Software Engineering University of Nevada, Reno Department of Computer Science & Engineering.
Chapter 10 System Sequence Diagrams. What is a System Sequence Diagram? A way of modeling input and output events related to systems It is a picture that.
1 UML Component and Deployment Diagrams. Models, Views, and Diagrams Use Case Diagrams Use Case Diagrams Use Case Diagrams Scenario Diagrams Scenario.
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Systems Analysis and Design in a Changing World, 6th Edition
Use Case Diagrams. Use Case Use case A view to system seen from outside(user) User’s requirements on system A set of scenario for an actor to achieve.
7M822 UML Interaction Diagrams 25 November 2010.
UFCEPM-15-M Object-oriented Design and Programming Jin Sa.
Unified Modeling Language
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Lecture 6 Unified Modeling Language (UML)
UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.
Data Flow Diagrams Objectives:
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.
Process Analysis Agenda  Multiple methods & perspectives There are lots of ways to map processes  Useful in many situations not just HRIS design  Preparation.
Chapter 14. Activity Modeling for Transformational Systems
Systems Analysis and Design in a Changing World, 6th Edition
Dynamic Modeling Chapter 11 Part of Analysis Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 20. Review Software Requirements Requirements Engineering Process.
 A software application is like a city  Modeling = Architecture  OOP = Civil Engineering  UML Classes = Blueprints of Buildings  UML is a common.
1 Recent work in the area: Requirement-Driven Development of Distributed Applications Gregor v. Bochmann School of Information Technology and Engineering.
For accurate communication, since a project can have several participants, each from different background. Represent a given aspect of the system We will.
Procedures for managing workflow components Workflow components: A workflow can usually be described using formal or informal flow diagramming techniques,
Winter 2007, rev. 2008SEG Chapter 21 Chapter 2 Basic Principles.
PRJ566 System Sequence Diagrams.  A system sequence diagram …. Illustrates input and output events related to the system under discussion.  Larman,
UML Diagrams: The Static Model Class Diagrams. The Static Model Define the static structure of the logical model Represent classes, class hierarchies.
Use Case Modeling Chapter 7 Part of Requirements Modeling Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
1 An Introduction to UML Interaction (Sequence and Communication) Diagrams Georgia State University CIS 3300 Spring, 2009.
Interaction Diagrams Interaction Diagrams allow the designer to show how groups of objects collaborate in some behavior. –Interaction Diagrams will show.
(c) Addison Wesley Copyright © 2000 by Addison Wesley Version 1.0
HNUST, Gregor v. Bochmann, University of Ottawa ICICS International Conference on Information and Communication Systems December 2009 Gregor v.
Object-Oriented Modeling: Static Models. Object-Oriented Modeling Model the system as interacting objects Model the system as interacting objects Match.
UML Diagrams CSC 422 Kutztown University Dr. Daniel Spiegel.
Chapter 11 Activity Diagrams. 2 “Activity diagrams are a technique to describe procedural logic, business processes, and work flows” - M. Fowler An activity.
CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu.
UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
From Workflow to Protocols, Gregor v. Bochmann, University of Ottawa Summary of work done in collaboration with D. Amyot, H. Yamaguchi, T. Higashino,
Chapter 14: Activity Diagrams November 2015 [Arlow and Neustadt, 2005] CS 425/625 Senior Projects University of Nevada, Reno Department of Computer Science.
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
UML Activity Diagrams.
UML - Development Process 1 Software Development Process Using UML.
Capturing Requirements. Questions to Ask about Requirements 1)Are the requirements correct? 2)Consistent? 3)Unambiguous? 4)Complete? 5)Feasible? 6)Relevant?
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
1 More About UML Todd Bacastow Penn State University Geospatial System Analysis & Design.
CS551 - Lecture 7 1 CS551 Interaction Models (Chapter 4 of UML) Yugi Lee STB #555 (816)
Requirements Models Representing the Product in Ways Other than Text.
Systems Analysis and Design in a Changing World, Fourth Edition
Instructor: Dr. Hany H. Ammar
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 8 Advanced Interaction Modeling
BTS430 Systems Analysis and Design using UML
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
UML’s StateChart FSM, EFSM in UML Concurrent states Tool support.
Chapter 6 – System Design II: Behavioral Models
Lecture 4: Activity Diagrams
UML Diagrams: The Static Model Class Diagrams
Process Modeling: Activity/Swimlane Diagrams
Unified Modeling Language
Systems Analysis and Design in a Changing World, 6th Edition
Comparison between UML Activity Diagrams and Use Case Maps
UML Diagrams: Sequence Diagrams Dynamic Analysis Model
Software Design Lecture : 15.
Dynamic Modeling Lecture # 37.
Chapter 14. Activity Modeling for Transformational Systems
Software Development Process Using UML Recap
Presentation transcript:

Comparison between UML Activity Diagrams and Use Case Maps January 2007 Gregor v. Bochmann

Example of Activity Diagram January 2007 Gregor v. Bochmann

Same example as Use Case Map Warehouse Ship Order Office [ Order rejected ] Close Order [ Order accepted ] Receive Order Fill Order Send Invoice Acccept Payment Client Make Payment January 2007 Gregor v. Bochmann

Concepts for the description of requirements (behavior aspects) Each Use Case is a scenario Actions done by actors in some given order Action: Activity / Responsibility Actor: Swimlane / Component Order: sequence, alternatives, concurrency, arbitrary control flows (similar to Petri nets) Abstraction: refinement of activity / Plug-in Data-Flow: Object flow / not in UCMs. Question: what type of data is exchanged (an extension of control flow) Input assertions for input data flow Output assertions for output data flow Conditions for alternatives (also in UCMs) January 2007 Gregor v. Bochmann

Feedback: Privacy Policy Feedback
Do Not Sell My Personal Information
About project: SlidePlayer Terms of Service

© 2024 SlidePlayer.com Inc. All rights reserved.