Chap 28 UML Activity Diagrams and Modeling

Slides:



Advertisements
Similar presentations
© 2005 by Prentice Hall Appendix 3 Object-Oriented Analysis and Design Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Advertisements

Modeling Main issues: What do we want to build How do we write this down ©2008 John Wiley & Sons Ltd. vliet.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Introduction To System Analysis and Design
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Introduction to UML Part 2 Behavioral Modeling. Sequence (event) diagram Describes object interaction Typically captures behavior of a single use case.
L3-5d-S1 Class Diagrams © M.E. Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room.
© Copyright Eliyahu Brutman Programming Techniques Course.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
SwE 313 Introduction to Rational Unified Process (RUP)
Requirements Analysis Activity Diagrams b511.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis.
Activity Diagrams Derived from several techniques: Event diagrams of Jim Odell SDL state modeling techniques Workflow modeling Petri nets Especially useful.
Chapter 28 Activity Diagrams Model processes: –Business processes –Workflow –Data flow –Complex algorithms.
Unified Modeling Language
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
Chapter 8: Modelling Interactions and Behaviour UML Activity Diagram
Software Engineering 1 Object-oriented Analysis and Design Chap 29 UML State Machine Diagrams and Modeling.
RUP Design RUP Artifacts and Deliverables
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
Chapter 7 System models.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Behavioral Modeling Chapter 8.
ניתוח מערכות מידע 1 Unified Modeling Language (UML) § § The Unified Modeling Language (UML) is the industry-standard language for: Specifying, Visualizing,
Fall 2010 CS4310 Requirements Engineering A Brief Review of UML & OO Dr. Guoqiang Hu Department of Computer Science UTEP 1.
Activity diagrams. Introduction ● Activity diagrams are a behavioural model that represent the dynamics of the system. ● An activity diagram is essentially.
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 43 Introduction to Software Engineering.
 28object-oriented_programming%29 28object-oriented_programming%29.
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
Object-Oriented Analysis and Design CHAPTER 10: SYSTEM SEQUENCE DIAGRAMS 1.
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
University of Utah SoCCS Lecture 121 Dynamic Models in Design CS6961 – Lecture 12 Nathan Dykman.
Dr.Basem Alkazemi
1/26 On-demand Learning Series Software Engineering of Web Application - Object-Oriented Development & UML Hunan University, Software School.
Modeling as a Design Technique Chapter 2 Part 1: Modeling Concepts Object-Oriented Modeling and Design Byung-Hyun Ha
The Rational Unified Process 1 EECS810: Software Engineering.
Object-Oriented Analysis and Design CHAPTERS 9, 31: DOMAIN MODELS 1.
CSCI-383 Object-Oriented Programming & Design Lecture 12.
Chapter 11 Activity Diagrams. 2 “Activity diagrams are a technique to describe procedural logic, business processes, and work flows” - M. Fowler An activity.
A Student Guide to Object-Oriented Development
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
TK2023 Object-Oriented Software Engineering CHAPTER 9 INTRODUCTION TO OBJECT DESIGN.
Larman chapter 101 Domain Model: Visualizing concepts Larman chapter 10.
Software Engineering 1 Object-oriented Analysis and Design Chap 31 More SSDs and Contracts.
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
Technical Module C Object Modeling Objects Object – a valuable resource: Money (Account Receivable) Material (Product) Machines (Delivery Truck) Personnel.
WELCOME TO OUR PRESENTATION UNIFIED MODELING LANGUAGE (UML)
Elaboration: Iteration 3. Elaboration: Iteration 3 Basics Inception and iteration-1 explored many basic OOA/D modeling basics. Iteration-2 narrowly emphasized.
Introduction to UML.
CSSE 374: UML Activity Diagrams
Chapter 8: Modelling Interactions and Behaviour UML Activity Diagram
Activity Diagrams.
Business System Development
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4th edition, Prentice Hall, Hans Van Vliet, Software Engineering:
Appendix 3 Object-Oriented Analysis and Design
Ch. 28 Larman UML & Patterns
Presentation transcript:

Chap 28 UML Activity Diagrams and Modeling

Activity Diagram 1 Once an action is finished, there is an automatic outgoing transition The diagram can show both control flow and data flow a sequence of activities, including parallel activities. for visualizing business workflows and processes, and use cases. Business Process Modeling The partitions are useful to see the multiple parties and parallel actions involved in the business process Data Flow Modeling the UML data store node is applicable

Activity Diagram 2 Receive Video Order Fill Order Send Invoice Deliver Receive Payment Close Order Fulfillment Customer Service Finance Invoice start Action . It does something There is an automatic transition on its completion A transition supports modeling of control flow Fork One incoming , and multiple outgoing parallel transitions and / or object flows Partitions Show different parties involved in the process Join Multiple incoming transitions and or object flows ; one outgoing transition The outgoing continuation does not happen until all the inputs arrive from flows Object Node An object produced or used by actions This allows us to model data end of activity

Activity Diagram 3 Student Registration System Application Complete Check Course Availability «datastore» Courses Applications Check Applicant Qualification Students Accept / Deny Reply

Expanded activity to Another Diagram

Model Events as Action

Guidelines This technique proves most valuable for very complex processes, usually involving many parties. If modeling a business process, take advantage of the "rake" notation and sub-activity diagrams. "level 0" diagram keep all the actions at a very high level of abstraction. Expand the details in sub-diagrams at the level 1, and perhaps even more at the level 2. to make the level of abstraction of action nodes roughly equal within a diagram. bad example: suppose in a "level 0" diagram there is an action node labeled "Deliver Order." And, a second action node "Calculate Tax." Those are very different levels of abstraction.

NextGen POS Activity Diagram [ cash payment ] Enter Cart Items Calculate Taxes and Discounts Customer Cashier NextGen POS Receipt Shop and Fill Cart Submit Authorization Request else Create Receipt Hand Over Items Service Authorize Payment

Activity Diagrams in the UP UP disciplines - Business Modeling its purpose is to understand and communicate the structure and the dynamics of the organization in which a system is to be deployed. A key artifact of the Business Modeling discipline is the Business Object Model (a superset of the UP Domain Model), which essentially visualizes how a business works, using UML class, sequence, and activity diagrams.