Introduction to UML Dr. Rajivkumar S. Mente

Similar documents
A Conceptual Model of the UML

INTRODUCING THE UML. Chapter 2

UNIT-II Introduction to UML

UNIT II. Syllabus. a. An Overview of the UML: Visualizing, Specifying, Constructing, Documenting

Basic Structural Modeling. Copyright Joey Paquet,

Introduction to UML. Danang Wahyu utomo

Allenhouse Institute of Technology (UPTU Code : 505) OOT Notes By Hammad Lari for B.Tech CSE V th Sem

Introduction to UML. (Unified Modeling Language)

Advanced Software Engineering

Modellistica Medica. Maria Grazia Pia, INFN Genova. Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico

Introduction to UML CHAPTER 1. Visualizing. Specifying LEARNING OBJECTIVES

CHAPTER 5 CO:-Sketch component diagram using basic notations 5.1 Component Diagram (4M) Sample Component Diagram 5.2 Deployment Diagram (8M)

Topics. Overview- The UML Functional Model. Structural Model. Behavioral Models. Use Case Diagram (essential and system)

Vidyalankar. T.Y. Diploma : Sem. VI [IF/CM] Object Oriented Modeling and Design Prelim Question Paper Solution

CHAPTER 5 ARCHITECTURAL DESIGN SE211 SOFTWARE DESIGN

OO Analysis and Design with UML 2 and UP

Lecture 17 Engineering Design Resolution: Generating and Evaluating Architectures

UNIT V *********************************************************************************************

UML Tutorial. Unified Modeling Language UML Tutorial

LABORATORY 1 REVISION

SOFTWARE DESIGN COSC 4353 / Dr. Raj Singh

IS 0020 Program Design and Software Tools

Introduction to Software Engineering. ECSE-321 Unit 9 Architectural Design Approaches

Software Engineering from a

Practical UML - A Hands-On Introduction for Developers

Object Oriented Design. Program Design. Analysis Phase. Part 2. Analysis Design Implementation. Functional Specification

Practical UML : A Hands-On Introduction for Developers

CHAPTER 1. Topic: UML Overview. CHAPTER 1: Topic 1. Topic: UML Overview

LECTURE NOTES ON OBJECT ORIENTED ANALYSIS AND DESIGN PATTERNS. III B. Tech II Semester (R-16) Ms. N Shalini. Assistant Professor

OBJECT ORIENTED ANALYSIS AND DESIGN

Software Design Methodologies and Testing. (Subject Code: ) (Class: BE Computer Engineering) 2012 Pattern

Class Diagram. Classes consist of. Note that class diagrams contain only classes, not objects.

Representing System Architecture

Dr.S.S.Riaz Ahamed Principal, Sathak Institute of Technology, Ramanathapuram,India.

UNIT-IV BASIC BEHAVIORAL MODELING-I

Architecture and the UML

Chapter 5: Structural Modeling

Lecture 17: (Architecture V)

Class Diagram. Classes consist of. Note that class diagrams contain only classes, not objects.

UNIT-4 Behavioral Diagrams

Object-Oriented Systems Analysis and Design Using UML

Interactions A link message

Lab Manual. Object Oriented Analysis And Design. TE(Computer) VI semester

Meltem Özturan

Vidyalankar. T.Y. Diploma : Sem. VI [IF/CM] Object Oriented Modeling and Design Prelim Question Paper

Unified Modeling Language

UNIT 5 - UML STATE DIAGRAMS AND MODELING

Lecture 16: (Architecture IV)

Introduction to UML p. 1 Introduction to the Object-Oriented Paradigm p. 1 What Is Visual Modeling? p. 6 Systems of Graphical Notation p.

Introducing the UML Eng. Mohammed T. Abo Alroos

Software Service Engineering

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION (Autonomous) (ISO/IEC Certified)

Ingegneria del Software Corso di Laurea in Informatica per il Management. Introduction to UML

A - 1. CS 494 Object-Oriented Analysis & Design. UML Class Models. Overview. Class Model Perspectives (cont d) Developing Class Models

Objectives. Explain the purpose and objectives of objectoriented. Develop design class diagrams

Object-Oriented Systems Development: Using the Unified Modeling Language

The Unified Modeling Language User Guide

DIGITAL NOTES ON OBJECT ORIENTED ANALYSIS AND DESIGN B.TECH III YEAR - II SEM ( )

What is a Class Diagram? A diagram that shows a set of classes, interfaces, and collaborations and their relationships

What is a Class Diagram? Class Diagram. Why do we need Class Diagram? Class - Notation. Class - Semantic 04/11/51

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION (Autonomous) (ISO/IEC Certified) MODEL ANSWER

SOFTWARE ENGINEERING UML FUNDAMENTALS. Saulius Ragaišis.

