CIM LAB MEETING Presentation on UML 03-07-02 Rakesh Mopidevi Kwangyeol Ryu.

Slides:



Advertisements
Similar presentations
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Advertisements

UML Diagrams Jung Woo. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems, business.
Unified Modeling Language
Object-Oriented Analysis and Design
Introduction To System Analysis and Design
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
7 July 2003 MDA presentation Dennis Wagelaar 1 Model-Driven Architecture The current state of affairs.
COST G9 - Work group 2 Cadastral science meeting Aalborg, Dk Modeling methodology for real estate transactions Radoš Šumrada Faculty.
Rational Worldwide Software Symposium
© Copyright Eliyahu Brutman Programming Techniques Course.
Lab 6 CPIT 250 System Analysis and Design.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Chapter 7: The Object-Oriented Approach to Requirements
1 Introduction to UML DIAGRAMS & CLASS DIAGRAM Chapter 7,8 主講人 : 許勝杰
Metadata Tools and Methods Chris Nelson Metanet Conference 2 April 2001.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
PowerDesigner 与对象建模. 2 Why Using UML? Visually define and communicate the structure and behavior of an application Represent systems using Object-Oriented.
Introduction to MDA (Model Driven Architecture) CYT.
METACASE. WHAT THIS PRESENTATION IS ABOUT  What’s META MODELING?  What’s METACASE?  METAEDIT+ 5.1 EVALUTION PROGRAM  Diagram and its kinds.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
Modeling Component-based Software Systems with UML 2.0 George T. Edwards Jaiganesh Balasubramanian Arvind S. Krishna Vanderbilt University Nashville, TN.
ניתוח מערכות מידע 1 Unified Modeling Language (UML) § § The Unified Modeling Language (UML) is the industry-standard language for: Specifying, Visualizing,
By: DiGitAll UML an overview. Topics covered in this Session 1. Introducing UML. 2. What constitutes the UML. 3. Concepts of UML.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
1 Introduction to UML. 2 What is UML? UML is an acronym for Unified Modeling Language. Unified –Combines the best from existing object- oriented software.
TAL7011 – Lecture 4 UML for Architecture Modeling.
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
Michael Schloh von Bennewitz 1. Oktober 2002 The Unified Modeling Language Overview of theory and practice of the OMG Unified Modeling.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.
Software Engineering Lecture 8 Object-Oriented Analysis.
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.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
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.
MADALINA CROITORU Software Engineering week 4 Practical Madalina Croitoru IUT Montpellier.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Prof. Hany H. Ammar, CSEE, WVU, and
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
1 Architectural Blueprints—The “4+1” View Model of Software Architecture (
Diagrams. Typically, we view the static parts of a system using one of the four following diagrams. 1. Class diagram 2. Object diagram 3. Component diagram.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
CS 501: Software Engineering Fall 1999 Lecture 15 Object-Oriented Design I.
Introduction to UML and Rational Rose UML - Unified Modeling Language Rational Rose 98 - a GUI tool to systematically develop software through the following.
Object Oriented Analysis & Design By Rashid Mahmood.
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.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
UML (Unified Modeling Language)
UML AN OVERVIEW. Topics covered in this Session 1. Introducing UML. 2. What constitutes the UML. 3. Concepts of UML.
Instructor: Dr. Hany H. Ammar
UML Diagrams By Daniel Damaris Novarianto S..
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Unified Modeling Language
Introduction to Unified Modeling Language (UML)
UML Diagrams Jung Woo.
Rational Worldwide Software Symposium
Unified Modeling Language
Introduction to UML.
Evaluating Compuware OptimalJ as an MDA tool
Rational Worldwide Software Symposium
Visual Modeling Using Rational Rose
Rational Worldwide Software Symposium
PASSI (Process for Agent Societies Specification and Implementation)
Uml diagrams In ooad.
Presentation transcript:

CIM LAB MEETING Presentation on UML Rakesh Mopidevi Kwangyeol Ryu

Overview Static and Dynamic diagrams of UML with the example of a simple scenario Why UML

Use Case Diagram Graphical view of some or all to the actors, use cases, and their interactions identified for a system Address static use case view of system Especially important in organizing and modeling the behaviors of the system

Use Case sequence of transactions performed by a system that yields a measurable result of values for a particular actor A use case describes what a system does but it does not specify how it does it

Example Assembly sends order to the supplier

Use case diagram

Flow of Events Description of events needed to accomplish the required behavior of the use case Written in terms of what the system should do, not how the system does it It is written in the language of domain, not in terms of implementation

Flow of Events Flow of events for Place Order use case Main flow: This use case begins when the Assembly sends an order to the supplier and ends when the supply reaches the assembly. Interactions: The order status use case has a bidirectional association relation with the Assembly actor and Supplier actor. Data Needed: The use case needs all the data related to the order dates and quantity. Normal flow of events: If the required quantity as per the order is available at the supplier then order is passed to it and the order status is kept track of. Alternate Flow: If the required quantity as per the order is not available at the supplier then order is sent back.

CLASS DIAGRAMS Show a set of classes and their relationships Most common diagram found in modeling object-oriented systems Address the static design view of a system

Class Diagram I

Interaction Diagrams Shows an interaction, consisting of a set of objects and their relationships, including the messages that may be dispatched among them Address dynamic view of system Sequence and collaboration diagrams are kinds of interaction diagrams

Interaction diagrams Sequence diagram is an interaction diagram that emphasizes the time- ordering of messages Collaboration diagram emphasizes the structural organization of the objects that send and receive messages These two diagrams are isomorphic

Sequence diagram

Collaboration diagram

Activity Diagram Shows the flow from activity to activity within a system Address the dynamic view of the system Important in modeling the function of a system and emphasize the flow of control among objects

Activity diagram

WHY UML ?

UML Features Enable the modeling of systems (and not just software) using Object-Oriented Concepts Semantics come from Booch, OMT (Object Modeling Technique), OOSE (Object-Oriented Software Engineering) Support package concept  refine model iteratively Unify the Perspectives among many different kinds of systems (business versus software), development phases (requirements analysis, design, and implementation), and internal concepts  manage models with one file Structural diagrams: class, object, component, deployment diagram Behavior diagrams: use case, sequence, activity, collaboration, statechart diagram Model management diagrams: package, subsystem, and models

UML Features (cont’d) Automatic (skeleton) Source Code Generation Supporting language: C/C++/C#, VB, Java, Ada, etc. Supporting middleware: CORBA XML_DTD Generate tools for Reverse Engineering Code  UML model Web pages with ASP/JSP  UML model Use the OCL (Object Constraint Language) Describe additional constraints about the objects in the model

UML Features (cont’d) Support MDA (Model Driven Architecture) Address the complete life cycle of designing, deploying, integrating, and managing applications as well as data using open standards Provide an open, vendor-neutral approach to the challenge of interoperability UML TM, XMI TM /XML, CORBA TM MOF : Meta Object Facility CWM : Common Warehouse Metamodel