Introduction to Unified Modeling Language (UML) - INSPIRATION

INSPIRATION – Spatial Data Infrastructure in the Western Balkans 

Introduction to Unified Modeling 

Language (UML) 

3rd INSPIRATION Training 

December 4-5, 2012 

A multi-country project funded by the 

European Union and implemented by

Content 

• Basic introduction 

• Models 

• UML 

• Diagrams 

• Exercises & Examples 

• Class diagram

Scope 

• Basic knowledge of UML 

Introduction 

of modelling 

and UML 

Class model 

introduction 

& Exercises 

INSPIRE Data 

Specification 

on Cadastre

UML Background 

What are models?


What are models? 

• A complete description of a system from a 

particular perspective 

• Simplification of reality

Why models? 

• Modeling achieves four aims: 

• Helps you to visualize a system as you want it to be. 

• Permits you to specify the structure or behavior of a 

system. 

• Gives you a template that guides you in constructing a 

system. 

• Documents the decisions you have made. 

• You build models of complex systems because you 

cannot comprehend such a system in its entirety. 

• You build models to better understand the system 

you are developing.

Four Principles of Modeling 

• The model you choose influences how the 

problem is attacked. 

Process Model 

Deployment Model 

Design Model 

• Every model may be expressed at different levels 

of precision. 

• The best models are connected to reality. 

• No single model is sufficient.


What is UML? 

The OMG specification states: 

? 

"The Unified Modeling Language (UML) is a graphical 

language for visualizing, specifying, constructing, and 

documenting the artifacts of a software-intensive system. 

The UML offers a standard way to write a system's 

blueprints, including conceptual things such as business 

processes and system functions as well as concrete things 

such as programming language statements, database 

schemas, and reusable software components."


What is UML? 

• UML is a language (Unified Modeling 

Language) for models 

• technical and graphical specification 

• Graphic notation to visualize models 

• Not a method or procedure 

• Managed and created by the Object 

Management Group


• The UML is a language for 

• Visualizing 

• Specifying 

• Constructing 

• Documenting 

the artifacts of a software-intensive system. 

• The Unified Modelling Language (UML) is an 

industry standard for object oriented design 

notation, supported by the Object Management 

Group (OMG).

Language for Visualizing 

• Communicating conceptual models 

to others is prone to error unless 

everyone involved speaks the same 

language. 

• There are things about a software 

system you can’t understand unless 

you build models. 

• An explicit model facilitates communication.

Language for Specifying 

• The UML builds models that are precise, 

unambiguous, and complete.

Language for Constructing 

• UML models can be directly connected to a 

variety of programming languages. 

• Maps to Java, C++, Visual Basic, and so on 

• Tables in a RDBMS or persistent store in an 

OODBMS 

• Permits forward engineering 

• Permits reverse engineering

Æ¯Á¤¹®¼¿¡ ´ëÇÑ º¸±â¸¦ 

»ç¿ëÀÚ°¡ ¿äÃ»ÇÑ´Ù. 

ÈÀÏ°ü¸®ÀÚ´Â ÀÐ¾î¿Â 

¹®¼ÀÇ Á¤º¸¸¦ ÇØ´ç ¹®¼ 

°´Ã¼¿¡ ¼³Á¤À» ¿äÃ»ÇÑ´Ù. 

È¸é °´Ã¼´Â ÀÐ¾îµéÀÎ 

°´Ã¼µé¿¡ ´ëÇØ ÀÌ¸§º°·Î 

Á¤·ÄÀ» ½ÃÄÑ È¸é¿¡ 

º¸¿©ÁØ´Ù. 

1: Doc view request ( ) 

9: sortByName ( ) 

2: fetchDoc( ) 

3: create ( ) 

6: fillDocument ( ) 

4: create ( ) 

8: fillFile ( ) 

5: readDoc ( ) 

7: readFile ( ) 

ºÐ»ê È¯°æÀÇ ÇÏµå¿þ¾î¹× ³×Æ®¿÷À¸·ÎÀÇ Á¤º¸ ½Ã½ºÅÛ ¿¬°á ¸ðµ¨ 

- À©µµ¿ì 95 : Å¬óÀÌ¾ðÆ® 

