Modelling Class T07 Conceptual Modelling – Behaviour References: –Conceptual Modeling of Information Systems (Chapters 11, 12, 13 and 14)

Slides:



Advertisements
Similar presentations
Requirements Elicitation and Use Case Diagrams
Advertisements

Ver 1,12/09/2012Kode :CIA-230 Anal-Perc.SistemFASILKOM PERTEMUAN-4 Chapter 4. Use Case Analysis.
Modelling Class T05 Conceptual Modelling – Domain References: –Conceptual Modeling of Information Systems (Chapters 1.2.1, 2, 3) –A practical Guide to.
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Object-Oriented Analysis and Design
Introduction To System Analysis and Design
Systems Analysis and Design in a Changing World, Fourth Edition
Slide 1 Systems Analysis & Design CS183 Spring Semester Dr. Jonathan Y. Clark Course Website:
Use Case Modeling Written by: Zvika Gutterman Adam Carmi.
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
Slide 1 Systems Analysis & Design CS183 Spring Semester 2008 Dr. Jonathan Y. Clark Course Website:
© 2005 Prentice Hall4-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Object-Oriented Analysis and Design
System Sequence Diagrams
1 Object-Oriented Modeling Using UML (2) CS 3331 Fall 2009.
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.
Slide 1 UML Review Chapter 2: Introduction to Object-Oriented Systems Analysis and Design with the Unified Modeling Language, Version 2.0 Alan Dennis,
Unified Modeling Language, Version 2.0
Introduction To System Analysis and Design
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
Modelling Class T16: Conceptual Modelling – Architecture Image from
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 8: Behavioral Modeling.
Conceptual Modelling – Behaviour
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Behavioral Modeling Chapter 8.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 02. Objects,
UML-1 3. Capturing Requirements and Use Case Model.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
UML-1 8. Capturing Requirements and Use Case Model.
1 Structuring Systems Requirements Use Case Description and Diagrams.
9-1 © Prentice Hall, 2007 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
♦ Use Case Model  Detailled use case - Important  Use case diagram- Refactoring Use case diagram  > 1 Last Lectures.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
Object Oriented Design Jerry KotubaSYST Object Oriented Methodologies1.
Drawing System Sequence Diagrams
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
CPSC 871 John D. McGregor Module 3 Session 1 Architecture.
Requirements and Use Cases
Systems Analysis and Design in a Changing World, Fourth Edition
 Building Block Building Block  Things in the UML Things in the UML  Structural Things Structural Things  Behavioral Things Behavioral Things  Grouping.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
1 IBM Software Group ® Essentials of Visual Modeling with UML 2.0 Module 5: Interaction Diagrams.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
1 Unified Modeling Language, Version 2.0 Chapter 2.
7-1 © Prentice Hall, 2007 Topic 7: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
UML - Development Process 1 Software Development Process Using UML.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
McGraw-Hill/Irwin© 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 17 Object-Oriented Design and Modeling Using the UML.
Introduction to UML Hazleen Aris Software Eng. Dept., College of IT, UNITEN. …Unified Modeling Language.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 6: Functional Modeling.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
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.
CompSci 280 S Introduction to Software Development
Systems Analysis and Design in a Changing World, Fourth Edition
Analysis Classes Unit 5.
Roberta Roth, Alan Dennis, and Barbara Haley Wixom
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design With UML 2
BTS430 Systems Analysis and Design using UML
Unified Modeling Language
Systems Analysis and Design With UML 2
Software Architecture & Design Pattern
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 22 Object-Oriented Systems Analysis and Design and UML
Presentation transcript:

Modelling Class T07 Conceptual Modelling – Behaviour References: –Conceptual Modeling of Information Systems (Chapters 11, 12, 13 and 14)

Modelação2 Program T01-T02 – Module 1 - Introduction to Systems Modeling T03-T06 – Module 2 - Conceptual Modeling – Domain T07-T11 – Module 3 - Conceptual Modeling – Behavior 1.Overview 2.Flow-Based Behavior 3.Message Based Behavior 4.Event Based Behavior 5.Revision T12-T15 – Module 4 - Ontology T16-T19 – Module 5 - Conceptual Modeling – Architecture T20-T21 – Module 6 - Conceptual Modeling – Methodologies T22-T23 – Module 7 - Ontology: Advanced T24-T25 - Conceptual Modeling – Global Revisions; Exercises, …

Behavior in UML 3Modelação

Behavior in SysML 4Modelação

