INF5120 Modellbasert Systemutvikling Modelbased System development

Transcription

1 INF5120 Modellbasert Systemutviklig Modelbased System developmet Lecture 7: Are-Jørge Berre or Telecom ad Iformatics 1

2 Cotet Itroductio to Metamodels ad UML Profiles Itroductio to Eclipse, EMF ad Sirius Group presetatios for Oblig 1 Telecom ad Iformatics 2

3 Course parts (16 lectures) Jauary February (1-7) (BAE/WebRatio): MDE-1: Itroductio to INF5120 MDE-2: Modelig structure ad behaviour (UML ad UML 2.0 ad metamodelig) ( B. Hjelle) BAE-1: Busiess Architecture Busiess Model Cavas - Strategyzer tool. SAE-1: WebRatio for Mobile App developmet (Get a App up ad ruig!) BAE-2: Essece, Scrum, User stories ad Use cases 2.0, Backlog, with Someoe BAE-3: BPMN process, VDML ad UML Activ.Diagrams, (MD/EA, Smaply ad Balsamiq) BAE-4: Service Desig, AT ONE,Touchpoits, UI, UX, Smaply ad Balsamiq (Amela, Raghild) Oblig 1: BA Spec, WebRatio App1 (idividual) (ed of February, March 7 th ), Agile Scrum March (8,9,10) (MDE/IFML/Cliet-Side): MDE-3: Model drive egieerig Metamodels, DSL, UML Profiles, EMF, Sirius Editors SAE-2: IFML Iteractio Flow Modelig Laguage, WebRatio advaced MDE-4: DSLs MOFScript, ATL Eclipse Sirius, trasformatio techologies Oblig 2: Sirius DSL Editor for IFML +/- (idivual), WebRatio/IFML App2 UI (simple) (ed of March, April 11 th ) April (11,12,13) (SAE/UML/Server-side): SAE-3: WebRatio Server side ad IFML, Data models/uml, Architecture patters SAE-4: UML Service Modelig, ServiceML,SoaML, UML 2.0 Compositio, MagicDraw SAE-5: No Fuctioal requiremets OCL ad PLaguage Oblig 3: SA Spec (More models), WebRatio/IFML App 3 Server (ed of April, May 2 d ) May (14,15,16): (Brigig it together) SAE-6: Fial WebRatio App demo ad discussio day (May 2 d ) MDE-5: Eterprise Architecture, TOGAF, UPDM, SysML DSLs etc. Big picture MDE-6: Coclusios/Summary of the course Exam (4 hours), (Jue 6 th ) Telecom ad Iformatics 3

4 OMG Model-Drive Architecture (MDA) Telecom ad Iformatics 4

5 Model-drive a defiitio A system developmet process is model-drive if the developmet is maily carried out usig coceptual models at differet levels of abstractio ad usig various viewpoits it distiguishes clearly betwee platform idepedet ad platform specific models models play a fudametal role, ot oly i the iitial developmet phase, but also i maiteace, reuse ad further developmet models documet the relatios betwee various models, thereby providig a precise foudatio for refiemet as well as trasformatio Telecom ad Iformatics 5

6 MDA From Feet J2EE.Net A PIM ca be retargeted to differet platforms Not the oly reaso why MDA might be of iterest to you Telecom ad Iformatics 6

7 Automatio i Software Developmet Requiremet s Maually implemet Requiremet s Maually implemet Requiremet s Maually implemet Source i domai-specific laguage (DSL) High-level spec (fuctioal ad ofuctioal) Source i domai-specific laguage (DSL) Implemet with Iteractive, automated support Compile Compile Source i a geeral-purpose laguage, e.g., Java or C++ (may geerate code i Java or C++) (may geerate code i Java or C++) Compile Compile Compile Implemetatio Implemetatio Implemetatio Telecom ad Iformatics 7

8 Basic MDA Patter PIM Trasformatio PSM Additioal iformatio Model markup Geeric trasformatio Geeric trasformatios Implemet best practices, architectural ad desig patters, techology patters (e.g., J3EE patters), optimizatios, etc. Additioal iformatio Adjust the trasformatio globally Similar to compiler optios Model markup Direct the trasformatio of particular model elemets Not part of the PIM Differet platform mappigs may require differet markup Similar to compiler pragmas Telecom ad Iformatics 8