- À©µµ¿ì NT: ÀÀ¿ë¼¹ö 

- À¯´Ð½º ¸Ó½Å: ÀÀ¿ë ¼¹ö ¹× µ¥ÀÌÅ¸ ¼¹ö, Åë½Å ¼¹ö 

- IBM ¸ÞÀÎÇÁ·¹ÀÓ: µ¥ÀÌÅ¸ ¼¹ö, Åë½Å ¼¹ö 

Window95 

¹®¼°ü¸® 

Å¬óÀÌ¾ðÆ®.EXE 

FileMgr 

fetchDoc( ) 

Repository 

(from Persistence) 

rep 

name : char * = 0 

readDoc( ) 

readFile( ) 

Windows 

NT 

sortByName( ) 

Windows 

NT 

¹®¼°ü¸® ¿£Áø.EXE 

FileList 

add( ) 

delete( ) 

read( ) 

File 

Windows95 

DocumentList 

add( ) 

IBM 

Mainframe 

µ¥ÀÌÅ¸º£ÀÌ½º¼¹ö 

delete( ) 

1 

fList 

Solaris 

ÀÀ¿ë¼¹ö.EXE 

GrpFile 

read( ) 

open( ) 

create( ) 

fillFile( ) 

get( ) 

name : int 

docid : int 

open( ) 

close( ) 

read( ) 

Document 

numField : int 

sortFileList( ) 

create( ) 

Windows95 

¹®¼°ü¸® ¾ÖÇÃ¸´ 

fillDocument( ) 

Alpha 

UNIX 

code.. 

read() fill the 

Language for Documenting 

• The UML addresses documentation of system architecture, 

requirements, tests, project planning, and release management. 

Use Case Diagram 

Deployment Diagram 

Use Case 1 

Actor A 

Use Case 2 

Actor B 

Use Case 3 

user 

mainWnd fileMgr : 

FileMgr 

document : 

Document 

gFile 

repository 

Sequence Diagram 

Class Diagram

History of the UML

Diagrams 

• Diagrams graphically depict a view of a part of your 

model. 

• Different diagrams represent different views of the 

system that you are developing. 

• A model element will appear on one or more diagrams.

UML Diagrams 

• UML 2.2 

• 14 different types of diagrams 

• 2 different groups 

• Behavior & Interaction models 

• Structural models

UML Diagrams

Key Diagrams in UML 

Requirements 

Use Case Diagrams 

System Structure 

System Behaviour 

Class Diagrams 

Collaboration Diagrams 

Interaction Diagrams 

Activity Diagrams 

State Charts

Different diagrams of system 

for different people 

Logical View 

Implementation View 

Analysts/Designers 

Structure 

Use-Case View 

End-user 

Functionality 

Programmers 

Software management 

Process View 

Deployment View 

System integrators 

Performance, scalability, throughput 

System engineering 

System topology, delivery, 

installation, communication

What is a Use-Case Model? 

A use-case model: 

• Is a model of a system’s intended functions and its 

environment 

• Serves as a contract between the customer and the 

developers 

• Contains the following diagrams: 

• Use case: Shows a set of use cases and actors and their 

relationships 

• Activity: Shows the flow of events within a use case 

• Sequence: Shows how a use case will be implemented in terms of 

collaborating objects

Use-Case Diagram 

View Report Card 

Student 

Register for Courses 

Login 

Course Catalog 

Registrar 

Maintain Professor 

Information 

Maintain Student 

Information 

Professor 

Select Courses to 

Teach 

Submit Grades 

Close Registration 

Billing System

Activity Diagram 

Action 

A step in the flow of events 

Decision 

Flows split based on a guard 

condition 

Fork 

Beginning of concurrent flows 

Join 

End of concurrent flow 

Flow 

Show the sequence of 

activities

Activity Diagram (Example) 

Concurrent 

Threads 

Guard 

Condition 

Check 

Schedule 

Select Course 

[ add course ] 

[ delete course ] 

Check 

Pre-requisites 

[ checks completed ] [ checks failed ] 

Decision 

Delete Course 

Activity/Action 

Synchronization 

Bar (Fork) 

Synchronization 

Bar (Join) 

Assign to 

Course 

Resolve 

Conflicts 

Transition 

