Presentation is loading. Please wait.

Presentation is loading. Please wait.

Training: INSPIRE Basics EC JRC 1/15 UML class diagram: example INSPIRE UML class diagram for administrative units.

Similar presentations


Presentation on theme: "Training: INSPIRE Basics EC JRC 1/15 UML class diagram: example INSPIRE UML class diagram for administrative units."— Presentation transcript:

1 Training: INSPIRE Basics EC JRC 1/15 UML class diagram: example INSPIRE UML class diagram for administrative units

2 Training: INSPIRE Basics EC JRC 2/15 UML (Unified Modeling Language)

3 Training: INSPIRE Basics EC JRC 3/15 Class Definition: description of a set of objects that share the same attributes, operations, relationships, and semantics. Objects are also called «instances» of the class

4 Training: INSPIRE Basics EC JRC 4/15 Class Car + seatNumber : Integer + colour : Colour [1..*] visibility class name (convention: UpperCamelCase) attribute name (convention: lowerCamelCase) attribute type multiplicity – [min..max] (default: exactly 1) « A car is characterised by a seat number and one or several colors. »

5 Training: INSPIRE Basics EC JRC 5/15 Inheritage / generalisation Definition: taxonomic relationship between a more general element and a more specific element. Representation: ClassA ClassB « A ClassB instance is also a ClassA instance » « ClassB instances share the same characteristics as Class A instances » « ClassB specialises ClassA » « ClassA is more abstract / generalised than ClassB »...

6 Training: INSPIRE Basics EC JRC 6/15 Inheritage / generalisation Bus passengerNb : Integer Vehicle ownerName : String Boat draft : Float Car constructionDate : Date « Cars, boats, and buses are vehicles » « All vehicles have a construction date » « A bus is a vehicle with a passenger number value » … abstract classes (shown in italics) cannot have instances

7 Training: INSPIRE Basics EC JRC 7/15 Association ClassAClassB c..d a..b AssotiationName roleA roleB CompanyPerson 0..* 1..* Employment employer employee Definition: relationship between classes that specifies connections between their instances Example:

8 Training: INSPIRE Basics EC JRC 8/15 Multiplicity CompanyPerson 0..* Employment employer employed Individual « Companies and persons are linked with an employment relation » « A person can be employed by zero, one or several companies » « A company can employ zero, one or several persons » Kinship « There is a kinship relation between individuals » « All individuals have exactly 2 parents » « Each individual can have no, one or several children » parent child 0..* 2 Examples:

9 Training: INSPIRE Basics EC JRC 9/15 Aggregation Definition: Aggregation relationship between instances of a class and several instances of another class Example: AggregateClassAggregatedClass c..d a..b « A ClassA instance is an aggregate of instances of classB » CountryRegion * 1 « A country is an aggregation of regions »

10 Training: INSPIRE Basics EC JRC 10/15 Composition Definition: Composition relationship between instances of a class and several instances of another classe (they cannot exist independently Example: CompositeClassComponantClass * 1 « A classA instance is a a composite of instances of classB » BookPage 2..* 1 « A book is composed of pages (at least two) »

11 Training: INSPIRE Basics EC JRC 11/15 Navigability Definition: Indication, whether instances of one class can see or know about instances of another class to which they are related through an association CompanyPerson * 0..2 supplier user « A Person instance knows the Company instances it is associated with » « A Company instance does not know the Person instances it is associated with »

12 Training: INSPIRE Basics EC JRC 12/15 Note Definition: Comment or a constraint attached to a diagram element. Usually linked to the element it is related to (with dashed line) In natural language ClassA Comment on classA

13 Training: INSPIRE Basics EC JRC 13/15 Constraint Definition: condition or restriction to satisfy. Can be represented in {…} or in a note In natural language, or OCL (when possible) ClassA ClassA objects should be like this {ClassA objects should be like that}

14 Training: INSPIRE Basics EC JRC 14/15 Stereotype Definition: Stereotypes extend the semantics, but not the structure of pre-existing UML elements (classes, attributes, operations, associations, roles, packages) UML representation: > ClassName > + attributeName : DataType

15 Training: INSPIRE Basics EC JRC 15/15 Exercise: What is represented here? INSPIRE UML class diagram for administrative units


Download ppt "Training: INSPIRE Basics EC JRC 1/15 UML class diagram: example INSPIRE UML class diagram for administrative units."

Similar presentations


Ads by Google