9 Goals The three primary goals of MDA are portability, iteroperability ad reusability. The MDA starts with the well-kow ad log established idea of separatig the specificatio of the operatio of the system from the details of the way the system uses the capabilities of its software executio platform (e.g. JEE, CORBA, Microsoft.NET ad Web services). MDA provides a approach for: specifyig a system idepedetly of the software executio platform that supports it; specifyig software executio platforms; choosig a particular software executio platform for the system; trasformig the system specificatio ito oe for a particular software executio platform; Telecom ad Iformatics 9

10 Basic cocepts System Existig or plaed system. System may iclude aythig: a program, a sigle computer system, some combiatio of parts of differet systems Model A model of a system is a descriptio or specificatio of that system ad its eviromet for some certai purpose. A model is ofte preseted as a combiatio of drawigs ad text. Architecture The architecture of a system is a specificatio of the parts ad coectors of the system ad the rules for the iteractios of the parts usig the coectors. MDA prescribes certai kids of models to be used, how those models may be prepared ad the relatioships of the differet kids of models. Viewpoit A viewpoit o a system is a techique for abstractio usig a selected set of architectural cocepts ad structurig rules, i order to focus o particular cocers withi that system. View A viewpoit model or view of a system is a represetatio of that system from the perspective of a chose viewpoit. Platform A platform is a set of subsystems ad techologies that provide a coheret set of fuctioality through iterfaces ad specified usage patters, which ay applicatio supported by that platform ca use without cocer for the details of how the fuctioality provided by the platform is implemeted. Telecom ad Iformatics 10

11 MDA Three mai abstractio levels Computatio idepedet model (CIM) The computatioal idepedet viewpoit is focused o the eviromet of the system ad o the specific requiremets of the system. A CIM represets the computatioal idepedet viewpoit. The CIM hides the structural details ad, of course, the details related to the targeted platform. Platform idepedet model (PIM) A platform idepedet model is a view of the system from a platform idepedet viewpoit. The platform idepedet viewpoit is focused o the operatio of the system, hidig the platform specific details. A PIM exhibits platform idepedece ad is suitable for use with a umber of differet platforms of similar types. The PIM gathers all the iformatio eeded to describe the behaviour of the system i a platform idepedet way. Platform specific model (PSM) A platform specific model is a view of the system from the platform specific viewpoit. A PSM combies the specificatios i the PIM with the details that specify how the system uses a particular type of platform. The PSM represets the PIM takig ito accout the specific platform characteristics. Telecom ad Iformatics 11

12 Model-drive developmet (MDD) Model trasformatio Model trasformatio CIM PIM Busiess Cotext Models Software Specificatio Models PSM Software Realisatio Models Model-drive approach to system egieerig where models are used i uderstadig desig costructio deploymet operatio maiteace modificatio Model trasformatio tools ad services are used to alig the differet models. Busiess-drive approach to system egieerig where models are refied from busiess eeds to software solutios Computatio idepedet model (CIM) capturig busiess cotext ad busiess requiremets Platform idepedet model (PIM) focusig o software services idepedet of IT techology Platform specific model (PSM) focusig o the IT techology realisatio of the software services Telecom ad Iformatics 12

13 Basic MDA Patter The basic patter ca be applied multiple times PIMs ad PSMs are relative otios Someoe s PIM ca be someoe else s PSM Platform idepedece is relative, too It s a scopig issue It s a strategic decisio Telecom ad Iformatics 13

14 Role of Models Capture desig iformatio that is usually abset from code ad lost durig developmet Basis for System geeratio Aalysis Simulatio Test geeratio Documetatio geeratio Domai-specificity of a modelig laguage stregthes its capabilities for geeratio, optimizatio, early error detectio, etc. Telecom ad Iformatics 14

15 Viewpoits ad Views System models are orgaized ito multiple views Differet abstractio levels Differet aspects (e.g., workflow, domai cocepts, deploymet) Each view coforms to some viewpoit that prescribes some appropriate modelig otatio Each viewpoit is relevat to some stakeholder Telecom ad Iformatics 15