Update 

Schedule

What is a Design Model? 

A design model: 

• Describes the realization of use cases in terms of design 

elements 

• Describes the design of the application 

• Contains the following diagrams: 

• Class: Shows UML classes and relationships 

• Component: Shows the structure of elements in the 

implementation model 

• Communication and Sequence: Show how objects and classes 

interact 

• State Machine: Shows event-driven behavior

Class Diagram 

• Class diagrams show the static structure of the 

model resp. system 

• Classes 

• Attributes 

• Relationships to other classes 

• Class diagrams do not show temporal 

information 

• INSPIRE data specifications

Class Diagram 

Class 

A description of a set 

of objects 

Attribute 

Named property of 

a class 

Operation 

Class behavior 

Generalization 

Shows an inheritance 

relationship 

Aggregation 

Represents a part-whole 

relationship


• used to show how objects interact to 

perform the behavior of all or part of a use 

case as part of a use-case realization


Object/Class 

Shows the 

object/class involved 

in the interaction 

Messages 

Show data exchanged 

between objects 

Execution Occurrence 

Shows object executing 

Lifeline 

Shows the life of the object


(Example) 

:RegisterForCoursesForm :RegistrationController SWTSU Catalog : 

CourseCatalogSystem 

: Student : Course Catalog 

1: create schedule( ) 

2: get course offerings( ) 

3: get course offerings(for Semester) 

5: display course offerings( ) 


6: display blank schedule( ) 

ref 

Select Offerings


Combined Fragments 

Interaction Use (ref) 

References another interaction 

Optional Fragment 

(opt) 

Executed if guard condition 

evaluates to true 

Loop (loop) 

Executed as long as the first 

guard condition 

evaluates to true

Communication Diagram 

• Collaboration diagram 

• provide another way to show how objects 

interact to perform the behavior of a 

particular use case or a part of a use case. 

Where sequence diagrams emphasize the 

interactions of objects over time, 

communication diagrams are designed to 

emphasize the relationships between objects


Object/Class 

Shows the 

object/class involved 

in the interaction 

Message 

Shows data 

exchanged 

between objects


Messages 

5: display course offerings( ) 

6: display blank schedule( ) 

1: create schedule( ) 

: RegisterForCoursesForm 

Links 

: Course Catalog 

: Student 



3: get course offerings(forSemester) 

: RegistrationController : CourseCatalogSystem

Component Diagram 

• It shows the runtime structure of the 

system at the level of software 

components. Components are the modular 

parts of the system and are made up of 

groups of related objects that are hidden 

behind an external interface.

Component Diagram 

Component 

Modular parts of the system 

Class 

Included to show implementation 

relationships.


• Deployment diagrams show the 

deployment architecture of the system, 

that is, which of the system’s software 

artifacts reside on which pieces of 

hardware.


Artifact 

Represents a physical file 

Owned Element 

Relationship 

Shows another way of 

showing nested elements 

Node 

Represents a 

physical machine

How Many Diagrams? 

• Depends: 

• You use diagrams to visualize the system from different 

perspectives. 

• No complex system can be understood in its entirety from one 

perspective. 

• Diagrams are used for communication 

• Model elements will appear on one or more 

diagrams. 

• For example, a class may appear on one or more class diagrams, be 

represented in a state machine diagram, and have instances appear 

on a sequence diagram. 

• Each diagram will provide a different perspective.

UML – Exercise

UML – Exercise 

• Class diagram 

• INSPIRE Data 

Specifications 

• Foundation for 

other structure 

diagrams 

• Classification of 

reality

UML Exercise 

• The class diagram 

• Class (and objects) 

• Relationship 

• Package (advanced) 

• Interfaces (advanced)


• The class 

• Summarize a number of objects with the same 

behavior and semantics 

• Abstraction of entities 

• Semantic concept with common attributes and 

operations


• The class 

• Abstraction of entities 

class Tree 

«FeatureClass» 

Tree 

- TreeAge :int 

- TreeType :char


• The class 

Class name 

Class attributes 

Class operations


• The class attribute 

Attribute name 

Data type 

E.g.: 

-Integer 

- LongInt 

- Double 

- Char 

- Date 

- Boolean 

- String 

- Geometry 

