UML (Sequence Diagrams, Collaboration and State Chart Diagrams) Presentation By - SANDEEP REDDY CHEEDEPUDI (Student No: 17037032) - VISHNU CHANDRADAS (Student.

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

UML an overview.
UML Diagrams Jung Woo. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems, business.
© 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.
Systems Analysis and Design 8th Edition
Chapter 22 Object-Oriented Systems Analysis and Design and UML Systems Analysis and Design Kendall and Kendall Fifth Edition.
Department of Computing
2-1 © Prentice Hall, 2007 Chapter 2: Introduction to Object Orientation Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph.
Systems Analysis and Design in a Changing World, Fourth Edition
Essentials of interaction diagrams Lecture 23 & 24.
Essentials of interaction diagrams Lecture Outline Collaborations Interaction on collaboration diagrams Sequence diagrams Messages from an object.
C++ Training Datascope Lawrence D’Antonio Lecture 11 UML.
© 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.
UML. Overview of UML Diagrams Structural : element of spec. irrespective of time Class Component Deployment Object Composite structure Package Behavioral.
Unified Modeling Language
UML Sequence Diagrams Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
UML Diagrams Computer Science I.
CS3773 Software Engineering
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.
Prepared by Afra`a Sayah. Introduction. Weekly Tasks. Plane Phase. Analysis Phase. Design Phase. Report Rules. Conclusion. 2.
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.
Programming in Java Unit 3. Learning outcome:  LO2:Be able to design Java solutions  LO3:Be able to implement Java solutions Assessment criteria: 
Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.
Systems Analysis & Design 7 th Edition Chapter 5.
Programming Logic and Design Fourth Edition, Comprehensive Chapter 15 System Modeling with the UML.
Systems Analysis and Design 8 th Edition Chapter 6 Object Modeling.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
ניתוח מערכות מידע 1 Unified Modeling Language (UML) § § The Unified Modeling Language (UML) is the industry-standard language for: Specifying, Visualizing,
Sequence diagram in UML Martin Palkovik. Sequence diagram  It is a graphic representation of system operations based on chronology - a time sequence.
An Introduction to the Unified Modeling Language
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
1 An Introduction to UML Interaction (Sequence and Communication) Diagrams Georgia State University CIS 3300 Spring, 2009.
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
Design Jon Walker. More UML ● What is UML again?
UML Diagrams CSC 422 Kutztown University Dr. Daniel Spiegel.
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.
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.
©2007 · Georges Merx and Ronald J. NormanSlide 1 Chapter 15 The Unified Modeling Language: a Primer.
 Building Block Building Block  Things in the UML Things in the UML  Structural Things Structural Things  Behavioral Things Behavioral Things  Grouping.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
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
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Unified Modeling Language. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems,
UML (Unified Modeling Language)
Systems Analysis and Design in a Changing World, Fourth Edition
Appendix 3 Object-Oriented Analysis and Design
UML(Unified Modeling Language)
UML Diagrams By Daniel Damaris Novarianto S..
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Object-Oriented Analysis and Design
Unified Modeling Language
UML Diagrams Jung Woo.
Business System Development
UML: Unified modeling language
UML dynamic Modeling (Behavior Diagram)
Chapter 20 Object-Oriented Analysis and Design
CIS 375 Bruce R. Maxim UM-Dearborn
Appendix A Object-Oriented Analysis and Design
Chapter 5.
CIS 375 Bruce R. Maxim UM-Dearborn
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Appendix 3 Object-Oriented Analysis and Design
Presentation transcript:

UML (Sequence Diagrams, Collaboration and State Chart Diagrams) Presentation By - SANDEEP REDDY CHEEDEPUDI (Student No: ) - VISHNU CHANDRADAS (Student No: ) - MADHU VARMA CHEKURI (Student No: ) - PRAVEEN KUMAR EULUKA (Student No: )

Introduction: UML is a standardized visual specification language for object modeling. Is a general-purpose modeling language that includes a graphical notation. Is used to create an abstract model of a system, referred to as a UML model. UML is used for systems engineering modeling, business process modeling, and representing organizational structures. The available version now is UML 2.0.

Diagrams of UML UML has thirteen types of diagrams divided into three categories. The three categories are Structure Diagrams Behavior Diagrams Interaction Diagrams

Structure Diagrams A type of diagram that depicts the elements of a specification that are irrespective of time. These include…… Class Diagrams: Shows the classes of the system, the operations and attributes of the classes, and their interrelationships (including inheritance, aggregation, and association). Object Diagrams: Looks similar to that of a class diagram. These are also referred as instance diagrams. Component Diagrams: Used to represent the different high-level reusable parts of a system. Also captures the inter-relationships between these parts.

Composite Structure Diagrams: Same as that of a class diagram. The difference is it depicts individual parts instead of whole classes. Package Diagrams: The grouping of objects into sets of objects that provide related services are called package diagrams. Grouping makes the UML diagrams simpler and easier to understand. Deployment Diagrams: Least understood and more important of the diagrams of UML. There are four elements used in Deployment diagrams. They are nodes, components, dependencies, and links.

Behavior Diagrams: A type of diagram that depicts behavioral features of a system or business process. These include…… Use case Diagrams: Used during the analysis phase of a project and are helpful in designing and understanding the project. Depict the relationship between the users and the actors. Activity diagrams: Shows the flow of activities through the system. Look like a tree consisting of branches. State Machine diagrams: objects which have both behaviour and state are called state machine diagrams. Shows interesting behaviour about one particular object.

Interaction diagrams: Interaction diagrams are a subset of behavior diagrams which emphasize object interactions. These include…… Communication Diagrams: Show the message flow between the objects and the relationships between the classes. Used to explore the dynamic behavior of the systems. Interaction Overview Diagrams: Notation is same as that of an activity diagram in most of the cases. These diagrams introduce two new elements. They are interaction occurrences and interaction elements. Timing Diagram: The focus will be on timing constraints i.e., in a given period of time, these diagrams are used to explain more about the behavior of one or more objects. Often used in designing embedded software such as fuel injection system in automobiles.

Sequence Diagram A sequence diagram is a visual representation of how objects in a system interact. Used to represent or model the flow of messages. Sequence diagrams describe interactions among classes in terms of an exchange of messages over time. A Sequence diagram is two-dimensional in nature. A sequence diagram has four key elements. 1.Object appears along the top margin. 2.Each object has a life line; dashed line represents the life and perhaps the death of the object. 3.A focus of control is tall, thin rectangle that sits on the top of an object's lifeline. The rectangle shows the period of the time during which the given object is the control of the flow-for instance, when the object is creating another object. 4.Message shows the action that object performs on each other and on themselves.

Symbols used in Sequence Diagrams: Class roles: The way an object will behave in the diagram is described by class roles. Activation: Activation boxes represent the time an object needs to complete a task. Messages: Simple Messages are arrows that represent Synchronous communication between objects. Asynchronous Lifelines: These are the vertical dashed lines that indicate the object's presence over time. Destroying Objects: Using an arrow labeled " >" that points to an X the objects can be terminated early Loops: A repetition or loop within a sequence diagram is depicted as a rectangle. Object: Class

Example of a Sequence Diagram: Customer

Collaboration Diagram: Collaboration diagrams illustrate the relationship and interaction between software objects, and the sequence of messages exchanged between the objects during the interaction. Each system operation initiates a collaboration diagram. Therefore, there is a collaboration diagram for every system operation. This makes it easier to show how the objects are linked together, but harder to see the sequence at a glance. Symbols used in collaboration diagrams Class roles : Class roles describe how objects behave. Association roles : Association roles describe how an association will behave given a particular situation. Messages: Sequence numbering can become nested using the Dewey decimal system.

Example of collaboration Diagram:

State Chart Diagrams: State chart diagrams are used for describing the behavior of classes, use cases, actors, subsystems, methods or operations. The state chart diagrams are used to show the life cycle of a class. This diagram models the dynamic flow of control from state to state within a system. How to draw a State chart Diagram? Drawing a state chart diagram is straightforward and also easy. We need to identify the following things to draw a state chart diagram. 1.Identify the initial and final states. 2.Identify the transitions leaving a state. 3.Identify potential sub states. 4.Identify a target state to which the transition leads.

Elements of state chart diagrams: Initial State: This shows the starting point of the state chart diagram that is where the activity starts. State: A state represents a condition of a modeled entity for which some action is performed. The state is indicated by using a rectangle with rounded corners and contains compartments. Transition: It is indicated by an arrow. Transition is a relationship between two states which indicates that Event/ Action an object in the first state will enter the second state and performs certain specified actions. Final State: The end of the state chart diagram is represented by a solid circle surrounded by a circle.

Example of a state chart diagram:

Queries ….. ?