16 May differet views Telecom ad Iformatics 16

17 MDA-Related Stadards OMG Stadards Modelig UML Metamodelig MOF Actio sematics Model iterchage XMI Diagram iterchage Huma-readable textual otatio HUTN Model-based testig ad debuggig (CWM) Java Commuity Process (JCP) Stadard Java Metadata Iterface JMI Telecom ad Iformatics 17

18 Beefits of MDA Preservig the ivestmet i kowledge Idepedet of implemetatio platform Tacit kowledge made explicit Speed of developmet Most of the implemetatio is geerated Quality of implemetatio Experts provide trasformatio templates Maiteace ad documetatio Desig ad aalysis models are ot abadoed after writig 100% traceability from specificatio to implemetatio Telecom ad Iformatics 18

19 Domai specific modellig laguages Specific to a domai More focussed purpose Usable by the domai experts More productive tha geeral purpose If properly desiged ad tooled! UML profiles vs. DSL Telecom ad Iformatics 19

20 Assigig Meaig to Models If a model is o loger just facy pictures to decorate your room a graphical sytax for C++/Java/C#/Eiffel... The tools must be able to maipulate models Let s make a model of what a model is! => meta-modelig & meta-meta-modelig.. Use Meta-Object Facility (MOF) to avoid ifiite Meta-recursio {ordered} +subtype Geeralizes 0..* +supertype 0..1 {ordered} 0..* +cotaier +cotaiedelemet Cotais Namespace GeeralizableElemet 0..* ModelElemet Feature BehavioralFeature +costraiedelemet 1..* Costrait StructuralFeature Costrais 0..* Package Classifier Operatio Referece MofAttribute 0..* +referet RefersTo DataType Class Associatio 1 +refereceded AssociatioEd Telecom ad Iformatics

21 UML2 meta-model (part., OMG) Telecom ad Iformatics

22 Geeralizatios NB: Tell you othig about: geeralizatio beig acyclic, or sematics of dyamic bidig * Telecom ad Iformatics OMG

23 The 4 layers i practice Telecom ad Iformatics OMG

24 Comparig Abstract Sytax Systems M 3 Techology #1 Techology #2 (formal grammars (MOF + OCL) attribute grammars, etc.) EBNF MOF Techology #3 (XML Meta-Laguage) A XML DTD Or Schema Techology #4 (Otology egieerig) Upper Level Otologies M 2 Pascal Laguage Grammar The UML meta-model A XML documet A XML DTD or Schema KIF Theories M 1 A specific Pascal Program A specific executio of a Pascal program A Specific UML Model A Specific pheomeo correspodig to a UML Model A XML documet + Xlik, Xpath, XSLT + RDF, OIL, DAML + etc. [XMI=MOF+XML+OCL] +Descriptio Logics +Coceptual Graphs +etc. Telecom ad Iformatics

25 Model-Drive Architecture coformsto meta Metametamodel Metametamodel elemet MOF M3 meta coformsto M2 Metamodel elemet Metamodel Relatioal metamodel UML metamodel meta coformsto System repof M1 Model elemet Model Telecom ad Iformatics 25

26 Model-Drive Architecture: Example MOF Metametamodel Associatio source destiatio Class coformsto coformsto Relatioal Metamodel Table Colum + col * ame: Strig+ ower ame: Strig * {ordered} + keyof 1..* + key * Type + type ame: Strig coformsto System repof BookId Relatioal Model Title PagesNb AuthorId Book Telecom ad Iformatics 26

27 MDA techology stadards Uified Modelig Laguage (UML) UML is the de-facto stadard idustry laguage for specifyig ad desigig software systems. UML addresses the modellig of architecture ad desig aspects of software systems by providig laguage costructs for describig, software compoets, objects, data, iterfaces, iteractios, activities etc. Meta Object Facility (MOF) MOF provides the stadard modellig ad iterchage costructs that are used i MDA. These costructs are a subset of the UML modellig costructs. This commo foudatio provides the basis for model/metadata iterchage ad iteroperability. XML Metadata Iterchage (XMI) XMI is a format to represet models i a structured text form. I this way UML models ad MOF metamodels may be iterchaged betwee differet modellig tools. Commo Warehouse Metamodel (CWM) CWM is the OMG data warehouse stadard. It covers the full life cycle of desigig, buildig ad maagig data warehouse applicatios ad supports maagemet of the life cycle. MOF Queries/View/Trasformatios (QVT) The goals of the QVT are to provide a stadard specificatio of a laguage suitable for queryig ad trasformig models which are represeted accordig to a MOF metamodel. Telecom ad Iformatics 27

