 Engineering Quality Software.  Today o State Diagrams Jerry Kotuba SYST30009-Engineering Quality Software 2.

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

State Charts Mehran Najafi. Reactive Systems A reactive, event-driven, object is one whose behavior is best characterized by its response to events dispatched.
Nested state diagrams:Problems with flat state diagram
Behavioral Modeling: State Diagrams CIS 4800 Kannan Mohan Department of CIS Zicklin School of Business, Baruch College Copyright © 2009 John Wiley & Sons,
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
UML State chart/machine diagram State machine diagram is a behavior diagram which shows discrete behavior of a part of designed system through finite state.
ESE Einführung in Software Engineering 7. Modeling Behaviour Prof. O. Nierstrasz.
ZEIT2301 Design of Information Systems Behavioural Design: State Machines School of Engineering and Information Technology Dr Kathryn Merrick.
Introduction to Software Engineering 7. Modeling Behaviour.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Objectives Detailed Object-Oriented Requirements Definitions
Interaction Diagrams Activity Diagram State Machine Diagram
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 5, Analysis: Dynamic Modeling.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Systems Analysis and Design in a Changing World, 6th Edition
Advanced Behavioral Modeling
Detailed Object-Oriented Requirements Definitions
SE-565 Software System Requirements More UML Diagrams.
Unified Modeling Language(UML) BY
Chapter 10 State Machine Diagrams
State Diagrams / System Sequence Diagrams (SSDs)
1 Object-Oriented Modeling Using UML (2) CS 3331 Fall 2009.
NJIT Modeling Behavior in State Chart Diagrams Chapter 29 Rafael Mello.
Objectives Detailed Object-Oriented Requirements Definitions
Systems Analysis and Design in a Changing World, 6th Edition
Object-Oriented Modeling Using UML CS 3331 Section 2.3 of Jia 2003.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
11 Software Engineering Dr. K. T. Tsang Lecture 9 Advance State Modeling
Submitted By: Memon Khurshed (Group Leader) Hamed Abdollahpur
Activity & Class Modeling Labs Discussion p3 T120B pavasario sem.
CSIS3600 System Analysis and Design Statechart Diagrams.
1 A Student Guide to Object- Oriented Development Chapter 7 State Diagrams.
UML Diagrams: The Static Model Class Diagrams. The Static Model Define the static structure of the logical model Represent classes, class hierarchies.
9-1 © Prentice Hall, 2007 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
UML Discussion on State Machines Perfectly static system is intensely uninteresting Because nothing ever happens.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 5 INTRODUCTION TO SYSTEMS ANALYSIS AND DESIGN: AN AGILE, ITERATIVE APPROACH CHAPTER.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Chapter 11 Activity Diagrams. 2 “Activity diagrams are a technique to describe procedural logic, business processes, and work flows” - M. Fowler An activity.
12 Chapter 12: Advanced Topics in Object-Oriented Design Systems Analysis and Design in a Changing World, 3 rd Edition.
OMT Modeling 1. Object Model : presented by the object model and the data dictionary. 2. Dynamic Model: presented by the state diagrams and event flow.
States.
State Chart diagram Week objective Describe State chart Diagrams in Dynamic Modelling 2.
Statechart Diagrams. Creating a Statechart Diagram A Statechart diagram shows the life cycle of a single object, from the time that it is created until.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 26. Review UML behavioral Diagrams – Sequence diagram.
Scis.regis.edu ● CS-432: Modern Software Engineering Week 4 Dr. Jesús Borrego Lead Faculty, COS Regis University 1.
7-1 © Prentice Hall, 2007 Topic 7: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Modeling Object Lifecycles and State-Dependent Behavior ©SoftMoore ConsultingSlide 1.
Dynamic Models - Page L M.E. Fayad Lesson 30: Dynamic Models Object- Oriented Modeling & Application s.
State Machine Diagram Chapter 5 Introduction Pages
Activity & Class Modeling Labs Discussion p3 T120B pavasario sem.
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
1 Object Oriented Analysis System modeling = Functional modeling + Object modeling + Dynamic modeling Functional modeling = Use cases Object modeling =class.
Appendix 3 Object-Oriented Analysis and Design
Analysis Classes Unit 5.
Software Design Refinement Using Design Patterns
Activity and State Transition Diagram
State Machine Diagrams
Business System Development
UML Diagrams: The Static Model Class Diagrams
Informatics 121 Software Design I
States.
Object Oriented System Design
Chapter 10 Object States and The Statechart Diagram
States.
Appendix 3 Object-Oriented Analysis and Design
Modeling Behavior in Statechart Diagrams
UML State Diagrams (Ch. 29)
Presentation transcript:

 Engineering Quality Software

 Today o State Diagrams Jerry Kotuba SYST30009-Engineering Quality Software 2

Jerry KotubaObject Oriented Methods3

 Learn how to construct a state chart of an object.  Learn how to discover operations (behaviors) for the classes we found by studying object life cycles. Jerry KotubaObject Oriented Methods4

 Objects within the business domain (i.e., the context diagram) o Entity objects  Other objects o Interface objects…user access to the system o Control objects…application or business rule logic Jerry KotubaObject Oriented Methods5

 Models the dynamic aspects of a system as it moves from state to state Jerry KotubaObject Oriented Methods6

Jerry KotubaObject Oriented Methods7

 Lifetimes and Life Cycles  Events and States  Transitions  Actions and Activities  The Statechart Diagram  Object Lifecycles on the Statechart Diagram Jerry KotubaObject Oriented Methods8

Jerry KotubaObject Oriented Methods10

 state diagram exploded into lower levels  states can be exploded into substates Jerry KotubaObject Oriented Methods11

Jerry KotubaObject Oriented Methods12

 SLATE- Week08 o Cell Phone Exercise Jerry KotubaObject Oriented Methods13

 [1] Select the classes that will require statecharts  [2] List all the status conditions for each group  [3] Specify transitions that cause object to leave the identified state  [4] Sequence state-transition combinations in correct order Jerry KotubaObject Oriented Methods14

 [5] Identify concurrent paths.  [6] Look for additional transitions  [7] Expand each transition as appropriate  [8] Review and test each statechart Jerry KotubaObject Oriented Methods15

 SLATE – Week08 o ICE-06 Jerry KotubaObject Oriented Methods16

Jerry KotubaObject Oriented Methods17

 something that happens at a certain point in time  important occurrence that triggers a state transition o i.e. place an order, register for class, apply for loan, hire new employee  An event is considered to be instantaneous

 must be named after the event  may include the following: o [guard condition] shown in square brackets o /action expression action specified after the / slash o parameters of the event i.e. 3 month timeframe

 Concurrency: condition of being in more than one state at a time  Two modes of representation o Use synchronization bars and concurrent paths o Nest low-level states inside higher-level states  Higher-level states also called composite states o Complex structure of sets of states and transitions o Represent a higher level of abstraction Jerry KotubaObject Oriented Methods23

 Read text  What comes next? o Complete state charts o Begin Sequence Diagrams Jerry KotubaObject Oriented Methods24