Analysis Modeling Dynamic Modeling. Requirements analysis Results in static and dynamic models – Scenario models: use cases (static), swimlane diagrams.

Slides:



Advertisements
Similar presentations
System Sequence Diagrams
Advertisements

1 Behavioral Modeling Chapter 8. 2 Key Ideas Behavioral models describe the internal dynamic aspects of an information system that supports business processes.
Analysis Modeling Static Modeling.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Sequence Diagrams. Introduction A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods in each object, and.
7M701 1 Activity Diagram. 7M701 2 Example 7M701 3 Activity Diagram: what is it? Describes activities and flows of data or decisions between activities.
Interaction Diagrams Activity Diagram State Machine Diagram
Software Engineering COMP 201
SE 555 Software Requirements & Specification 1 Activity Diagrams.
Essentials of interaction diagrams Lecture 23 & 24.
State Change Modelling. Aim: To introduce the concept and techniques for describing the changes in state that may occur to an object in its lifetime.
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Modern Systems Analysis and Design Fifth Edition Jeffrey A
SE-565 Software System Requirements More UML Diagrams.
1 Lab Beginning Analysis and Design 4 Completion of first version of use case diagram initiates the processes of analysis and design. 4 UML provides.
Coming up: Interaction Diagrams
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Prof. Hany H. Ammar, CSEE, WVU, and Dept. of Computer Science, Faculty.
State and Sequence Diagrams Modelling dynamic information So far we have seen: Use Case Diagrams – requirements capture, interface.
Class, Sequence and UML Model.  Has actors and use cases.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
CS 325: Software Engineering March 3, 2015 Activity Modeling for Transformational Systems Trtansformational Systems UML Activity Diagrams.
Use Case Modeling. Watch the video on use cases Review at minute 2:41-3:37.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 25. Review Design Level Class Diagram Identifying classes/Operations/Attributes Associations – Simple associations.
10/17/01H-1 © 2010 T. Horton CS 4240: Principles of SW Design Interaction Diagrams Examples of Collaboration and Sequence Diagrams Phone modeling exercise.
Interaction Models (2): Sequence Diagrams Extracted from textbook: Object Oriented Modeling and Design with UML M. Blaha, J. Rumbaugh 1.
Behavioral Modeling: Sequence and Communication Diagrams Copyright © 2009 John Wiley & Sons, Inc. Copyright © 2005 Pearson Education Copyright © 2009 Kannan.
Behavioral Modeling Chapter 8.
Programming Logic and Design Fourth Edition, Comprehensive Chapter 15 System Modeling with the UML.
UML -Part 3. Dynamic Diagram Types Interaction Diagrams - Set of objects or roles and the messages that can be passed among them. – Sequence Diagrams.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
1 Use Case Modeling Reference: RUP Doc. Use Case Example 2.
Copyright © 2013 Curt Hill UML Unified Modeling Language.
Smith’s Aerospace © P. Bailey & K. Vander Linden, 2005 Interaction and Communication Diagrams Patrick Bailey Keith Vander Linden Calvin College.
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
Coming up: Interaction Diagrams Sequence Diagrams Dan Fleck.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour UML Sequence Diagram.
Object Oriented Analysis and Design Sequence Diagrams.
Use Case Driven Analysis Requirements Use Case Use Case Description System Sequence Diagram Chapter 5.
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
UNIFIED MODELING LANGUAGE(UML) BY Touseef Tahir Lecturer CS COMSATS Institute of Information Technology, Lahore.
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.
CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.
Dynamic Models Sequence Diagrams Collaboration Diagrams Activity Diagrams.
Coming up: Interaction Diagrams Sequence Diagrams Dan Fleck.
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Object-Oriented Systems Analysis and Design Using UML Systems Analysis and Design,
Chapter 3: Introducing the UML
 Activity diagram is basically a flow chart to represent the flow from one activity to another activity.
Chapter 7 Behavioral Modeling Brandon A. Jones Stand and Deliver ITEC March 6, 2011.
ITEC1301 Object-Oriented Systems Construction Lecture Notes #4 1.
CompSci 280 S Introduction to Software Development
Activity Diagrams Dan Fleck Coming up: Activity Diagram.
Analysis Classes Unit 5.
CHAPTER
Information Delivery Manuals: Process Mapping
Activity and State Transition Diagram
Visit for more Learning Resources
Analysis Modeling Dynamic Modeling.
Chapter 8: Modelling Interactions and Behaviour UML Activity Diagram
Business System Development
UML Activity Diagrams.
Activity Diagrams (Ch 8)
Process Modeling: Activity/Swimlane Diagrams
IMAT5205 Systems Analysis and Design
UML Diagrams: Sequence Diagrams Dynamic Analysis Model
Activity Diagrams Dan Fleck Coming up: Activity Diagram.
CIS 375 Bruce R. Maxim UM-Dearborn
Activity Diagrams Dan Fleck Coming up: Activity Diagram.
CIS 375 Bruce R. Maxim UM-Dearborn
Appendix 3 Object-Oriented Analysis and Design
Presentation transcript:

Analysis Modeling Dynamic Modeling

Requirements analysis Results in static and dynamic models – Scenario models: use cases (static), swimlane diagrams (dynamic) – Class diagrams (static) – Flow oriented diagrams (dynamic) – Behavioral models: sequence diagrams (dynamic), state diagrams (dynamic) These models bridge the gap between requirements and implementation (code)

Activity/Swimlane diagrams Help us visualize the flows associated with use cases A swimlane diagram has multiple actors; an activity diagram is the same thing, but no concrete actors are distinguished

Other syntax Concurrency can be modeled by fork/join We can include one diagram inside of another – Enables reuse Fork/Branc h Join

Swimlane diagrams Start circle Ends in bulls-eye Decisions are diamonds (must always have a guard on all branches)

Sequence diagrams Used to model interactions between classes/objects Emphasis on time ordering Message passing between objects

Sequence Diagram Example messages are methods of the classes Synchronous message Asynchronous message Return message

Messages in sequence diagrams Messages, along horizontal lines, correspond to operations in your class diagram; i.e. they are method calls Three main types – Synchronous: expects return – Asynchronous: does not expect return – Return argument: dashed line Synchronous message Asynchronous message Return message

Sequence Diagram: option

Sequence diagram: Alternate/else

Sequence diagram: loop

State diagrams Once sequence diagrams have been constructed for each use case, a state diagram can be built for the system Can model the: – State of each class – State of the system as viewed from the outside

State diagram syntax 13 State Name (verb in current tense) (Optional) actions happening during state Name Examples: sorting validating updating status … [age > 20] [age <= 20] Guards: Use to describe event that causes a state transition happens (ALL transitions should have guards) [age <= 20]/setFlag(false) Action: If something happens while transitioning to another state. (Optional)

Quiz Review What does a swimlane diagram visually model? What does a sequence diagram model? What goes on the arrows in a sequence diagram? What are the three different types of arrows? What goes in a state for a state diagram? What can go on an arrow for a state diagram?

In-class exercises Let’s do a swimlane diagram for making a withdrawal at an ATM – the system should or should not be an actor? – see the use case we did earlier Let’s do a sequence diagram for making a withdrawal at an ATM What are some states for an ATM? – For the class CheckingAccount? – For the machine itself as viewed by a customer? – What are the triggers and transitions between theses states? Complete the exercise here: Due next class

Team Exercise Examine the Quiz Game description/use cases In your teams, come up with at least: – One swimlane diagram – One sequence diagram – One state diagram for a class – One state diagram for the system Turn in this assignment through svn