28 How does MDD work? Developer develops model(s) based o certai metamodel(s). Model Model Model Metamodel Usig code geeratio templates, the model is trasformed to executable code. Optioally, the geerated code is merged with maually writte code. Trasformer Model Traformatio Rules Metamodel optioal, ca be repeated Oe or more model-to-model trasformatio steps may precede code geeratio. Trasformer Code Geeratio Templates Geerated Code Maually Writte Code optioal Telecom ad Iformatics 28

29 OMG MOF ad metamodellig Telecom ad Iformatics 29

30 Fragmets of a UML metamodel UML Telecom ad Iformatics 30

31 Three stages i the evolutio of modellig techiques at the OMG. (a) (b) (c) UML MOF MOF amodel UML UML SPEM Workflow etc. amodel UML_for_CORBA Commo Warehouse Metadata amodel Actio laguage Telecom ad Iformatics 31

32 Egyptia architecture M 3 meta-meta model The MOF M 1 M 2 metamodel model The UML meta-model ad other MM s Some UML models ad other M s Various usages of these models M 0 the real world" Telecom ad Iformatics 32

33 Illustratio Java MM Package MOF Class Associatio UML MM M3 Iterface Package Class exteds Class Associatio M2 Presetatio Participat Java program Participat listes Presetatio UML model M1 Telecom ad Iformatics 33

34 The three modellig levels M 3 level the MOF MMM M 2 level the UPM MM (SPEM) the UML MM the CWM MM CCM EDOC etc. M 1 level a UML model m aother UML model m M 0 level a particular use of m aother use of m Telecom ad Iformatics 34

35 Model -> Metamodel etity meta-etity UML MM relatioship Class 1 * Attribute model meta-model relatioship UML model Cliet Name: Strig Telecom ad Iformatics 35

36 Metamodel -> Meta-metamodel MOF etity meta-etity relatioship model meta-model Class source destiatio Associatio relatioship UML MM Class 1 * Attribute Telecom ad Iformatics 36

37 0..* Cotais ModelElemet /Depeds O 1..* Costrais 1..* AttachesTo MOF Model (M3) 0..* 0..* Import Namespace Tag{ordered} 0..* Costrait TypedElemet 0..* Aliases 0..* IsOfType 0..* +typedelemet GeeralizableElemet Geeralizes Feature Costat StructureField Parameter Package +type1 Classifier BehaviouralFeature StructuralFeature AssociatioEd /Exposes 1 1 ReferesTo Associatio Class DataType 0..* Operatio Exceptio Attribute Referece 0..* CaRaise 0..* {ordered} PrimitiveType StructureType EumeratioType CollectioType AliasType Telecom ad Iformatics 37

38 Goals & Challeges Goals: We eed a ed-to-ed tool chai that allows us to build models, verify them ad geerate various artefacts from them. All of this should happe i a homogeeous eviromet, amely Eclipse. Challeges: Good Editors for your models Verifyig the models as you build them Trasformig/Modifyig models Geeratig Code Itegratig geerated ad o-geerated code Telecom ad Iformatics 38

39 Applied metamodellig Telecom ad Iformatics 39

40 Metamodels A metamodel is just aother model (e.g. writte i UML) Model of a set of models Metamodels are specificatios Models are valid if o false statemets accordig to metamodel (e.g. well-formed) Metamodels typically represets domai-specific models (real-time systems, safety critical systems, e-busiess) The domai of metamodellig is laguage defiitio A metamodel is a model of some part of a laguage Which part depeds o how the metamodel is to be used Parts: sytax, sematics, views/diagrams,... Meta-metamodel Model of metamodels Reflexive metamodel, i.e., expressed usig itself Miimal reflexive metamodel Telecom ad Iformatics 40