OBJECT ORIENTED DESIGN with the Unified Process. Use Case Realization

Pertemuan 8. Object Oriented Modeling and Design

Design of Embedded Systems

Object Oriented Modeling and Design

IDERA ER/Studio Software Architect Evaluation Guide. Version 16.5/2016+ Published February 2017

Enterprise Architect. User Guide Series. Maintenance. Author: Sparx Systems. Date: 30/06/2017. Version: 1.0 CREATED WITH

COSC 3351 Software Design. An Introduction to UML (I)

OBJECT ORIENTED DESIGN with the Unified Process. Use Case Realization

Introduction to Software Engineering. 5. Modeling Objects and Classes

Activity Nets: A UML profile for modeling workflow and business processes

S T R U C T U R A L M O D E L I N G ( M O D E L I N G A S Y S T E M ' S L O G I C A L S T R U C T U R E U S I N G C L A S S E S A N D C L A S S D I A

UML Unified Modeling Language

Chapter 10. Object-Oriented Analysis and Modeling Using the UML. McGraw-Hill/Irwin

Agenda. Why Model. Why Model? History of OO Modeling Methodologies Object Modeling Technique (OMT) Unified Modeling Language (UML)

Structured and Object Oriented Analysis and Design

UNIT-II I. BASIC STRUCTURAL MODELING

THE UNIFIED MODELING LANGUAGE

Use-Case Analysis. Architecture Oriented Analysis. R. Kuehl/J. Scott Hawker p. 1 R I T. Software Engineering

Metamodeling. Janos Sztipanovits ISIS, Vanderbilt University

SE Assignment III. 1. List and explain primitive symbols used for constructing DFDs. Illustrate the use of these symbols with the help of an example.

(C) 2010 Pearson Education, Inc. All rights reserved. Dr. Marenglen Biba

UML UNIFIED MODELLING LANGUAGE EXEMPLIFIED ON BLACKJACK. Object Oriented Programming (Samy Zafrany)

Enterprise Architect. User Guide Series. Maintenance

user.book Page 45 Friday, April 8, :05 AM Part 2 BASIC STRUCTURAL MODELING

OBJECT ORIENTED ANALYSIS AND DESIGN

Object-Oriented and Classical Software Engineering

Enterprise Architecture Views and Viewpoints in ArchiMate - Reference

Pattern for Structuring UML-Compatible Software Project Repositories

Enterprise Architect. User Guide Series. UML Models. Author: Sparx Systems. Date: 30/06/2017. Version: 1.0 CREATED WITH

Accessibility. EEC 521: Software Engineering. Classes and Objects. Inheritance. Classes and Objects (OO Analysis)

Unified Modeling Language (UML)

Chapter No. 2 Class modeling CO:-Sketch Class,object models using fundamental relationships Contents 2.1 Object and Class Concepts (12M) Objects,

Oral Questions. Unit-1 Concepts. Oral Question/Assignment/Gate Question with Answer

Chapter 3 Research Method

An Introduction To Object Modeling System Concept for Object Modeling The Overall View Components of UML Diagram

SEEM4570 System Design and Implementation. Lecture 10 UML

CSE 403: Software Engineering, Spring courses.cs.washington.edu/courses/cse403/15sp/ UML Class Diagrams. Emina Torlak

University of Calgary Department of Electrical and Computer Engineering. SENG : Object Oriented Analysis and Design Behrouz Homayoun Far

Transcription:

Introduction to UML Dr. Rajivkumar S. Mente Assistant Professor, Department of Computer Science, Solapur University, Solapur rajivmente@rediffmail.com

Introduction to UML UML is a language used for 1. Visualizing : UML is a bunch of graphical symbols Each symbol is a well-defined semantics One developer can write a model in the UML and another developer or tool can interpret that model

Continued.. UML is a language used for 2. Specifying : Means building models that are precise, unambiguous and complete Deal with the specification of analysis, design and implementations decisions

Continued.. UML is a language used for 3. Constructing : Possible to generate code from a UML model into programming language The reverse is also possible 4. Documenting the artifacts of software system Means that the UML deals with the documentation of a system s architecture and all of its details

Where can the UML be used? It has been used effectively for software intensive domains such as 1. Enterprise information systems 2. Banking and financial services 3. Telecommunications 4. Transportation 5. Defense / aerospace 6. Medical electronics 7. Distributed web-based services

Conceptual Model of the UML Requires three elements 1. The basic building blocks 2. The rules 3. Common mechanisms

The basic building blocks Three kinds of building blocks 1. Things 2. Relationships 3. Diagrams

Structural Things in UML Nouns Mostly static parts Represents elements either conceptual or physical

Structural Things in UML Seven kinds of structural things 1. Class 2. Interface 3. Collaboration 4. Use case 5. Active class 6. Component 7. node

A Class Description of a set of objects window origin size open() close() move() display()

An Interface Class Collection of operations that specify a service of a class Ispass A Collaboration Defines an interaction and provide some cooperative behavior Chain of Responsibility

A use Case Set of sequence of actions that a system performs Place order An active class A class whose objects own one or more processes EventManager eventid suspend () flush()

A Component Physical and replaceable part of the system orderform.java A node Physical elements that exists at run time server

Behavioral Things in UML Dynamic parts of the UML model Two kinds of behavioral things are 1. An interaction behavior 2. A state machine

Interaction behavior Consists of a set of messages exchanged among a set of objects. State Machine Specifies the sequences of states an object goes through during its lifetime. Waiting

Grouping Things in UML Organizational parts of UML models Package is one kind of grouping things Package is used for organizing elements into groups Structural things, behavioral things and other things may be placed in a package A package is a conceptual thing i.e. it exists only at development time.

A package is graphically rendered as a tabbed folder including its name and contents Business rules

Annotational Things in UML Comments applied to describe, illuminate and remark about any element in a model. Graphically a note is rendered as a rectangle with dog-eared corner together with a textual or graphical comment Return copy of self

Relationships in UML Four types of relationships in the UML 1. Dependency 2. Association 3. Generalization 4. Realization

Continued..Relationships in UML Dependency : A semantic relationship between two things Change to one thing may affect the semantics of the other thing Graphically a dependency is shown as dashed line possibly directed and with label

Continued..Relationships in UML Association : Describes a set of links connected among objects Graphically shown as solid line possibly with label and with multiplicity and role names

Continued..Relationships in UML Generalization : Is a specialization / generalization relationship Objects of the specialized element ( the child) are substitutable for the generalized element (the parent) Graphically shown as solid line with a hollow arrow head pointing to the parent

Diagrams in the UML A diagram is the graphical representation of a set of elements rendered as a connected graph of vertices (things) and arcs (relationships) The same element may appear inall diagrams UML includes nine kinds of diagrams 1. Class diagram : Shows a set of classes, interfaces and collaborations and their relationships

Continued..Diagrams in the UML 2. An object diagram : Shows a set of objects and their relationships. 3. A use case diagram : Shows a set of use cases and actors (a special kind of class) and their relationships. 4. Sequence diagram : Is an interaction diagram that highlight the time ordering of messages. 5. Collaboration diagram : Is an interaction diagram that emphasizes the structural organization of the objects that send and receive messages.

Continued..Diagrams in the UML 6. Statechart diagram : Shows a state machine consisting of states, transitions, events and activities. 7. An activity diagram : Is a special kind of statechart diagram that shows the flow from activity to activity within a system 8. Component diagram : Shows the organizations and dependencies among a set of components. 9. Deployment diagram : Shows the configuration of run-time processing nodes and the components that live on them

Common Mechanisms in the UML Four common mechanisms 1. Specifications 2. Adornments 3. Common divisions 4. Extensibility mechanisms

Continued. Common Mechanisms in the UML Specifications : Behind every part of graphical notation there is a specification. This provides a textual statement of the syntax and semantics of that building block.

Continued. Common Mechanisms in the UML Adornments : Variety of adornments can be added to every symbol. e.g. figure shows a class adorned to indicate that it is an abstract class with two public, one protected and one private operation Transaction + execute() + rollback() # priority() - timestamp()

Continued. Common Mechanisms in the UML Common Divisions : There is the division of class and object In UML you can model class as well as objects. e.g. Customer Jan : Customer name address Phone : Customer Elyse Fig. : class objects

Continued. Common Mechanisms in the UML (Common Divisions) Common Divisions : There is separation of interface and implementation Both interfaces and their implementations can be modeled. IsUnknown Spellingwizard.dll IsSpelling Here spellingwizard.dll implements two interfaces IsUnknown and IsSpelling

Continued. Common Mechanisms in the UML Extensibility Mechanisms: UML is open ended Therefore possible to extend the language in controlled ways The extensibility mechanisms include 1.Stereotypes 2.Tagged values 3.Constraints

Continued. Common Mechanisms in the UML (Extensibility Mechanisms) Stereotypes : Allows to create new kinds of building blocks by extending the vocabulary. e.g. the exception class overflow in C++ is shown as << exception >> overflow Tagged Values : Extends the properties of a UML building block allowing to create new information in that element s specification

Continued. Common Mechanisms in the UML (Extensibility Mechanisms) Tagged Values : Extends the properties of a UML building block allowing to create new information in that element s specification EventQueue {version = 1.2 author = xyz} add() remove() flush()

Continued. Common Mechanisms in the UML (Extensibility Mechanisms) Constraints: Allows to extend the semantics of a UML building block by adding new rules or modify existing ones. e.g. EventQueue add() remove() flush() ordered Here {ordered} constraint on operation add specifies that all additions are done in order.