- …


• The class operations 

Attribute name 

Expected operation input 

Data type


• Exercise #1 – The Class 

• Please develop/draw the class “Cadastral_Parcel” 

• What common characteristics (attribute: datatype) 

should the concept “Cadastral_Parcel” have? 

class Exercise #1 

«featureType» 

CadastralParcel 

?

Group 1 

• Class: Parcel 

• Attributes: 

• Object no. 

• Number 

• Cadastral municipality 

• Land use 

• Number of building 

• Address 

• Area 

• Owner

Group 2 

• The same as g1, just no address



• Multiple solutions possible 




- Address :char 

- APN :char 

- Boundary :GM_Surface 

- Centroid :GM_Point



• INSPIRE Data Specifications on Cadastral 

• Geometry 

• Label 

• National cadastral reference 

• Area value (optional) 

• Reference Point (optional)


• Relations 

Relation?


• Relations 

• Associations 

• Generalisations 

• Aggregations 

• Compositions



• Implies that two classes have a relationship 

• General relationship connector 

• Target/Source roles 

• Cardinality 

• Directions 

• Constrains



class Tree 

«FeatureType» 

Tree 

+cutted by 

+cuts 

«FeatureTyp... 

Woodcutter 


- TreeType :char 

1..* 

1..* 

- Gender :char 

- Name :char



• Indicated inheritance 

• Target/Source roles (e.g. isPartOf) 

• Cardinality 

• Constrains 

• Source inherits targets characteristic



class Tree 


Tree 



+cutted by 

1..* 

+cuts 

1..* 


Woodcutter 

- LicenceNumber :int 

Woodcutter inherits 

attributes from Person 


Person 


- Name :char


• Aggregations & Compositions 

• Indicates that the lower concept is part of a higher 

concept 

• Aggregation: Lower concept ISN’T necessary for 

existence of higher concept 

• Composition: Lower concept IS necessary for existence 

of higher concept


• Aggregations & Compositions 

Compositio 

n 

class Tree 

Aggregation 


Forest 


Employees 

+consistsOf 1..* 

+has 0..* 

+isPartof 

+isPartOf 


Tree 

+cutted by 

+cuts 


Woodcutter 


Person 



1..* 

1..* 

- LicenceNumber :int 


- Name :char


• Exercise #2 – The relationship types 

• Imagine you have 3 different classes 

• CadastralParcel 

• Core class 

• Is part of several(!) administrative zones (different levels of 

hierarchy) 

• CadastralBoundary 

• Indicates measured boundary of CadastralParcel 

• AdministrativeZone 

• Administrative zones with different hierarchal levels which 

existence doesn’t depend on CadastralParcel 

• Please develop diagram using relationship types and 

classes with (some) attributes!

Exercise 2 

Administrative 

Zone 

Cadastral 

Boundary 

Cadastral Parcel



• Again there are multiple solutions 


- Label :char 

- ... :... 


CadastralZone 

? 




- ParcelNumber :char 

- ... :... 


CadastralBoundary 

- Geometry :GM_curve 

- ... :...



• There are multiple solutions 

• One example: 



CadastralBoundary 

+is border 

+hasBorder 



+isPartof 

+Contains 


Administrativ eZone 

- Geometry :GM_curve 

- ... :... 

1..2 

1..* 


- ParcelNumber :char 

- ... :... 

1..* 

0..* 

- Label :char 

- Geometry :GM_surface 

- ... :...

INSPIRE Cadastre 

• INSPIRE Data specifications on cadastral 

• http://inspire.jrc.ec.europa.eu/

References 

• OMG - UML 

• http://www.uml.org/ 

• Sparx Systems 

• http://www.sparxsystems.com/resources/uml2_t 

utorial/index.html 

• Learners support publication 

• http://www.lsp4you.com/seminar.htm

Contact & Information 

Christian Ansorge 

+43-(0)1-313 04/3160 

christian.ansorge@umweltbundesamt.at 

Ivica Skender 

+385-(0)91-33667-120 

ivica.skender@gdi.net 

Bečići ■ December 5, 2012 

69

Introduction to Unified Modeling Language (UML) - INSPIRATION

Create successful ePaper yourself

Delete template?

Save as template?