41 What is a metamodel? I its broadest sese, a metamodel is a model of a modellig laguage. The term meta meas trascedig or above, emphasisig the fact that a metamodel describes a modellig laguage at a higher level of abstractio tha the modellig laguage itself. I order to uderstad what a metamodel is, it is useful to uderstad the differece betwee a metamodel ad a model. Whilst a metamodel is also a model, a metamodel has two mai distiguishig characteristics. Firstly, it must capture the essetial features ad properties of the laguage that is beig modelled. Thus, a metamodel should be capable of describig a laguage s cocrete sytax, abstract sytax ad sematics. Secodly, a metamodel must be part of a metamodel architecture. Just as we ca use metamodels to describe the valid models or programs permitted by a laguage, a metamodel architecture eables a metamodel to be viewed as a model, which itself is described by aother metamodel. This allows all metamodels to be described by a sigle metamodel. This sigle metamodel, sometimes kow as a meta-metamodel, is the key to metamodellig as it eables all modellig laguages to be described i a uified way. Telecom ad Iformatics 41

42 Why metamodel? System developmet is fudametally based o the use of laguages to capture ad relate differet aspects of the problem domai. The beefit of metamodellig is its ability to describe these laguages i a uified way. This meas that the laguages ca be uiformly maaged ad maipulated thus tacklig the problem of laguage diversity. For istace, mappigs ca be costructed betwee ay umber of laguages provided that they are described i the same metamodellig laguage. Aother beefit is the ability to defie sematically rich laguages that abstract from implemetatio specific techologies ad focus o the problem domai at had. Usig metamodels, may differet abstractios ca be defied ad combied to create ew laguages that are specifically tailored for a particular applicatio domai. Productivity is greatly improved as a result. Telecom ad Iformatics 42

43 Uses for a metamodel Defie the sytax ad sematics of a laguage. Explai the laguage. Compare laguages rigorously. Specify requiremets for a tool for the laguage. Specify a laguage to be used i a meta-tool. Eable iterchage betwee tools. Eable mappig betwee models. Telecom ad Iformatics 43

44 The metamodellig process There is a clearly defied process to costructig metamodels, which does at least make the task a well-defied, if iterative, process. The process has the followig basic steps: defiig abstract sytax defiig well-formedess rules ad meta-operatios defiig cocrete sytax defiig sematics costructig mappigs to other laguages Telecom ad Iformatics 44

45 Abstract sytax The metamodel describes the abstract sytax of a laguage. The abstract sytax of a laguage describes the vocabulary of cocepts provided by the laguage ad how they may be combied to create models. It cosists of a defiitio of the cocepts, the relatioships that exist betwee cocepts ad well-formedess rules that state how the cocepts may be legally combied. Telecom ad Iformatics 45

46 Cocrete sytax visual A visual sytax presets a model or program i a diagrammatical form. A visual sytax cosists of a umber of graphical icos that represet views o a uderlyig model. A good example of a visual sytax is a class diagram, which provides graphical icos for class models. The visual sytax show i the figure (left) is particularly good at presetig a overview of the relatioships ad cocepts i a model. Telecom ad Iformatics 46

47 Cocrete sytax textual A textual sytax eables models or programs to be described i a structured textual form. A textual sytax ca take may forms, but typically cosists of a mixture of declaratios, which declare specific objects ad variables to be available, ad expressios, which state properties relatig to the declared objects ad variables. The followig Java code illustrates a textual sytax that icludes a class with a local attribute declaratio ad a method with a retur expressio: Telecom ad Iformatics 47

48 Challeges facig developers Complexity Diversity Chage Telecom ad Iformatics 48

49 Laguage-drive developmet Providig the solutio Executio Aalysis allows the model or program to be tested, ru ad deployed provides iformatio of the properties of models ad programs Testig Visualisatio support for both geeratig test cases ad validatig them must be provided may laguages have a graphical sytax, ad support must be provided for this via the user iterface to the laguage Parsig if a laguage has a textual sytax, a meas must be provided for readig i expressios writte i the laguage Traslatio laguages do t exist i isolatio. They are typically coected together whether it is doe iformally or automatically through code geeratio or compilatio Itegratio it is ofte useful to be able to itegrate features from oe model or program ito aother, e.g. through the use of cofiguratio maagemet. Telecom ad Iformatics 49