Behavior in UML and SyML 5Modelação UMLSysML

Behavior – Use Case Diagrams 6Modelação

Use Case Diagrams Use cases describes an interaction between a system and an actor (an external entity). The description must be provided from the point of view of the actor! Therefore, a use case describes "who" can do or is affected by "what" with or from the system. Use cases are also useful to make the bridge between the requirements documenting and the modeling of the detailed systems’ behavior Modelação7

8 The use case template… NameUC-8: Search SummaryAll occurrences of a search term are replaced with replacement text. RationaleWhile editing a document, many users find that there is text somewhere in the file being edited that needs to be replaced, but searching for it manually by looking through the entire document is time- consuming and ineffective. The search-and-replace function allows the user to find it automatically and replace it with specified text. Sometimes this term is repeated in many places and needs to be replaced. Other times, only the first occurrence should be replaced. The user may also wish to simply find the location of that text without replacing it. UsersAll users PreconditionsA document is loaded and being edited. Basic Course of Events 1.The user indicates that the software is to perform a search-and-replace in the document. 2.The software responds by requesting the search term and the replacement text. 3.The user inputs the search term and replacement text and indicates that all occurrences are to be replaced. 4.The software replaces all occurrences of the search term with the replacement text. Alternative Paths 1.In step 3, the user indicates that only the first occurrence is to be replaced. In this case, the software finds the first occurrence of the search term in the document being edited and replaces it with the replacement text. The postcondition state is identical, except only the first occurrence is replaced, and the replacement text is highlighted. 2.In step 3, the user indicates that the software is only to search and not replace, and does not specify replacement text. In this case, the software highlights the first occurrence of the search term and the use case ends. 3.The user may decide to abort the search-and-replace operation at any time during steps 1, 2 or 3. In this case, the software returns to the precondition state. PostconditionsAll occurrences of the search term have been replaced with the replacement text. Not to forget: Use cases are instantiated in scenarios!!!

Use case diagram -«include» and «extend» Modelação9

SysMLUML Behavior in UML and SyML 10Modelação Flow-based behavior Event-based behavior Message-based behavior

Behavior – Activity Diagrams 11Modelação Flow-based behavior

Activity Diagrams (UML) An activity diagram is used to display the sequence of activities involving one or more entities of the system. They show an workflow detailing the decision paths. Activity diagrams are useful for business modeling where they are used for detailing the processes involved in business activities. Modelação12

Activity Diagrams (SysML) An example… Modelação13

Behavior – Interactions (messages)… 14Modelação Message-based behavior

Interactions (messages) Interactions represent exchanges of messages between objects… Modelação15 Pre-defined Interactions in SysML Predefined interactions in UML Call Return Send Create Destroy

Interactions (messages) Semantics of the graphic elements: Modelação16 Synchronous message Return to a synchronous message Asynchronous message Creation of a new object

Behavior – Sequence Diagrams 17Modelação

Sequence Diagrams (UML; SysML) A way to represent interactions between objects, among time… Stress the lifetime of the objects in a specific execution context. Modelação18

Behavior – Communication Diagrams 19Modelação

Communication Diagrams (UML) Show interactions but stressing the relations between the objects involved Relevant to stress collaboration patterns among the objects Modelação20

Behavior – Timing Diagrams 21Modelação

Timing Diagrams (UML) Stress state changes in objects over time… It can represent the same information as in the interactions diagrams and state machine diagrams, but now with detailed information about temporal restrictions and lengths… Modelação22

Behavior – Interaction Overview Diagrams 23Modelação

Interaction Overview Diagrams (UML) Interaction overview diagrams in UML are relevant to describe sequences of action. These diagrams combine elements of activity diagrams with sequence diagrams to show the sequences of action. The elements represented are references to other existing diagrams (activity or interaction in general…). Modelação24

Behavior – State Machine Diagrams 25Modelação Event-based behavior

State Machine Diagrams (UML; SysML) A state machine diagram models the behavior of a single object, specifying the sequence of events that object goes through during its lifetime in response to events. Modelação26

Please never forget that: “A model is the explicit interpretation of one’s understanding of a situation, or merely of one’s ideas about that situation. It can be expressed in mathematics, symbols or words, but it is essentially a description of entities, processes or attributes and the relationships between them. It may be prescriptive or illustrative, but above all, it must be useful” Brian Wilson. Systems: Concepts, Methodologies and Applications. John Wiley and Sons, 1990, 2 nd Edition, page 11 Modelação27

Modelação28