UML VOOR GEO DATA. Welke Diagram(en) zijn geschikt voor Lineage. Anneke Kleppe, Capgemini Netherlands

Transcriptie

1 UML VOOR GEO DATA Welke Diagram(en) zijn geschikt voor Lineage Anneke Kleppe, Capgemini Netherlands

2 VOORAF Breaks Mobiles Introductions Smoking Course Timing Meals 2

3 WAAROM UML Open standaard Goed uitwisselingsformaat Binnen project Nationaal Internationaal Ondersteund door groot aantal tools Enterprise Architect, MagicDraw, Rational Software Architect, See 3

4 DE 13 UML DIAGRAMMEN 4

5 OVERVIEW UML-STRUCTURE DIAGRAMS cd 01 Class Diagram cd 03 Composite Structure Diagram id 05 Component Diagram Auto Class1 OrderComp CustomerComp Motor Tire Part1 Part2 SpaceTire ActiveTire Account cd 02 Object Diagram pd 04 Package Diagram dd 06 Deployment Diagram Package2 Server client mijnhond :Hond naam = "Snoopy" geboortedatum = "14/07/2005" oornummer = 007 vachtkleur = "zwart" Package1 «import» «artifact» Art1 TCP/IP 5

6 OVERVIEW UML-BEHAVIOR DIAGRAMS ud 07 Use Case Diagram sm 08 State Machine Diagram ad 09 Activity Diagram Activity1 Withdraw money State1 Action2 «include» Included use case State4 Customer Request amount State2 State3 Action1 Action3 Action4 sd 10 Interaction Overview Diagram sd 11 Sequence Diagram :Class1 :Class2 :Class3 :Class4 Action5 :ActorX m1() critical authorisatie m2() m3() Action6 loop m4() sd ExampleSDDiagram m5() :Client :Server result= getdata() sd 12 Communication Diagram td 13 Timing Diagram [condition1] 1: m1() eenactor1 : ActorX :Class1 2: m2() :Class2 Lamp on defective off buy switchon {40} burnout ref [condition2] 09 Activity Diagram 2.3: m5() :Class4 2.2: m4() 2.1: m3() :Class3 state buy off switchon on defective burnout

7 CLASS DIAGRAM Class diagrams show the types of the elements in the system Typically used to model Domain objects / entities Application objects 7

8 CONCEPTUAL LEVEL 8

9 SYSTEM LEVEL MUCH MORE DETAIL 9

10 BASIC NOTATIONAL ELEMENTS ClassX Class - conceptual ClassY Class - detailed Association Composition Inheritance 0..* Multiplicity Dependency ob1:classx Object - conceptual ob1:classy Object - detailed attr = 10 10

11 GLOSSARY CLASS DIAGRAM -1 Class. The rectangles represent classes. A class is the type of a set of objects or instances. Object. The rectangles with underlined text represent objects, also called instances. Each object belongs to a class. Association. The lines on the diagram between classes represent relationship between classes. When two classes are associated, their objects have links. Link. The lines on the diagram between objects represent are links. 11

12 GLOSSARY CLASS DIAGRAM - 2 Multiplicity. The numbers at each side of an association indicate how many objects may be related. Composition. The diamond with line between two classes indicates a composition relationship. One object of the class at the diamond side can be composed of multiple objects of the class at the other side. Inheritance. The open arrowhead indicates a super-subclass relationship. The subclass has all the properties of the superclass (the class at the arrowhead). Dependency. The dotted arrow indicates that there is a dependency between the two elements. 12

13 ACTIVITY DIAGRAM Activity diagrams show flow of control and data flow Typically used to model Business process Process workflow Flow within a use case Business rules logic Modeling of methods A1 A2 A4 A5 A3 13

14 HIERARCHY OF DIAGRAMS One activity can be specified in another, lower level, diagram A1 A2 A4 A5 A3 Activity A3 A6 A8 A7 14

15 BASIC NOTATIONAL ELEMENTS Control Flow Data Flow Action Object Node (may include state) Decision Node Merge Node Fork Node Join Node Initial Node Activity Final Flow Final 15

16 BUSINESS PROCESS Receive order Fill order Ship order Close order Send invoice Accept payment Object Invoice Make payment Action/activity Process step 16

17 Customer Company Accounting OrderDepartment PARTITIONING CAPABILITIES Seattle Reno Receive order Fill order Ship order Close order Send invoice Accept payment Invoice Business Object System Object Make payment Business service Process step 17

18 GLOSSARY ACTIVITY DIAGRAM -1 Activity. The rounded rectangles represent activities that occur. An activity may be physical or electronic. Flow/edge. The arrows on the diagram representing the ordering in time of the activities. Initial node. The filled in circle is the starting point of the diagram. An initial node isn t required although it does make it significantly easier to read the diagram. Activity final node. The filled circle with a border is the ending point. An activity diagram can have zero or more activity final nodes. Flow final. The circle with the X through it. This indicates that the process stops at this point. Partition. A diagram can be organized into partitions, also called swim lanes, indicating who/what is performing the activities. 18

19 GLOSSARY ACTIVITY DIAGRAM - 2 Decision. A diamond with one flow entering and several leaving. The flows leaving include conditions of which only one may be true at a certain point in time. Merge. A diamond with several flows entering and one leaving. The implication is that one or more incoming flows must reach this point until processing continues, based on any guards on the outgoing flow. Fork. A black bar with one flow going into it and several leaving it. This denotes the beginning of parallel activity. Join. A black bar with several flows entering it and one leaving it. All flows going into the join must reach it before processing may continue. This denotes the end of parallel processing. Condition. Text such as [Incorrect Form] on a flow, defining a guard which must evaluate to true in order to traverse the node. 19

20 VRAGEN? 20

21 MIJN INTERPRETATIE VAN LINEAGE Gaat om Traceability and Provenance Geo Data Sets en Elementen worden gecreëerd In een bepaalde activiteit Mogelijk met andere data als input Twee kern elementen: De activiteit De gegevens 21

22 HOE LINEAGE WEER TE GEVEN Lineage moet worden vastgelegd in de vorm van meta data Voor opslag is een structuur nodig Best weergegeven in UML Class diagram Voor begrip door menselijke gebruikers is een proces beschrijving nodig Best weergegeven in UML Activity diagram Meest effectief: (Her)creëer Activity diagram uit opslag structuur Moet tool voor gebouwd worden 22

23 VRAAG VAN DE DAG Wat is de beste opslagstructuur? Dit leidt tot de volgende subvragen: Wat moet er eigenlijk opgeslagen worden? Welk soort activiteiten zijn er? Zijn er standaard activiteiten te benoemen? Wie voert de activiteit uit? Wanneer, Met welk doel (waarom), op welke (deel)gegevens? Zijn er andere zaken die per activiteit bijgehouden moeten worden? Is manier waarop data opgeslagen wordt afdoende? 23

24 AANPAK 1. Uitwerken Testcase Noord Brabant in Activity diagram Moet bruikbaar zijn voor mensen 2. Vanuit diagram abstraheren wat als meta data opgeslagen moet worden 3. Vastleggen van structuur van meta data in Class diagram Moet bruikbaar zijn voor computer 24