50 Laguage egieerig ad metamodellig I order to be able to egieer laguages, we eed a laguage for capturig, describig ad maipulatig all aspects of laguages i a uified ad sematically rich way. This laguage is called a metamodellig laguage. Metamodels (models of laguages) are the primary meas by which laguage egieerig artefacts are expressed, ad are therefore the foudatio for laguage-drive developmet. Telecom ad Iformatics 50

51 Sematics A abstract sytax coveys little iformatio about what the cocepts i a laguage actually mea. Therefore, additioal iformatio is eeded i order to capture the sematics of a laguage. Defiig a sematics for a laguage is importat i order to be clear about what the laguage represets ad meas. Otherwise, assumptios may be made about the laguage that lead to its icorrect use. For istace, although we may have a ituitive uderstadig of what is meat by a state machie, it is likely that the detailed sematics of the laguage will be ope to misiterpretatio if they are ot defied precisely. What exactly is a state? What does it mea for trasitio to occur? What happes if two trasitios leave the same state. Which will be chose? All these questios should be captured by the sematics of the laguage. Telecom ad Iformatics 51

52 Laguage Egieerig with Eclipse Modelig Framework (EMF) Telecom ad Iformatics 52

53 The Laguage Egieer resposibilities Telecom ad Iformatics 53

54 Metamodel developmet Uderstadig of cocepts ad requiremets Iitial requiremets Cocepts Partitioig of the metamodel ito structures Architectural style Documet the metamodel ad develop it i EMF (.ecore) 1. Metamodel Scope, cocepts, style 4. Feedback Add, remove, ad modify cocepts 2. DSL ad/or UML profile Create cocrete sytax (graphics) 3. Test Evaluate i user scearios Telecom ad Iformatics 54

55 Characteristics for metamodel Suited for target roles Support domai cocepts ad scearios of target roles Ease-of-use ad uderstadable for busiess modeller (use terms) Support precise details ad correctess for solutio architect Avoid uecessary complexity Keep it simple stupid (KISS) Number of elemets ad associatios Type ad avigatio of associatios Make it modular Provide core with extesios Defie ad illustrate possible subsets ( dialects ) that support scearios Cosider itegratio ad extesio poits Suited for implemetatio EMF represetatio Trasformatio from/to UML profile Trasformatio to PSM Telecom ad Iformatics 55

56 Techology overview OMG MDA specificatio Eclipse techology Commets MOF UML EMF UML UML profile/dsl QVT MOF2TExt SPEM XMI GEF GMF ATL, MOFScript MOFScript EPF EMF Telecom ad Iformatics 56

57 MDA-compliat Eclipse techologies Sirius Eclipse Modelig Tools: Eclipse Modelig Framework (EMF) EMF is a modelig framework ad code geeratio facility for buildig tools ad other applicatios based o a structured data model. Eclipse Graphical Editig Framework (GEF) The Graphical Editig Framework (GEF) allows developers to take a existig applicatio model ad quickly create a rich graphical editor. Eclipse Graphical Modelig Framework (GMF) The Eclipse Graphical Modelig Framework (GMF) provides a geerative compoet ad rutime ifrastructure for developig graphical editors based o EMF ad GEF. Eugeia EuGENia is a tool that automatically geerates the.gmfgraph,.gmftool ad.gmfmap models eeded to implemet a GMF editor from a sigle aotated Ecore metamodel Atlas Trasformatio Laguage The ATL project aims at providig a set of trasformatio tools for GMT. These iclude some sample ATL trasformatios, a ATL trasformatio egie, ad a IDE for ATL (ADT: ATL Developmet Tools). Eclipse Process Framework (EPF) To provide a extesible framework ad exemplary tools for software process egieerig - method ad process authorig, library maagemet, cofigurig ad publishig a process. Telecom ad Iformatics 57

58 EMF Eclipse Modelig Framework Uifyig Java, XML ad (almost) UML EMF models are essetially simplified UML Class Diagrams EMF geerates Java code based o these models Stadard serializatio is i the form of XMI EMF is MDA o traiig wheels Telecom ad Iformatics 58

59 EMF Models ad Ecore Ecore is the model used to represet EMF models Ecore is also a EMF model ad therefore its ow metamodel Ad its ow meta-meta-.-model, but ever mid Available elemets are: EClass EAttributes EReferece EDataType EEum, EEum Literal EPackage EOperatio, EParameter Coceptually equal to OMGs Essetial MOF (EMOF) Telecom ad Iformatics 59

60 Creatig your model Ca be defied i three ways Java XML Schema Directly maipulate the model (the almost UML way) Both Java ad XML Schema approach builds a EMF model Editig the model ca be doe with the EMF tree editor or the GMF graphical editor It is also possible to import Ratioal Rose (.mdl) files Telecom ad Iformatics 60

61 3 shades of EMF Ecore model Geerated Java files Creatio of a istace Book book = LibraryFactory.eINSTANCE.createBook(); book.settitle( How to be a meta role model ); Telecom ad Iformatics 61

62 GMF The Eclipse Graphical Modelig Framework (GMF) project is a ope source project uder the Eclipse Techology Project Ifrastructure ad compoets for developig visual desig ad modelig surfaces i Eclipse UML editors Busiess process editors Etc.. GMF forms a geerative bridge betwee EMF ad GEF A diagram defiitio (GEF) will be liked to a domai model (EMF) as iput to the geeratio of a visual editor Telecom ad Iformatics 62

63 GMF Graphical Modelig Framework Utilizes EMF ad GEF to support geeratio of graphical editors GEF Graphical Editig Framework Basic idea: Brig your ow model Defie diagram otatio Defie your tools Map model elemets to diagram elemets Geerate editor Metamodel = Abstract Sytax Diagram otatio = Cocrete Sytax Telecom ad Iformatics 63

64 Simplified workflow Telecom ad Iformatics 64

65 UML profiles Telecom ad Iformatics 65

66 UML profiles They allow us to adapt the UML laguage to the eeds of the aalysts or the applicatio domai Allows desigers to model usig applicatio domai cocepts. There are three extesio mechaisms: Stereotypes Restrictios Tagged values Telecom ad Iformatics 66

67 Stereotype Exteds the vocabulary of UML with ew costructio elemets derived from existig UML but specific to a problem domai Ca have associated restrictios ad tagged values Possibility of assigig a ico for a better graphical represetatio DB Parters Telecom ad Iformatics 67

68 Restrictio Is a sematical coditio represeted by a textual expressio Imposes some kid of coditio or requisite o the elemet to which it is applied OCL Object Costrait Laguage {A iterface does ot have attributes, oly operatios} Telecom ad Iformatics 68

69 Tagged value Is a property associated to a model elemet Used to store iformatio about the elemet Maagemet iformatio, documetatio, codig parameters,... Geerally, the tools store this iformatio but it is ot show i the diagrams Telecom ad Iformatics 69

70 Metamodels ad profiles model <-> meta-model relatioship extesio relatioship MOF M3 UML process geeric Meta-model M2 UML Real-time UML For J2EE Migratio orieted process Meta-model Workflow Meta-model real-time model migratio model Workflow model M1 Telecom ad Iformatics 70

71 Domai-specific laguages (DSLs) Telecom ad Iformatics 71

72 UML oe size fits all? While the OMG MDA promotes UML as the visual uiversal glue suitable for modellig everythig, we are also seeig a tred towards developmet ad co-existece of several domai-specific modellig laguages, e.g. supported by the Microsoft Domai-Specific Laguage (DSL) tools ( Such approaches are ow also beig discussed i various OMG forums. UML is see as a geeral-purpose laguage while DSLs may be more expressive for most purposes. A model-drive framework eeds to ackowledge the existece of differet models ad views expressed i differet modellig laguages. The MDA techologies ca help us to alig these models through a commo metamodellig laguage o which model trasformatios ad model mappigs ca be defied. Telecom ad Iformatics 72

73 Software factory The Software Factories Web site ( defies the term Software Factory i the followig way: A Software Factory is a software product lie that cofigures extesible developmet tools like Visual Studio Team System with packaged cotet like DSLs, patters, frameworks ad guidace, based o recipes for buildig specific kids of applicatios. For example, we might set up a Software Factory for thi cliet Customer Relatioship Maagemet (CRM) applicatios usig the.net framework, C#, the Microsoft Busiess Framework, Microsoft SQL Server, ad the Microsoft Host Itegratio Server. Equipped with this factory, we could rapidly puch out a edless variety of CRM applicatios, each cotaiig uique features based o the uique requiremets of specific customers. Better yet, we could use this factory to create a ecosystem, by makig it available to third parties, who could exted it to rapidly build CRM applicatios icorporatig their value added extesios. Telecom ad Iformatics 73

74 UML ad DSLs The issue of the role of UML is ofte stated i overly simplistic terms: MDD advocates the use of UML for all domai modellig while the Software Factories approach advocates that UML ever used. This is a icorrect statemet of the positios of both camps. While the MDD approach treats UML, with customizatio, as the modellig laguage of choice for most applicatio modellig, it also ackowledges the value of custom laguages i certai specialized circumstaces. This is the purpose of the OMG Meta-Object Facility (MOF) stadard that plays a importat role i MDD. UML itself is defied usig MOF ad there are MOF defiitios of may other laguages. The MDD approach ackowledges the value of o-uml DSLs as a techique to be applied judiciously. Further, the Software Factories approach does ot reject UML etirely. It suggests that you use UML for developig sketches ad documetatio, where DSLs should be used for developig models from which code is geerated. Telecom ad Iformatics 74

75 Advatages of usig UML profiles UML is a ope stadard modellig laguage for which there are may available books ad traiig courses. UML profiles provide a lightweight approach that is easily implemeted usig readily available UML toolig. Models with UML profiles applied ca be read by all UML tools eve if they do ot have ay kowledge of the profile. Basig all DSLs o UML creates a set of related laguages that share commo cocepts. UML ca be used for high-level architectural models as well as detailed models from which code ca be geerated. Telecom ad Iformatics 75

76 Disadvatages of usig UML profiles UML profiles oly permit a limited amout of customizatio. It is ot possible to itroduce ew modellig cocepts that caot be expressed by extedig existig UML elemets. The use of UML does require familiarity with modellig cocepts. Telecom ad Iformatics 76

77 Example Metamodels UML Use case Metamodel BPMN Metamodel IFML Metamodel Oblig 3 Visual Service Jourey laguage Telecom ad Iformatics 77

78 UML Use Case Metamodel Telecom ad Iformatics 78

79 BPMN Metamodel Telecom ad Iformatics 79

80 BPMN Defiitios Telecom ad Iformatics 80

81 IFML Metamodel Telecom ad Iformatics 81

82 Oblig 2 Use of Eclipse EMF ad SIRIUS for your selected modelig laguage/diagram techique Telecom ad Iformatics 82

83 Scope Maager metamodel Telecom ad Iformatics 83

84 Dictioary metamodel Telecom ad Iformatics 84

85 Some historic refereces [Atkiso ad Kühe 2003] C. Atkiso ad T. Kühe, "Model-Drive Developmet: A Metamodelig Foudatio", IEEE Software, vol. 20, o. 5, pp , [Clark, et al. 2004] T. Clark, A. Evas, P. Sammut, ad J. Willas, "Applied Metamodellig - A Foudatio for Laguage Drive Developmet, Versio 0.1", [Seidewitz 2003] E. Seidewitz, "What Models Mea", IEEE Software, vol. 20, o. 5, pp , [Swithibak, et al. 2005] P. Swithibak, M. Chessell, T. Garder, C. Griffi, J. Ma, H. Wylie, ad L. Yusuf, "Patters: Model-Drive Developmet Usig IBM Ratioal Software Architect", IBM, Redbooks, December Telecom ad Iformatics 85

86 Next lecture - Moday March 14th, 2016 Lecture o IFML ad use of WebRatio Mobile platform Delivery deadlie for Oblig 1 Presetatio of Oblig 2 Eclipse/Sirius ad CitiZese App Demostratio of Eclipse, EMF ad Sirius Telecom ad Iformatics 86