D15.3 Specifications and Design of Service Lifecycle Management ToolBox M18 issue

Transcription

1 D15.3 Spcifications and Dsign of Srvic Lifcycl Managmnt ToolBox M18 issu Documnt Ownr: Contributors: Dissmination: Contributing to: WP 1.5 Dat: Rvision: Vrsion 1.0 H. Boyé (HARDIS) H.Bazoun (HARDIS), K.Blkhlladi (HARDIS), F.Tournadr (HARDIS), M. Hirsch (DITF), M. Maggio (ENG), Hiko Wittborg (SAP) Public

2 VERSION HISTORY VERSION DATE NOTES AND COMMENTS INITIAL VERSION (HARDIS) CONTRIBUTION BY HARDIS INTEGRATION OF CONTRIBUTIONS SUBMISSION TO PEER REVIEW INTEGRATION OF PEER REVIEW COMMENTS DELIVERABLE PEER REVIEW SUMMARY ID Commnts Rarrang dtaild contnt (.g. mapping tabls) in annx Various cohrnc chcks (.g. xc. summary ; documnt structur figur) Radability improvmnts (.g. : Enlargmnt of crtain figurs ; idntification of rquirmnts) Addrssd () Answrd (A) 4 5 MSEE Consortium Dissmination: Public 2/143

3 TABLE OF CONTENTS EXECUTIVE SUMMARY INTRODUCTION Objctiv of th dlivrabl Structur of th dlivrabl Rlations with othr work packags and dlivrabls Links with WP1.1, WP1.2, WP1.3 and WP Links with WP4.1; WP4.2; WP Rlations with prvious work of WP Mthodology & Projct plan Ovrall dvlopmnt procss Dvlopmnt roadmap SYSTEM OVERVIEW Contxt and purpos Contxt Purpos Systm vision and top lvl rquirmnts Motivation High lvl rquirmnts Scop of th solution Limitations Logical architctur Ovrviw Foundations Modling Srvic Enginring Monitoring & control Rfrnc modls Intraction with xtrnal IT systms REQUIREMENT ANALYSIS SLMToolBox 1 st prototyp fdback V1.0.x vrsion history V1.0.x faturs V1.0.x Fdback V2.0.3 BETA faturs Collction & xtraction of rquirmnts Rquirmnts survy Rquirmnt mapping Slction of rquirmnts Rquirmnts licitation Rquirmnts ovrviw Rquirmnts: Srvic Modling Rquirmnts: virtualization (xtnsion of srvic modling) Rquirmnts: Srvic Enginring Rquirmnts: Srvic Govrnanc Transvrsal rquirmnts Boundaris FUNCTIONAL ANALYSIS Faturs list Covrag of SP1 Dlivrabls Actors and rols Businss Actors Domain Spcific Actors End-to-nd scnarios Scnario 1: Dsign a nw srvic within a singl ntrpris Scnario 2: Dsign & dploy a nw srvic within a VME DETAILED DESIGN Systm nvironmnt Ovrviw Intraction with othr platforms Focus: Intractions with th Gnric Srvic Dvlopmnt Platform Modling workflow and collaboration with th srvic dvlopmnt platform MSEE Consortium Dissmination: Public 3/143

4 5.2. Modlling languags dscription Intgratd graphical ditors Extrnal ditors Ovrall objct modl Modling architctur ovrviw BSM cor Mtamodl TIM cor Mtamodl S figur in: Annx 2 Dtaild dsign : 10.2 Mtamodl - TIMExtndd Actigram Star Mtamodl (BSM) Grai Grid Mtamodl (BSM) S figur in: Annx 2 Dtaild dsign : 10.3 Mtamodl Grai GridMapping: BSM GraiGrid Mapping: BSM Extndd Actigram Star Srvic modling faturs Summary of modling ditors F#1.02 UML Editors F#1.04 Improvd Extndd Actigram Star Editor F# VME orintd GRAI Grid Editor (BSM Lvl) F# VME orintd Extndd Actigram Star Editor (BSM Lvl) F# Rus VME assts dscriptions F# Publish USDL srvic dscriptions to asst rpository F# BSM2TIM Modl Transformation F# EA2BPMN Modl Transformation F#1.12 Grai Nts Modling Editor (BSM lvl) Srvic nginring faturs F#2.1 Light Businss Procss simulation F#2.2 Availability of rfrnc modls F#2.3 Srvic nginring mthodology Srvic govrnanc faturs F#3.1 KPI dscription wizards Intgration faturs F#1.03 Intgration with WP4.2 modl rpository TECHNICAL DESIGN Tchnical rquirmnts and slctd tchnologis Tchnical platform Modl manipulation Rich usr intrfacs Graphical modl diting Modl transformation Dynamic simulation of BPMN modls Modl rpository intgration Assts rpository intgration Tchnical architctur Ovrviw Tchnical moduls Application moduls Non-functional Rquirmnts covrag Graphical intrfac dscription Layout ovrviw Viw: Projct xplorr Editor: Domain spcific ditor Viw: Proprtis Wizards CONCLUSION REFERENCES ANNEX 1 COLLECTION & EXTRACTION OF REQUIREMENTS Rquirmnts survy Rquirmnts mapping ANNEX 2 DETAILED DESIGN Mta modl BSM Mtamodl - TIM Mtamodl Grai Grid Mtamodl Grai Nts Mtamodl Mapping Grai Nts / BSM / Grai Grid Mapping: MDSEA Mtamodls / In-Tangibl assts ontology BSM Mapping: MDSEA Mtamodls / In-Tangibl assts ontology - TIM 113 MSEE Consortium Dissmination: Public 4/143

5 10.8. EA Star to BPMN Collaboration Diagram Modl Mapping EA Star to BPMN Collaboration Diagram Transformation Ruls EA Star to BPMN Procss Diagram Modl Mapping EA Star to BPMN Procss Diagram Transformation Ruls ANNEX 3 TECHNOLOGY INDEPENDENT MODELS METHODOLOGICAL APPROACH Scop Background Contnt of th study Pr rquisits Limits Succss factors TIM Modling architctur TIM Modling viws TIM rprsntations (modling languags) TIM Modling lvls TIM Modling procss Modling phass Contnt of th itrations Rcommndations ANNEX 4 BIVOLINO CUSTOMIZED CONFIGURATOR TIM MODELS Scop Background Qustions to b addrssd Ovrall modling architctur Gnral architctur Scop of th analysis Us cas analysis (UML Us Cas Diagram) Actors & rols UC#1 : Crat a nw customizd configurator UC#2 : Buy a custom shirt onlin (through a spcific customizd configurator) Usr cntrd procsss (BPMN2.0 Diagram) UP#1 : Crat a nw customizd configurator UP#2 : Buy a customshirt onlin ANNEX 5 INDESIT CARE FREE WASHING SERVICE TIM MODELS Scop Background Gnral dscription / ovrviw of th INDESIT cas (BSM lvl) Gnric procss (Extndd Actigram languag) Gnral dscription of th modl (TIM lvl) UML us cas diagram UML componnt diagram of th high lvl architctur UML componnt diagram of th Mobil Wb Sit UML class diagram - Domain ntitis 143 MSEE Consortium Dissmination: Public 5/143

6 LIST OF FIGURES Figur 1 - Structur of D Figur 2 - Fatur dvlopmnt procss Figur 3 - SLMToolBox v2.0 - Dvlopmnt Roadmap Figur 4 - SLMToolBox - Contxt within th srvic lifcycl Figur 5 - Purpos: phass of th srvic lifcycl to support Figur 6 - WP1.5 - Intgration of SP1 scintific concpts Figur 7 - v1.0.x - vrsion history Figur 8 - v1.0.x - faturs Figur 9 - v BETA Faturs Figur 10 - Slctd rquirmnts Figur 11 - Rquirmnts Ovrviw Figur 12 - SLMToolBox v2.0 - Fatur List Figur 13 - Covrag of SP1 dlivrabls Figur 14 - Systm Actors Figur 15 - Dsign a nw srvic within a singl ntrpris Figur 16 - Dsign & dploy a nw srvic within a VME Figur 17 - MSEE IT systm intgration ovrviw Figur 18 - Modling workflow and collaboration with th srvic dvlopmnt platform Figur 19 - Modling architctur ovrviw Figur 20 - Mapping: BSM GraiGrid Figur 21 - Mapping: BSM Extndd Actigram Star Figur 22 - UML Editor Figur 23 - Starting and Ending Extndd Activitis Figur 24 - Start/End in EA* diagram (bfor and aftr) Figur 25 - rsourcrol of a SupportFlow Figur 31 rsourcrol in EA* diagrams (bfor and aftr) Figur 27 EA* Procss - objct diagram Figur 28 - ProcssConnctor attributs Figur 29 - Procss ProcssConnctor rlation Figur 30 - Combination of two GraiGrids (concpt) Figur 31 - Combination of two GraiGrids (mockup) Figur 32 - VME Grai Grid Gnration wizard Figur 33 - Combination of 'n' GraiGrids Figur 34 - EA* diagram in th currnt vrsion of SLMToolBox Figur 35 - EA* diagram with collaboration graphical notations Figur 36 - EA* diagram in a singl ntrpris Figur 37 - right click and choos "Gnrat collaboration diagrams" Figur 38 - Gnratd EA* collaboration diagram Figur 39 - Gnric MSEE mtamodl Figur 40 - Connct to th Assts Rpository Figur 41 Brows th assts rpository Figur 42 - EA* diagram Figur 43 - Brows asst rpository Figur 44 - EA* : rfrnc an asst as an activity rsourc Figur 45 - BsmOrganization-BsmProcss rlationship Figur 46 - EA* to Collaboration BPMN2.0 scnario Figur 47 An xcution activity Figur 48 Dcision activity Figur 49 - Grai Nts Editor - Scrn Mockup Figur 50 - Simulation Scnario - Sourc Extndd Actigram Procss Diagram Figur Simulation Scnario - Businss Procss within Bonita procss dsignr Figur 52 - Simulation Scnario - Simulation Profil Figur Simulation Scnario - Simulation launch MSEE Consortium Dissmination: Public 6/143

7 Figur 54 - Simulation Scnario - Excution tims (1) Figur 55 - Eclips nvironmnt - Hlp modul Figur 56 MSEE PI mthod Figur 57 - UML componnt diagram SLMToolBox / GSDv Intgration Figur 58 - Intgration of th modl rpository clint viw Figur 59 - Modling Environmnt - Tchnical Architctur Ovrviw Figur 60 - Modling nvironmnt - Graphical Layout Figur 61 - Rquirmnts survy Figur 62 - Rquirmnt mapping Figur 63 - BSM cor Mtamodl Figur 64 - TIM cor Mtamodl Figur 65 - Grai Grid Mtamodl (BSM) Figur 66 - GRAI Nts Languag Mtamodl Figur 67 - Mapping with BSM mtamodl & GraiGrid mtamodl Figur 68- TIM Modling viws Figur 69 - UML Us Cas Diagram - Exampl Figur 70 - BPMN - Usr cntrd procss - Exampl Figur 71 - Usr intrfac flow - Exampl Figur 72 - Usr intrfac mockup - Exampl Figur 73 - Gnral Architctur diagram - Exampl Figur 74 - Domain modl - Exampl Figur 75 - Logical architctur - Exampl Figur 76 - BPMN systm cntrd procss - Exampl Figur 77 - UML Squnc Diagram - Exampl Figur 78 - Data modl - Exampl Figur 79 - Objct modl - Exampl Figur 80 - TIM Modls dcomposition Figur 81 - BIVOLINO Modling Architctur Figur 82 - BIVOLINO Configurator Customizr - Gnral Architctur Figur 83 - UC#1 : Crat a nw customizd configurator Figur 84 - UC#2 : Buy a custom shirt onlin (through a spcific customizd configurator) 138 Figur 85 - Usr Procss : Crat a nw customizd configurator Figur 86 - Usr Procss : Buy a shirt onlin Figur 87 - Gnral dscription / ovrviw of th INDESIT cas (BSM lvl) Figur 88 - Gnric procss (Extndd Actigram languag) Figur 89 - Gnral dscription of th modl (TIM lvl) Figur 90 - UML us cas diagram Figur 91 - UML componnt diagram of th Mobil Wb Sit Figur 92 - UML class diagram - Domain ntitis MSEE Consortium Dissmination: Public 7/143

8 LIST OF TABLES Tabl 1 - WP1.1 - Srvics Modling for SLM Tabl 2 - WP1.2 - Srvics Enginring & Simulation Tabl 3 - WP1.3 - Srvics Prformanc Assssmnt & Govrnanc Tabl 4 - WP1.4 - Srvic Lif Cycl Mgmt in Virtual Factoris & Entrpriss Tabl 5 - Links with WP4.1; WP4.2; WP Tabl 6 - Rlations with prvious work of WP Tabl 7 - REQ - Provid sufficint TIM modl contnt to th GSDEV PTF Tabl 8 - REQ - Initiat TIM projcts on th basis of an xisting BSM projct data Tabl 9 - REQ - Initializ BPMN procsss from EA* diagrams Tabl 10 - REQ - Build modls (BSM/ TIM) at th lvl of th VME Tabl 11 - REQ - Modl dcision ntworks in rlation to dcision structur Tabl 12 - REQ - Rus cosystm / vm assts into srvic modls (rtriv in/tan assts). 29 Tabl 13 - REQ - Virtualiz in/tan assts through BSM or TIM modls Tabl 14 - REQ - Estimat th duration/cost/quality of th srvic dlivry Tabl 15 - REQ - Availability of rfrnc modls Tabl 16 - REQ - Srvic nginring mthodology Tabl 17 - REQ - Spcify th govrnanc systm of th organization Tabl 18 - REQ - Updatd BSM & TIM mtamodls Tabl 19 - REQ - Stor modl and diagram data in a singl cntralizd rpository Tabl 20 - SLMToolBox platform intractions Tabl 21 - Intgratd graphical ditors Tabl 22 - Extrnal ditors Tabl 23 - SLMToolBox - Modling ditors ovrviw Tabl 24 - Mapping BSM mtamodl / TIM mtamodl Tabl 25 - GRAI Nts - Entity Rols Tabl 26 - GRAI Nts - Rfrnc oprators Tabl 27 - Evaluation of Businss Procss Simulation Tools Tabl 28 - Modling Environmnt - Non-functional Rquirmnts covrag Tabl 29 - Mapping : BSM Cor / In-Tangibl assts ontology Tabl 30 - Mapping : TIM Cor / In-Tangibl assts ontology Tabl 31 - EA* 2 BPMN - Transformation Mapping (Collaboration Diagram) Tabl 32 - EA* 2 BPMN - Transformation Mapping (Collaboration Diagram) Tabl 33 - Input documnts Tabl 34 - Foundational documnts Tabl 35 - Qustions to b addrssd Tabl 36 - Scop of th analysis Tabl 37 - Actors & rols MSEE Consortium Dissmination: Public 8/143

9 ACRONYMS API: ATL: BPMN: BSM: CASE: CDO: EEF: EMF: GEF: GMF: GRAI: GUI: IDEF: KPI: MDSEA: OMG: QVT: SLA: SLM: TIM: TSM: UML: USDL: WPx: XMI: XML: Application Programing Intrfac ATL Transformation Languag Businss Procss Modl Notation Businss Srvic Modl Computr Aidd Systm Enginring Connctd Data Objcts Extndd Editing Framwork Eclips Modling Framwork Graphical Editing Framwork Graphical Modling Framwork Graphs with Rsults and Activitis Intrrlatd Graphical Usr Intrfac Intgratd Dfinition (Mthod) Ky Primary Indicator Modl Drivn Srvic Enginring Architctur Objct Managmnt Group Qury Viw Transformation (languag) Srvic Lvl Agrmnt Srvic Systm Lifcycl Tchnological Indpndnt Modl Tchnological Spcific Modl Unifid Modling Languag Univrsal Srvic Dscription Languag MSEE Work Packag x XML Mtadata Intrchang Extnsibl Markup Languag MSEE Consortium Dissmination: Public 9/143

10 Excutiv Summary Th Work Packag 1.5 of th MSEE projct aims at dsigning and dvloping a st of softwar tools, which will support th srvic nginring activitis for singl ntrpriss and virtual manufacturing ntrpriss. As ths tools will provid support for intrrlatd activitis, in particular: srvic modling, srvic nginring and srvic govrnanc, thy ar proposd in th form of a cohrnt packag, namly th Srvic Lifcycl Managmnt Tool Box. This dlivrabl rports on th scond vrsion of th spcification and tchnical dsign of th Srvic Lifcycl Managmnt Toolbox. It stands on th basis of th first vrsion of th softwar rlasd during th first cycl of th MSEE projct (spcification & dsign: M9; 1 st prototyp implmntation: M12) in which wr proposd th tchnical platform (basd on Eclips tchnologis) and a first st of modling faturs. Th main challng of th scond vrsion of th softwar is to xtnd its faturs toward srvic govrnanc and srvic nginring mthodology. Th first chaptr of th documnt introducs th numrous rlations of th softwar nginring work rportd in this dlivrabl with scintific outcoms of th MSEE projct and th connctions with othr tchnical work packags of th projct, such as th IT architctur of th MSEE IT Platform. Finally, th incrmntal mthodological approach for th dvlopmnt activitis is rcalld and a dvlopmnt roadmap is proposd. Th scond chaptr brings an ovrviw on th systm; and stablishs a clar distinction btwn th contxt in which it is usd; and th srvic lifcycl phass it aims at prparing. Th vision and scop of th dvlopmnt is assssd as wll as a cohrnt concptual architctur, covring ths thr major pillars: srvic modling; srvic nginring; srvic govrnanc. Third and fourth chaptrs aim a driving a prcis list of faturs to b implmntd in th final vrsion of th systm. Th procss of rquirmnt collction and licitation procss and outcoms ar xplaind and rfrncs ar mad to xisting usr fdback concrning th prvious vrsions of th softwar prototyp. Two major nd-to-nd usag scnarios ar laboratd: dsign a nw srvic within a singl ntrpris ; dsign a nw srvic within a virtual ntrpris. Th fifth chaptr is th cor of th documnt. It contains th whol spcification of th faturs to b dvlopd in th scond vrsion of th SLMToolBox. Ths faturs ar organizd by domains (in rlation with th concptual architctur xposd in th scond chaptr of th documnt). This chaptr aims at constituting rfrnc dvlopmnt bluprint documntation, giving th right lvl of information to th dvlopmnt tam, in charg of th implmntation of th scond vrsion of th softwar. Intgration aspcts (in connction with WP4.5 work) ar also takn into account for th spcifications of th softwar. Th sixth chaptr rcalls th major tchnological componnts as wll as th tchnical architctur of th softwar platform; in ordr to support th implmntation of th faturs dtaild in th prvious sction of th documnt. Finally, th svnth chaptr concluds th dlivrabl with a synthsis of th main modifications and volutions targtd in th scond vrsion of th SLMToolBox ; and opn prspctivs for futur dvlopmnts outsid of th MSEE projct fram. MSEE Consortium Dissmination: Public 10/143

11 1. Introduction 1.1. Objctiv of th dlivrabl Th main objctiv of WP15 is to dsign and dvlop a softwar toolst calld th Srvic Lifcycl Managmnt Toolbox (MSEE Projct - Dscription of Work, 2011). D15.3 provids a summary of th main rquirmnts drivd from othr work packags rlatd to th dfinition of srvic concpts, modls and mthodologis. An analysis and a rfinmnt of ths rquirmnts will b providd through th dfinition of th systm faturs. On this basis, th main functionalitis of th systm will b dsignd, with th support of a dtaild dscription of th mor critical us cass of th systm. Thrfor, th following objctivs hav bn dtrmind for th dlivrabl: Synthsis and rfinmnt of softwar tool orintd rquirmnts in th domain of srvic nginring Idntification and prioritization of th most important faturs to b implmntd in th scond vrsion of th softwar Dtaild spcification and dsign for ach faturs From th tchnical prspctiv, th approach is to build ths faturs upon th tchnical platform (clips basd) which was introducd and dscribd within th prvious vrsion of this dlivrabl (D15.2: Spcifications and Dsign of Srvic Lifcycl Managmnt ToolBox) 1.2. Structur of th dlivrabl Th structur of th dlivrabl is groupd into four major blocks, according to th objctivs dscribd in sction 1.1: Figur 1 - Structur of D15.3 Block A has th function to summariz th vision of th systm and dpict an ovrviw of th concpts and top lvl rquirmnts to b addrssd by th softwar. MSEE Consortium Dissmination: Public 11/143

12 Block B is prsnting th licitation procss for rquirmnt xtraction, analysis; as wll as th outcoms of th licitation phas. Thn, a brif functional analysis is proposd with th summary of systm faturs and to cor usag scnarios. Block C lays out th dtaild spcification of th functionalitis to b dvlopd, as wll as th tchnical componnts of th softwar. Block D concluds th dlivrabl with a synthsis of th main outcoms of th spcification and dsign tasks Rlations with othr work packags and dlivrabls Links with WP1.1, WP1.2, WP1.3 and WP1.4 Th SLMToolBox is xpctd to provid a st of softwar tools to support th first phass of srvic nginring, dfind in th srvitization procss stps dscribd in (D Srvic concpts, modls and mthod: Modl Drivn Srvic Enginring, 2012). To rach this goal, w can idntify thr cor functional domains in MSEE which must b covrd by appropriat softwar tools: Ths softwar rsults will b xprimntd along th four tst cass of th MSEE projct and through th two itration cycls of th projct. This toolst is mant to implmnt a subst of th thortical and mthodological concpts formalizd by othr SP1 WPs, rspctivly: WP1.1: Srvics Modling for SLM WP1.2: Srvics Enginring & Simulation WP1.3: Srvics Prformanc Assssmnt & Govrnanc Not: som dlivrabls rfrncd in th following tabls ar plannd for M18 or latr (s * ). Th dvlopmnt procss of WP1.5 softwar covrs this issu through an itrativ approach; which will allow intgrating furthr rquirmnts during th implmntation phas. This will b sustaind with th rlas of intrmdiat vrsion and a continuous collaboration with scintific partnrs through dlivrabl rviws and workshops WP1.1 - Srvics Modling for SLM # Titl D11.1 Srvic concpts, modls, mthod at CIM-PIM-PSM lvl D11.2 Srvic concpts, modls, mthod at CIM-PIM-PSM lvl D11.3 MDA/MDI Modl Transformation D11.4 MDA/MDI Modl Transformation Issu dat M4 M12 M8 M15 Rlation MDSEA modlling architctur ; modlling languag ; srvic modlling mthodology Rfinmnt of MDSEA srvic modlling mthodology and architctur - basd on us cas fdback (BIVOLINO analysis at BSM lvl) Modl transformation ruls from Businss Srvic Modl (BSM= lvl to Tchnology Indpndnt Modl lvl (D Srvic concpts, modls and mthod: Modl Drivn Srvic Enginring, 2012, p. 26). To b implmntd by th SLMToolBox Modl transformation spcification (BSM to TIM modls ; Extndd Actigram Star to BPMN procss modls) Prspctivs for th intgration of ontology support (smantic nrichmnt) in th modling MSEE Consortium Dissmination: Public 12/143

13 D11.5 ; D11.6 MSEE architctur for Srvic modlling M12 ; M24 (*) architctur. Dscribs a collaborativ architctur and tools for businss-it intraction and distributd dcision making in virtual factoris and ntrpriss. Tabl 1 - WP1.1 - Srvics Modling for SLM WP1.2 - Srvics Enginring & Simulation # Titl D12.1 Rport about Srvic Scnarios D12.3 ; Srvic nginring D12.4 mthodology for product-rlatd srvics Issu dat M4 M6 ; M18 Rlation Cor concpts on srvic nginring and srvitization ar xplaind. Approach on srvic nginring for productrlatd srvics is prsntd. Tabl 2 - WP1.2 - Srvics Enginring & Simulation WP1.3 - Srvics Prformanc Assssmnt & Govrnanc # Titl D13.1 KPIs and SLAs for cosystm govrnanc D13.2 KPIs and SLAs for cosystm govrnanc D13.3 Rport on Rol Modls in th Intgratd Srvic Lifcycl Mgmt Modl D13.5 ; Srvic oprations D13.6 monitoring and control toolst Issu dat Rlation M6 Concptual framwork for prformanc masurmnt dsign M15 Cor concpts on ECOGRAI and dscription of MSEE PI Mthod for srvic govrnanc dsign. M9 Mthodology and spcific rquirmnts for managing KPIs (Fitz-Gibbon, 1990) and SLAs (An outlin of th cor lmnts of an SLA) in virtual factoris. M12 ; Provid a dscription of th tools rquird to M24(*) dynamically us th KPIs and SLAs dfind in th rfrnc framwork for innovation cosystms (WP2.1) Tabl 3 - WP1.3 - Srvics Prformanc Assssmnt & Govrnanc WP1.4 - Srvic Lif Cycl Mgmt in Virtual Factoris & Entrpriss To nabl th transition from th concpts to th dsign and implmntation of th corrsponding usabl softwar tools, WP1.4 has th rol to dlivr an intgration of th rsults of work packags 1.1, 1.2 and 1.3 undr th form of a functional spcification. # Titl D14.1 ; D14.2 D14.5 ; D14.6 Intgratd Srvic Lifcycl Managmnt Modl Rport on th Approach on th Customization of Srvic Lifcycl Mgmt Issu dat M12 ; M18 M18 ; M24 (*) Rlation Dfinition of th MSEE SLM framwork (phass, rols, mthods & tools) Dfinition of a mthodological srvitization framwork for virtual manufacturing ntrpriss. Tabl 4 - WP1.4 - Srvic Lif Cycl Mgmt in Virtual Factoris & Entrpriss MSEE Consortium Dissmination: Public 13/143

14 Links with WP4.1; WP4.2; WP4.5 Th SLMToolBox is rcognizd as a softwar modul of th ovrall MSEE IT systm architctur. Its intgration within th gnral systm and th spcific intraction with third party systms (.g.: gnric srvic dvlopmnt platform) ar takn into account for th spcification and dsign of th SLMToolBox. In particular, th spcification and dsign of th IEP (Innovation Ecosystm Platform) and Dvlopmnt Platform provid guidlins in ordr to anticipat th intgration of th SLMToolBox with both of ths platforms. # Titl D41.1 MSEE Srvic-Systm Functional and Modular Architctur D26.2 Innovation Ecosystm platform spcifications and architctur D42.1 Gnric Srvic Dvlopmnt Platform spcifications and architctur D45.1 MSEE Srvic-Systm Intgratd Issu dat M6 M18 M12 M18 Rlation Dfin th architctural guidlins to comply with, in ordr to dsign th rlvant intgration btwn th tchnical platforms and moduls for th MSEE IT Systms. D15.2 taks this dlivrabl in account for th logical dsign and th choics of tchnologis of th SLMToolBox. Spcify th main softwar moduls of th IEP, provids guidlins for th intgration of third party MSEE tools. Spcify th main softwar componnts of th Srvic Dvlopmnt Platform, provids guidlins for th intgration of third party MSEE tools. This dlivrabl provids th first vrsion of th intgratd MSEE IT systm. Intgration constraints ar takn into account for th spcification and dsign of th scond vrsion of th SLMToolBox Tabl 5 - Links with WP4.1; WP4.2; WP Rlations with prvious work of WP1.5 Th scond vrsion of th SLMToolBox which is th scop of this dlivrabl is an volution of th first prototyp dlivrd at M12. Thrfor, th following dlivrabls ar considrd as th functional and tchnical basis for th nw spcification and dsign documnt: # Titl D15.1 Mthodologis and Tools for SLM componnts dvlopmnt D15.2 Spcifications and Dsign of SLM Platform D15.4 Dvlopmnt of th SLM platform Issu dat M9 Rlation Provids th mthodological foundations for th ovrall dvlopmnt procss instantiatd to dsign and dlivr th rsulting softwar. M9 Dscribs th functionalitis of th first prototyp and th dsign stratgy concrning th slction of th tchnical platform and its customization for th nds of th projct. M12 Th factshts associatd to th working prototyp dlivrd at M12 provids th rlvant tchnical and usr orintd information, ndd for th xploitation of th prototyp implmntation. Tabl 6 - Rlations with prvious work of WP1.5 MSEE Consortium Dissmination: Public 14/143

15 1.4. Mthodology & Projct plan Ovrall dvlopmnt procss Th dvlopmnt procss of th SLMToolBox is drivn by th implmntation of faturs, from thir idntification during th rquirmnt analysis phas to thir intgration and validation within WP4.5 & SP6 activitis. SLMToolBox Faturs Accptd Spcifid Idntifid Rquirmnt Analysis Inputs : WP11 ; WP12 ; WP13 ; WP14 Tch. Constraints : WP41 ; WP42 ; WP26 End Usr Scnarios : WP52 ; WP6.x Spcification & Dsign (D15.3) Rquirmnts Analysis : Mapping & Priorization Functional Analysis + Dsign : Pr us cas Tchnical Dsign : Tchnologis ; Prototyping Dsignd Dvlopmnt (D15.5) SCRUM Dvlopmnt Framwork Implmntd Validatd Intgration + Validation (WP4.5 + SP6) 21 Figur 2 - Fatur dvlopmnt procss Th figur dpicts th gnral procss for th implmntation of softwar faturs. W can notic that th main inputs (scintific; tchnical and usr orintd) ar collctd at th arly stag of th dvlopmnt procss. This work has bn prformd through thigh collaboration with th rsponsibl of th appropriat work packags, through th analysis of th rsulting dlivrabls, and svral workshop sssions: 22-23/01/2013 : SP3-SP4 Tchnical : WP42/WP15 workshop 22-25/01/2013 : Intgration among SP1, SP2 and : SLMToolBox prsntation 06-08/02/2013 : MSEE Gnral : SP1 Workshop, SP1-SP2 Workshop 28/02 01/03/2013 : SP1 SLMToolBox v2.0 rquirmnts & Spcification Wkly Tlco: SP4 architctur, intgration, tchnical validation Th D15.3 acts as a major milston as it aims at dfining th scop of th faturs to b implmntd and th dsign of th rlatd functionalitis. Thn, th dvlopmnt phas, starting at M18, is sustaind by an itrativ procss (dscribd in th D15.1) rlying on th scrum mthodological framwork. Such an approach aims at priodically dlivr working intrmdiat vrsions of th softwar; so that th softwar is rgularly assssd by usrs. MSEE Consortium Dissmination: Public 15/143

16 Finally, th rsulting softwar is intgratd with othr MSEE IT tools within WP4.5 activitis. Th rsulting systm will b xprincd by th nd usrs in th fram of SP6, through pilot us cass Dvlopmnt roadmap Th following figur givs an ovrviw of th rlas planning for th dvlopmnt phas of th scond vrsion of th SLMToolBox from M18 until M24. Figur 3 - SLMToolBox v2.0 - Dvlopmnt Roadmap Th undrlying approach is to dlivr rlvant intrmdiat rlass, so that th softwar can b constantly assssd by nd usrs and th scop of th nxt rlas is adjustd to th usrs nds. This approach will nabl to rassss th scop of th functionalitis to b dlivrd in th final vrsion of th SLMToolBox; thanks to a tight collaboration with othr scintific partnrs (SP1) and tchnical partnrs (SP4), this procss will nabl th intgration of MSEE projct outcoms byond M18. MSEE Consortium Dissmination: Public 16/143

17 2. Systm ovrviw 2.1. Contxt and purpos Th objctivs of th tools dvlopd in WP1.5 is to support th phass rlatd to srvic nginring, within th srvic lifcycl modl (D Srvic concpts, modls and mthod: Modl Drivn Srvic Enginring; Srvic Systm Lif cycl Managmnt (SLM)). It is important to mak a clar distinction btwn 1) th contxt in which th SLMToolBox is usd and 2) th phass of th srvic lifcycl it aims to support Contxt Th SLMToolBox will b usd in th fram of ntrpris projcts which aim at dvloping a nw srvic or an improvmnt on a srvic, within an organization (composd ithr by on singl ntrpris; or by svral partnrs, in this cas: a virtual manufacturing ntrpris). Th tools of WP1.5 will thn b usd at th stag of rquirmnt and dsign of th srvic nginring procss Purpos Figur 4 - SLMToolBox - Contxt within th srvic lifcycl During th rquirmnt and dsign stag of th srvic, th tools of WP1.5 will b usd to dscrib in dtails how th srvic will bhav in th opration phas of its lifcycl. As a complmnt, it is possibl to also dscrib th nxt phass of th srvic in its lifcycl: How (with which procss /rsourcs / tools) will th srvic b dsignd; implmntd? How th srvic will b dcommissiond at th nd of its lifcycl? Figur 5 - Purpos: phass of th srvic lifcycl to support MSEE Consortium Dissmination: Public 17/143

18 2.2. Systm vision and top lvl rquirmnts Motivation Th main motivation for th dvlopmnt of th SLMToolBox could b formulatd as th following: no rfrnc tool for dsigning and managing srvic innovation projcts (Srvitization procss) currntly xists. It affcts Europan Manufacturrs willing to invst on srvic innovation: as thy currntly hav to rly on various gnric tools, mostly orintd on «businss procss managmnt» and «softwar nginring» domain High lvl rquirmnts To crat or modify a srvic within an organization (ithr a singl ntrpris or a virtual manufacturing ntrpris); th stak holdrs nd: To spcify, valuat, communicat and dsign th systm supporting th srvic and its lifcycl Appropriat formalisms (domain spcific & asy to rad) Productiv mans ; Introprabl formats To optimiz th dvlopmnt of th IT part of a srvic systm (xampl: an onlin shirt configurator); th dvlopmnt tams nd: To laborat a solution which is dirctly connctd to th initial rquirmnts (.g. : intgrats with th businss procsss of th company) Concntrat on tchnical activitis (.g.: tchnical dsign, implmntation ) Scop of th solution An intgratd modling tool, ddicatd to manufacturing srvics lifcycl managmnt. It will allow: To tak bnfit of a modl basd architctur: syntactic validation; transformation; xcution; Maintain th cohrnc through th whol nginring procss - from Businss rquirmnts to IT implmntation (modling) Anticipat / simulat th rsult of th srvic (nginring) Dsign th govrnanc of th srvic (monitoring & control) Unlik othr CASE tools (.g.: UML modling Tools; Businss Procss Managmnt Tools; ): It will guid th dvlopmnt of nw srvics and srvic systms in a cohrnt approach, from th businss prspctiv, to th dsign prspctiv Limitations Th SLMToolBox dos not provid support for: Implmntation / Coding softwar componnts Th implmntation of Businss Intllignc rport Monitoring th xcution of srvics Th flxibility of th modlling architctur is limitd to th instantiation of th mtamodls which ar linkd to th softwar at th dvlopmnt tim. It mans that th structur and th tmplat availabl to modl srvics ar static. Thrfor, a modification on th modlling languags and mtamodls will ncssitat nw coding activitis through a nw dvlopmnt phas. MSEE Consortium Dissmination: Public 18/143

19 2.3. Logical architctur Ovrviw Th following figur dpicts th logical architctur of th tools proposd by WP1.5. It clarly dpicts th intgration of th outcoms of SP1 scintific work packags Foundations Figur 6 - WP1.5 - Intgration of SP1 scintific concpts Th foundation of th SLMToolBox is basd on th modling architctur laboratd within WP1.1. This modl cntric approach provids th appropriat structur for laborating srvic rquirmnt and dsign thanks to a st of spcific mtamodls ddicatd to th domain of manufacturing srvics Modling Th first pillar of th architctur brings a st of modling ditors, nabling th usr to laborat structurd and graphical dscriptions of th srvic and its aspcts (IT ; Human ; Physical Mans) at th businss lvl (BSM : Businss Srvic Modls) and th dsign lvl (TIM : Tchnology Indpndnt Modls). As a complmnt, modl transformation facilitis will lvrag introprability of th modls and nforc consistnc btwn th Businss rquirmnts of th srvic and its dsign at TIM lvl Srvic Enginring Th scond pillar aims at sustaining th modling activitis thanks to a mthodological support. Guidanc will b providd to th usr through th modling activitis of th srvic via an appropriat srvic nginring mthodology, drivd from WP1.2. Bsids, som support will b providd to assss th ovrall quality of th srvic at high lvl at dsign tim, thanks to appropriat tools Monitoring & control Th third pillar will support th dfinition of th govrnanc of th srvic systm, which will b thn implmntd by th organization to continuously assss th prformanc of th srvic, according to th thr dcision lvls of th organization (Stratgic; Tactic; Oprational), its functions and its dtaild objctivs. MSEE Consortium Dissmination: Public 19/143

20 Rfrnc modls Finally, a st of rfrnc modls will b laboratd on top of this tooling support. Such xampl rfrnc modls aim at providing matrial to nw srvic nginring projcts Intraction with xtrnal IT systms As rflctd in th logical architctur ovrviw, th SLMToolBox intracts with two xtrnal systms. (WP4.2) Modl Rpository modul: th modls laboratd with th SLMToolBox ar stord (publishd and rtrivd) in th modl rpository modul. Which rsponsibility is to guarant th accss to srvic modling projcts (at BSM; TIM and TSM lvls) btwn th platforms of th ovrall MSEE IT systm, and to manag th rlvant accss policis. Furthrmor, this cntralizd rpository modul will nabl svral instancs of th SLMToolBox to xchang modling projcts. (WP2.6) Assts Rpository modul: this rpository is rsponsibl for storing and sharing th dscription of virtualizd assts btwn svral mmbrs of a Manufacturing Virtual Entrpris (VME). In this spcification documnt, w propos a st of faturs, aiming at 1) rfrncing xisting assts within srvic modls ; 2) nabling th usr laborat and publish assts dscriptions from th SLMToolBox modling ditors. MSEE Consortium Dissmination: Public 20/143

21 3. Rquirmnt analysis In this part of th documnt, w will giv a dscription of rquirmnts collctd from xisting and rlvant dlivrabls, plus som high lvl rquirmnts idntifid during prvious mtings or workshops rgarding th srvitization concpts, in th fram of th MSEE projct. Th purpos of this sction is to stand as th starting point for furthr analysis, toward th implmntation of th rlvant softwar tools SLMToolBox 1 st prototyp fdback V1.0.x vrsion history Oct V1.0 Initial Architctur - Tch. Platform - Modl Rpository BSM Editors - Cor Tmplats ; EA* ; GraiGrid TIM Editors - Cor Tmplats Nov V1.1 TIM Editors - BPMN Modlr Oct V2.0 Modling - Monitoring & control - Enginring - Intgration - Figur 7 - v1.0.x - vrsion history V1.0.x faturs DOMAINS BSM Modls Srvic Systm Modling TIM Modls Usr Orintd FEATURES Edit BSM cor modls contnt (tmplats) MDSEA Mtamodls Edit TIM cor modls contnt (tmplats) Edit Grai Grid diagrams updat BSM data accordingly Crat modling projcts Edit BPMN2.0 Procss Modls Edit Extndd Actigram Star Diagrams updat TIM data accordingly Intgration FEATURES Stor modl data in a ddicatd rpository Provid OMG compliant BPMN2.0 modls Non Functional FEATURES Modular Architctur (multi ditor) basd on Eclips Figur 8 - v1.0.x - faturs MSEE Consortium Dissmination: Public 21/143

22 V1.0.x Fdback Modls for BIVOLINO us cas wr laboratd succssfully with th modlling tools at BSM and TIM lvl (D Srvic concpts, modls and mthod Modl Drivn Srvic Enginring : 10.Application of th Modlling languags to a pilot cas of MSEE ; Annx : BIVOLINO Customizd configurator TIM modls) Modls for INDESIT wr laboratd at th TIM lvl with th SLMToolBox (Annx : INDESIT - Car fr washing srvic TIM modls ) A modlling mthodology has bn proposd at th TIM lvl, in cohrnc with th mthod dvlopd at th BSM lvl. A lightr installation configuration procss has bn claimd by usrs ; a bta rlas of th SLMToolBox wr issud with and mbddd databas ngin for th modl rpository modul, which avoidd th nd for a pr-configurd RDBS (s V2.0.3 BETA faturs) Th nd for a UML ditor has bn rcognizd as critical in ordr to nabl th intgration with th Gnric Srvic Dvlopmnt platform RDBS (s V2.0.3 BETA faturs) V2.0.3 BETA faturs An intrmdiat rlas of th SLMToolBox was issud at M17, in ordr to 1) provid a mor stabl modling nvironmnt 2) as th installation procss of th tool 3) provid UML modling faturs. DOMAINS BSM Modls Srvic Systm Modling TIM Modls Usr Orintd FEATURES Edit BSM cor modls contnt (tmplats) MDSEA Mtamodls Edit TIM cor modls contnt (tmplats) Edit Grai Grid diagrams updat BSM data accordingly Crat modling projcts Edit BPMN2.0 Procss Modls Edit Extndd Actigram Star Diagrams updat TIM data accordingly Edit UML Modls (class diagrams ; us cas ; ) Intgration FEATURES Stor modl data in a ddicatd rpository «Light» installation profil Provid OMG compliant BPMN2.0 modls Non Functional FEATURES Modular Architctur (multi ditor) basd on Eclips Major Bug Fixs Figur 9 - v BETA Faturs MSEE Consortium Dissmination: Public 22/143

23 3.2. Collction & xtraction of rquirmnts This sction brifly xposs th procss which rsultd in th idntification of prcis softwar faturs, to b implmntd in th scond vrsion of th SLMToolBox. This analysis tchniqu was inspird by th tchniqu of Usr Story Mapping by Jff Patton 1 which aims at arranging usr storis into a usful modl to hlp undrstand th functionality of th systm, idntify hols and omissions in your backlog, and ffctivly plan holistic rlass that dlivry valu to usrs and businss with ach rlas. In our cas, w start this analysis procss at an uppr lvl, w aim at driving softwar faturs mostly from scintific concpts and assss thir rlativ valu, considring 1) thir potntial impact on th projct; 2) th tchnical fasibility or th ndd ffort to provid an implmntation on th basis of th SLMToolBox tchnical platform Rquirmnts survy Th first phas of th procss was to analyss SP1 and SP4 dlivrabls (at M16) ; xtract and collct all th rquirmnts which could b rlatd to th SLM tools in WP1.5 ; and to map ths rquirmnts along thr axis : Domains : which ar quivalnt to th thr cor pillars which support th concptual architctur of th SLMToolBox (srvic modlling ; srvic govrnanc ; srvic nginring) Catgoris : which distinguish th drivr of th rquirmnt, ithr : usr orintd, rlatd to intgration purpos, or non-functional Th rsult of this first survy and classification is a holistic viw of possibl faturs, which could b scopd in th scond vrsion of th SLMToolBox, undr th form of a visual map. S figur in: Annx 1 Collction & xtraction of rquirmnts : 9.1Rquirmnts survy Rquirmnt mapping Th scond phas consists in mapping th rquirmnts prviously collctd along two axs: (horizontally) thir potntial impact on th projct (vrtically) th tchnical fasibility or th ndd ffort to provid an implmntation on th basis of th SLMToolBox tchnical platform S figur in: Annx 1 Collction & xtraction of rquirmnts : 9.2 Rquirmnts mapping 1 MSEE Consortium Dissmination: Public 23/143

24 Slction of rquirmnts This last phas of th rquirmnt collction and xtraction procss consistd in isolating th most important / fasibl rquirmnts to b satisfid by th scond vrsion of th SLMToolBox. Figur 10 - Slctd rquirmnts MSEE Consortium Dissmination: Public 24/143

25 3.3. Rquirmnts licitation Rquirmnts ovrviw Rquirmnts: Srvic Modling Figur 11 - Rquirmnts Ovrviw Th following tabls list th main functional rquirmnts idntifid rgarding th modling tools of th SLMToolBox. From ach rquirmnt a list of softwar faturs is xtractd, it will thn srv as a basis for th spcification and dsign of th functionalitis to b implmntd in th scond vrsion of th SLMToolBox Provid sufficint TIM modl contnt to th GSDEV PTF ID REQ1.1 Domain Srvic modling Importanc MUST Goal To nabl th implmntation of th srvic systm, in cohrnc with th businss rquirmnts Impact To prov that th collaboration btwn th SLMToolBox and th Dvlopmnt Platform will structur and acclrat th implmntation of IT componnts, to support th dploymnt of a nw srvic within a VME Dscription A «srvic nginr» will dsign graphical modls, with th hlp of th following formalisms, in ordr to spcify in dtails th IT artifacts which ar ncssitatd to dlivr th srvic and how ths artifacts will intracts with humans and othr artifacts and along which ruls. TIM cor tmplats : to dscrib gnric information rlatd to th srvic, and which will hlp th implmntation of th srvic systm UML Class Diagrams : to dscrib th data objcts which will b manipulatd MSEE Consortium Dissmination: Public 25/143

26 Scnarios Nonfunctional constraints Faturs: UML Squnc Diagrams : to dscrib th intractions btwn th subcomponnts of th IT assts and th associatd ruls UML Us Cas Diagrams : to dscrib th diffrnt usr rols and thir intractions with th systm to b implmntd BPMN Diagram : to dscrib th squnc flow of tasks (ithr manual or automatic) which will support th procsss Th common objcts of th diagrams ar linkd with th contnt of th «TIM Cor» modl. Thanks to ths modling facilitis, th nginr will b abl to prform th right choics for th dsign of th srvic systm and can xprss its spcifications in a standard structurd and clar syntax, in cohrnc with th ovrall srvic systm modl. As an IT architct, I want to spcify th ndd IT componnts and procsss to dlivr an IT srvic, so that th systm will fulfill th businss rquirmnts and th dvlopmnt tam can start th implmntation with clar guid lins Th TIM modls (both modl data and graphical rprsntation) will b publishd to th Modl Rpository modul, so that th dvlopmnt platform can samlssly rtriv ths modls to nrich thm (TSM) and prform th coding activitis Th tchnical format of UML modls must conform to th XMI syntax Tabl 7 - REQ - Provid sufficint TIM modl contnt to th GSDEV PTF # UML Editor (for BSM and TIM modlling projcts) Initiat TIM projcts on th basis of an xisting BSM projct data ID 1.2 Domain Srvic modling Importanc MUST Goal Enforc cohrnc btwn dsign & rquirmnt, incras productivity : Initializ gnric srvic information TIM lvl, from xisting BSM modl data Impact Automatically support th cohrnc btwn th BSM and TIM modling lvls. Dscription Th srvic systm modling s framwork dfins thr abstraction lvls: BSM, TIM, and TSM. Data at ths lvls can shar som similaritis but with diffrnt dtails and spcification lvls. Scnarios A businss usr wants to crat a TIM lvl taking into considration th data dvlopd in a spcific BSM projct. With a click h can chos which BSM projct to initializ his TIM projct. Nonfunctional - constraints Faturs: Tabl 8 - REQ - Initiat TIM projcts on th basis of an xisting BSM projct data # BSM2TIM Modl Transformation Initializ BPMN procsss from EA* diagrams ID 1.3 Domain Srvic modling Importanc MUST MSEE Consortium Dissmination: Public 26/143

27 Goal Impact Dscription Scnarios Nonfunctional constraints Faturs: Enforc cohrnc btwn dsign & rquirmnt, incras productivity : Initializ procss spcifications at TIM lvl, from procss modls at BSM lvl Automatically support th cohrnc btwn th BSM and TIM modling lvls. Provid introprability btwn Extndd Actigram Star spcific procss modling languag and standard procss modling languag (BPMN2.0) Th usr will tak advantag of what was modld at BSM lvl by othr usrs in ordr to crat his propr modl at TIM lvl without th nd to rcrat th modl from scratch. This transformation is basd on a mapping which rsultd from th analysis of th two Modling languags to find th connctions btwn thm. Onc I achivd a procss modl at BSM with xtndd Actigram star, I can opn a TIM projct and automatically initializ a BPMN ( procss or collaboration ) diagram, basd on this xtndd Actigram star procss modl. Th targt format must b compliant with th OMG s BPMN2.0 spcification in ordr to b compatibl with th nds of othr Ecosystm ntitis. Tabl 9 - REQ - Initializ BPMN procsss from EA* diagrams # Improvd Extndd Actigram Star Editor (v4.0) # EA*2BPMN Modl Transformation Build modls (BSM/ TIM) at th lvl of th VME ID 1.4 Domain Srvic modling Importanc SHOULD Goal To dsign th srvic systm involving svral partnrs, forming a virtual organization, known as a Virtual Manufacturing Entrpris Impact To dsign innovativ and ffctiv srvics in th contxt of virtual manufacturing ntrpriss through modling tchniqus Dscription A businss usr will : Modl th collaborativ procsss, involving svral partnrs of th VME Dfin th dcision / govrnanc systm of th srvic, dlivrd by th VME according to th rol of ach partnr Scnarios I can modl a procss involving svral singl ntrpris and rprsnting which organization is rsponsibl for which activity I can modl a dcision structur (GRAI Grid) and rprsnting th collaboration btwn th diffrnt functions of th partnrs Nonfunctional - constraints Faturs: Tabl 10 - REQ - Build modls (BSM/ TIM) at th lvl of th VME # Updatd BSM & TIM tmplats mtamodls # VME orintd GRAI Grid Editor (BSM Lvl) # VME orintd Extndd Actigram Star Editor (BSM Lvl) MSEE Consortium Dissmination: Public 27/143

28 Modl dcision ntworks in rlation to dcision structur ID 1.5 Domain Srvic modling Importanc Could Goal To xtnd th dscription of dcision structur to th lvl of dcision ntwork Impact Provid an laboratd modling tool for th spcification of dcision structurs, basd on grai nts formalism (G. Doumingts, 1998) Dscription Linkd to th concptual rfrnc modl of a dcision cntr, GRAI ntworks aim a dscribing in dtails th activitis rlatd to dcision cntrs idntifid in th dcision structurs (GRAI Grids) Scnarios In ordr to dsign th piloting systm of th organization, I nd to bring an mphasis on th triggrs, rsults and supports which charactriz th activitis, within a dcision cntr. Nonfunctional constraints Th modlling ditor must intgrat with th xisting BSM modlling ditors of th SLMToolBox Faturs: Tabl 11 - REQ - Modl dcision ntworks in rlation to dcision structur # Grai Nts Modlling Editor (BSM lvl) Rquirmnts: virtualization (xtnsion of srvic modling) Th virtualization rquirmnts & faturs ar considrd as a possibl xtnsion of th srvic modling capabilitis of th SLMToolBox; in ordr to link th srvic modling activitis with th virtualization procss, laboratd in SP Rus cosystm / vm assts into srvic modls (rtriv in/tan assts) ID 2.1 Domain Srvic modling - Virtualization Importanc Could Goal To bnfit from th xisting assts of th cosystm in ordr to dsign a nw srvic systm involving xisting and availabl rsourcs from my partnrs within th cosystm Impact To dmonstrat th valu of «Virtualizd Assts» of th Ecosystm to hlp a VME to dsign a nw srvic through modling tools Dscription A «srvic managr» wants to dsign a nw srvic or to modify an xisting srvic which rquirs th participation of on or svral partnrs in th dlivry procss - according to th comptnc and xprtis of ths partnrs. To hav an ovrviw of th intractions and to valuat th impact of this collaboration, th «srvic managr» wants to dfin th ovrall procss and crtain sub procsss which will consum srvics dlivrd by third party. To do this : Th srvic managr sarch for availabl srvics in th cosystm, corrsponding to crtain critria s (.g.: domain; pric; dlivry tim; ) and compar thm. Ths availabl srvics ar rprsntd as two catgoris of «assts» (ithr tangibl or intangibl) Th usr slcts th most appropriat srvic to involv in its procss or sub-procss Th usr includs a rprsntation of th srvic h has slctd as a particular stp in th procss or as a rsourc, contributing to a particular stp. MSEE Consortium Dissmination: Public 28/143

29 Scnarios As th srvic managr of Bivolino, I can sarch and slct th appropriat cutting machins / srvics of my partnrs and includ thm into th dscription of th dlivry procss of my «custom shirts» srvic, so that I can dsign th most fficint organization to dlivr my srvic and how my partnrs will b involvd As th srvic managr of Ibarmia, I can sarch and slct th most appropriat maintnanc srvic from th cosystm dpnding on thir : gographical intrvntion primtr ; tim to rpair ; pric so that I associat a maintnanc srvic packag to th drilling machins srvics for my customrs in Asia Nonfunctional constraints Faturs: Enabl asst rpository accss from th SLMToolBox Manag format introprability btwn modl rprsntations in th SLMToolBox & virtualizd assts rprsntation in th assts rpository Th MDSEA cor mta modls should b xtndd with constructs and attributs to nhanc th mapping with asst ontologis dfind in SP2 Tabl 12 - REQ - Rus cosystm / vm assts into srvic modls (rtriv in/tan assts) # Rus USDL VME assts dscriptions Virtualiz in/tan assts through BSM or TIM modls ID 2.2 Domain Srvic modling - Virtualization Importanc Could Goal To captur th ncssary information to publish assts to my cosystm through modling tools Impact To provid cohrnt mans for virtualizing assts in cohrnc with th MDSEA architctur Dscription In ordr to xpand his businss activity, a sals managr wants particular assts of th company, to b sold as srvics and to b known by othr cosystm mmbrs. A «srvic nginr» will idntify rlvant assts to b «virtualizd» and xposd as a srvic to th cosystm. Thn, h will captur this information with th SLMToolBox into a TIM modl. H will b guidd by wizards and tmplats, to writ th ncssary information, according to th ontologis of SP2 (.g.: tangibl /intangibl; ). Th data will fd th TIM Cor modl, and will b linkd with th srvic dscription, according to th constructs of MDSEA (xampl : «rsourcs») Onc an asst has bn dscribd («virtualizd»), th srvic nginr will publish it to th cosystm, samlssly from th SLMToolBox. Thanks to this functionality, th «public» assts of th ntrpris ar dscribd in a structurd format which is xploitabl by th MSEE platform, which allows cosystm mmbrs to sarch, brows, slct and buy such assts in th form of a srvic. Scnarios As th sals managr of Bivolino, I can dscrib my «cutfil MSEE Consortium Dissmination: Public 29/143

30 Nonfunctional constraints Faturs: srvic» as an «intangibl asst» and submit it to th cosystm, so that I can dvlop my businss, now that cosystm mmbrs ar awar of my srvics and skills As a txtil manufacturing company, I can dscrib and publish my «cutting machins» as «tangibl assts» through TIM modls so that th mmbrs of my cosystm ar awar of my production capability As a maintnanc company, I can dscrib my «maintnanc srvics» as an «intangibl asst» and submit it to th cosystm, so that potntial customrs can find, valuat and buy my srvics Enabl asst rpository accss from th SLMToolBox Manag format introprability btwn modl rprsntations in th SLMToolBox & virtualizd assts rprsntation in th assts rpository Th MDSEA cor mta modls should b xtndd with constructs and attributs to nhanc th mapping with asst ontologis dfind in SP2 Tabl 13 - REQ - Virtualiz in/tan assts through BSM or TIM modls # Publish USDL srvic dscriptions to asst rpository Rquirmnts: Srvic Enginring This sction givs an ovrviw of th high lvl rquirmnts collctd from th work of Fraunhofr IAO, mainly from th dlivrabl D12.1 (D12.1 Rport about Srvic Scnarios, 2012) Estimat th duration/cost/quality of th srvic dlivry ID 3.1 Domain Srvic nginring Importanc Should Goal Simulat th main aspcts of th srvic to dtrmin how it can b improvd, and how futur changs will affct th systm Impact Anticipat srvic cost/tim/quality assssmnt sinc th dsign phas Dscription Th Estimation of th duration/cost/dlivry of th srvic dlivry provids th usr with an important aspct for systm simulation. Systm simulation allows th usr to assss th systm s bhavior in particular circumstancs. As a rsult, futur dvlopmnt s plans or any modification plans can b basd on th rsults and rports of systm s simulations Scnarios As an IT support srvic managr, I nd to valuat if I can downsiz th hlp dsk tam and still satisfying th SLAs of Nonfunctional constraints Faturs: th incidnt managmnt procss Th simulation xcution should b basd on srvic modls laboratd thanks to th modling faturs of th SLMToolBox Tabl 14 - REQ - Estimat th duration/cost/quality of th srvic dlivry #2.1 - Light Businss Procss simulation Availability of rfrnc modls ID 3.2 Domain Srvic nginring MSEE Consortium Dissmination: Public 30/143

31 Importanc Goal Impact Dscription Should Provid guidanc to th srvic modlr whn starting a nw srvic modling projct Eas th accssibility to th SLMTools thanks to rusabl gnric srvic modls A library of rfrnc modls should b built with th hlp of th SLMToolBox, so that a nw usr would b abl to choos and rus a pr-initializd modlling projct ; in ordr not to start th modlling from scratch and bing guidd by rlvant modl tmplats Scnarios I can brows th modl rpository and sarch for srvic nginring rfrnc modls similar to my own cas, so that I can bnfit from good modling practics and xampls diagrams Nonfunctional constraints Faturs: Th rfrnc modls should b publicly accssibl on th modl rpository, and asily sarchabl #2.2 - Availability of rfrnc modls Tabl 15 - REQ - Availability of rfrnc modls Srvic nginring mthodology ID 3.3 Domain Srvic nginring Importanc Should Goal Provid guidanc to th srvic nginring projct tam Impact Provid a powrful srvitization kit, including documntation and tooling support Dscription A simpl usr guid should b laboratd, basd on th srvic nginring mthodology dvlopd by IAO and strongly connctd to th functionalitis of th SLMToolBox in ordr to driv th modlling activitis accordingly to th stps of th srvic nginring mthod. Scnarios - Nonfunctional constraints This could b achivd in two possibl forms. 1) A raw usr documntation prsnting th srvic nginring mthod modls and rlatd scrnshots of th SLMToolBox. 2) a dynamic and contxtual hp, dirctly intgratd within th SLMToolBox modlling ditors Tabl 16 - REQ - Srvic nginring mthodology Faturs: #2.3 - Srvic nginring mthodology Rquirmnts: Srvic Govrnanc Th rquirmnt dscription blow is xtractd from th discussions btwn POLIMI and HARDIS rgarding what support can b xpctd from th SP1 softwar tools for prformanc managmnt, in th fram of srvic lifcycl managmnt. It has bn shard with POLIMI that th softwar tools of WP1.5 could bring som support for th dsign phas of prformanc managmnt ( slction, implmntation, modification, and upgrad ). Th runtim phas ( monitoring, prsntation ) of th prformanc managmnt should b supportd by anothr st of monitoring softwar, ncompassd by th Srvic Ecosystm Innovation platform (WP2.6) Spcify th govrnanc systm of th organization MSEE Consortium Dissmination: Public 31/143

32 ID 4.1 Domain Srvic govrnanc Importanc Could Goal To idntify th right indicators to control th prformanc of my srvic and to spcify thm in cohrnc with th objctivs of th organization Impact To optimiz th prformanc of a srvic systm, thanks to a structurd dsign of th govrnanc systm of th VME Dscription According to th MSEE PI mthod, a businss usr will dfin th govrnanc systm through th following activitis : To dfin th «objctivs» which ar associatd to th dcision frams of th «piloting systm» To dfin th «dcision variabls» - as «drivrs» on which th dcisions can act to rach th «objctivs» To dfin «primary indicators» as quantifiabl and masurabl data which masur th fficincy of an activity or a st of activity Th usr will formaliz ths dfinition on th basis of th GraiGrid modling ditor, which will allow to : Enrich th BSM modls with th data rlatd to th govrnanc modl of th srvic systm Slct appropriat indicators from a rfrnc list according to a st of sarch critria s (cf. D13.5) Propos facilitis to chck th cohrnc (links and wights) of th triplts {objctiv ; drivrs dcision variabls ; primary indicators} for ach dcision cntr (cf. D13.3 Figur #7) Provid a tmplat sht to dsign th prformanc indicator from th prspctiv of th information systm (cf. D ) Scnarios As a srvic managr, I can dfin how to assss th prformanc of my srvic systm through th constitution of a dcisional grid with my objctivs, thir dcomposition, th idntification of dcision variabls and th choic of rlvant primary indicators slctd from an xisting databas so that I can implmnt th masurmnt of ths mtrics and I can rly on this rfrnc modl to valuat th masurmnts rsults and tak appropriat actions As a srvic managr, I can valuat th cohrnc of my primary indicators, basd on th link btwn th dcision Nonfunctional constraints Faturs: - variabls and th objctivs of my dcision systm Tabl 17 - REQ - Spcify th govrnanc systm of th organization #3.1 - KPI dscription wizards Transvrsal rquirmnts Updatd BSM & TIM mtamodls ID 5.1 Domain Srvic modling MSEE Consortium Dissmination: Public 32/143

33 Importanc MUST Goal Align BSM & TIM modling tmplats with D11.2 modifications Impact Align modling tools with last vrsion of MDSEA spcification Dscription S D11.2 Srvic concpts, modls and mthod: Modl Drivn Srvic Enginring 4.3 BSM srvic modl tmplats ; 5.3 TIM srvic modl tmplats Scnarios - Nonfunctional - constraints Faturs: Tabl 18 - REQ - Updatd BSM & TIM mtamodls #1.00 Updatd BSM & TIM tmplats mtamodls Stor modl and diagram data in a singl cntralizd rpository ID 5.2 Domain Srvic modling - intgration Importanc MUST Goal Shar srvic modls (diagrams and data) at diffrnt modling lvls Impact Enabl collaboration btwn actors and tools through th srvic nginring procss, for modling rlatd activitis Dscription WP4.2 provids a modl rpository as a modul of th MSEE IT Systm. It acts as shard rsourc to fdrat th sharing and communication of srvic mods btwn human actors and IT tools. Th SLMToolBox must intgrat with th modl rpository in ordr to : Enabl th collaboration btwn modling actors Provid srvic modls at TIM lvl to th gnric srvic dvlopmnt platform (UML) and to th IEP (BPMN). Scnarios I can rtriv a modling projct from th modl rpository I can publish a modling projct to th modl rpository I can updat a modling projct on my local nvironmnt from th modl rpository I can updat a modling projct on th modl rpository I can brows and sarch srvic modls on th modl rpository Nonfunctional constraints Faturs: Th SLMToolBox must mbd th modl rpository clint componnt in th modling nvironmnt. Tabl 19 - REQ - Stor modl and diagram data in a singl cntralizd rpository # Intgration with WP4.2 modl rpository MSEE Consortium Dissmination: Public 33/143

34 Boundaris Srvic systm modling Th SLMToolBox will not support th implmntation of th spcific domain aspcts. Th implmntation of th IT part is supportd by anothr MSEE IT systm, namly: th gnric srvic dvlopmnt platform. Hnc, th SLMToolBox will provid srvic systm modls at th TIM lvl, to th gnric srvic dvlopmnt platform. (D MSEE Srvic- Systm Functional and Modular Architctur, 2012). As a consqunc, th SLMToolBox will not support th modls at th TSM lvl, which is th rsponsibility of th dvlopmnt platform Srvic nginring As for th srvic systm modling, th SLMToolBox will not support th implmntation activitis of th srvic nginring procss Srvic govrnanc Th SLMToolBox will not covr th implmntation activitis and th runtim phas for th prformanc managmnt. MSEE Consortium Dissmination: Public 34/143

35 4. Functional analysis This sction of th documnt will prsnt th st of softwar faturs which wr xtractd from th rquirmnt analysis, prsntd in th prvious sction. Th diffrnt rols of th actors which would intract with th systm will b formulatd, as wll as th two major ndto-nd us cass, which th SLMToolBox will support in its final vrsion Faturs list Th following tabl rcaps th faturs which wr xtractd from th rquirmnt analysis. Each fatur is charactrizd 1) by a Valu attribut in ordr to qualify its ncssity; 2) by a Work attribut in ordr to qualify th ncssary ffort ndd for its implmntation. Finally, th wight attributs aims at stablishing a rlativ prioritization ranking with th following formula: Wight = 25*{valu}/ {work} (whr XL =4; L =3; M =2; S =1). Figur 12 - SLMToolBox v2.0 - Fatur List Impact Domain # Faturs Valu Work Wight Srvic Modling 1.00 Updatd BSM & TIM Mtamodls XL L 33 Srvic Modling 1.02 UML ditors XL M 50 Srvic Modling 1.03 Intgration with WP4.2 modl rpository XL L 33 Srvic Modling 1.04 Improvd Extndd Actigram Star Editor (v4.0) XL L 33 Srvic Modling 1.05 VME orintd GRAI Grid Editor (BSM Lvl) S M 13 Srvic Modling 1.06 VME orintd Extndd Actigram Star Editor (BSM Lvl) S M 13 Srvic Modling 1.07 Publish USDL srvic dscriptions to asst rpository S L 8 Srvic Modling 1.08 Rus USDL VME assts dscriptions M L 17 Srvic Modling 1.09 Ergonomic improvmnts on xisting ditors S M 13 Modl Transformation 1.10 BSM2TIM Modl Transformation M M 25 Modl Transformation 1.11 EA*2BPMN Modl Transformation XL L 33 Srvic Modling 1.12 Grai Nts Modling Editor (BSM lvl) S M 13 Srvic Enginring 2.1 Light Businss Procss simulation XL XL 25 Srvic Enginring 2.2 Availability of rfrnc modls M L 17 Srvic Enginring 2.3 Srvic nginring mthodology S M 13 Srvic Govrnanc 3.1 KPI dscription wizards L M 38 MSEE Consortium Dissmination: Public 35/143

36 4.2. Covrag of SP1 Dlivrabls Th following tabl cross chck th covrag of SP1 dlivrabls with th faturs proposd for th scond vrsion of th SLMToolBox. Dlivrabl Titl Issu WP1.5 Faturs Covrag D11.1 Srvic concpts, modls, mthod at CIM-PIM-PSM lvl M4 BSM + TIM Mtamodls + Tmplats v1.0 Modling Editors : GraiGrid ; EA* ; BPMN OK D11.2 Srvic concpts, modls, mthod at CIM-PIM-PSM lvl M12 #1.0 - Updatd BSM & TIM Mtamodls #1.2 - UML ditors #1.5 - VME orintd GRAI Grid Editor OK #1.6 - VME orintd Extndd Actigram Star Editor # GRAI Nts Editor D11.3 MDA/MDI Modl Transformation M8 # BSM2TIM Modl Transformation # EA*2BPMN Modl Transformation OK #1.4 - Improvd Extndd Actigram Star Editor (v4.0) D11.4 MDA/MDI Modl Transformation M15 # BSM2TIM Modl Transformation # EA*2BPMN Modl Transformation OK #1.4 - Improvd Extndd Actigram Star Editor (v4.0) D11.5 MSEE architctur for Srvic modling M12 #2.1 - Light Businss Procss simulation OK D11.6 MSEE architctur for Srvic modling M24 Planning D12.1 Rport about Srvic Scnarios M4 #2.1 - Availability of rfrnc modls OK D12.3 Srvic nginring mthodology for product-rlatd srvics M6 #2.1 - Availability of rfrnc modls OK D12.4 Srvic nginring mthodology for product-rlatd srvics M18 Planning D12.5 Evaluation of Study about Srvic Laboratoris and xisting tst scnarios M15 #2.1 - Light Businss Procss simulation OK D12.6 Evaluation of Study about Srvic Laboratoris and xisting tst scnarios M24 Planning D13.1 KPIs and SLAs for cosystm govrnanc M6 #3.1 - KPI dscription wizards OK D13.2 KPIs and SLAs for cosystm govrnanc M15 #3.1 - KPI dscription wizards OK D13.3 Rport on Rol Modls in th Intgratd Srvic Lifcycl Mgmt Modl M9 #3.1 - KPI dscription wizards OK D13.4 Liability, trust and rputation modls M18 Planning D13.5 Srvic oprations monitoring and control toolst M12 #3.1 - KPI dscription wizards OK D13.6 Srvic oprations monitoring and control toolst M24 Planning D14.1 Intgratd Srvic Lifcycl Managmnt Modl M12 #2.3 - Srvic nginring mthodology OK D14.2 Intgratd Srvic Lifcycl Managmnt Modl M18 Planning D14.3 Rport on Rol Modls in th Intgratd Srvic Lifcycl Mgmt Modl M15 #2.3 - Srvic nginring mthodology OK D14.4 Rport on Rol Modls in th Intgratd Srvic Lifcycl Mgmt Modl M21 Planning D14.5 Rport on th Approach on th Customization of Srvic Lifcycl Mgmt M18 Planning D14.6 Rport on th Approach on th Customization of Srvic Lifcycl Mgmt M24 Planning Figur 13 - Covrag of SP1 dlivrabls W can assss that gnrally, th faturs proposd in WP1.5 tnd to covr ach work packag in SP1. W can lgitimatly considr that modling faturs tnds to b prdominant but provid a solid basis for mor spcific functions, such as KPI modling and businss procss simulation. As mntiond prviously in th documnt, th SP1 dlivrabls which ar not issud at M18 (idntifid as Planning in th prvious tabl) will b furthr analyzd from th WP1.5 prspctiv; vntually, nw rlvant faturs will b implmntd accordingly in th SLMToolBox Actors and rols Th MSEE IT Systm will provid svral functionalitis that will b usd by diffrnt usrs. In this sction th rols of th actors involvd in th activitis of srvic rquirmnt and srvic dsign phass will b idntifid and dscribd. This list is partially drivd from th actors idntifid at th lvl of th gnric MSEE IT architctur. Th rols dscrib bllow dfin at a concptual lvl th catgoris of usr profils concrnd by th SLMToolBox faturs. MSEE Consortium Dissmination: Public 36/143

37 From th two modling abstraction lvls covrd by th SLMToolBox (BSM; TIM), it is trivial to driv two catgoris of actors which will contribut to th modling activitis, in intraction with th Modling Environmnt, providd by th SLMToolBox Businss Actors Figur 14 - Systm Actors This catgory includs th actors which can collct th knowldg of th ntrpris at th businss lvl. Businss Analyst: is th actor that can collct th knowldg and th rquirmnts at th highst lvl of th ntrpris. H is intrstd in th analysis of its ntrpris / cosystm and th dvlopmnt of th srvic systm at a global lvl. Domain xprt: this actor is an xprt of a spcific domain insid th ntrpris / cosystm. This can b on of th following: IT, Manufacturing, Organization. Th domain xprt is abl to bring spcific knowldg and constraints rlatd to its spcific domain. H can idntify th impact of th srvitization at an oprational lvl and procd to th dsign of th modifications to implmnt in its domain Domain Spcific Actors Th domain spcific modling activitis at TIM lvl will b handld or in th rsponsibility of th corrsponding domain actors: IT, Manufacturing, Organization. (D Srvic concpts, modls and mthod: Modl Drivn Srvic Enginring, 2012, p. 81) This catgory dfins th actors rlatd to on of th thr spcific domains of th srvic systm. IT Exprt: this actor can collct th knowldg and procd to th dsign rlatd to th IT systm of th ntrpris / cosystm (including: infrastructur, applications, data rpositoris ). Manufacturing Exprt: this actor can collct th knowldg and procd to th dsign rlatd to th physical mans of th ntrpris / cosystm (including: manufacturing machins, supply chain, products dsign ) Organization Exprt: this actor can collct th knowldg and procd to th dsign rlatd to th organizational aspcts of th ntrpris / cosystm (including: human rsourcs ) MSEE Consortium Dissmination: Public 37/143

38 4.4. End-to-nd scnarios Th SLMToolBox ssntially supports th rquirmnt and dsign phass of srvic nginring. Th two following subsctions illustrat two major scnarios, involving th main faturs of th SLMToolBox, through spcific us cass and thir squnc Scnario 1: Dsign a nw srvic within a singl ntrpris This first scnario dpicts how th SLMToolBox will b usd to dsign a nw srvic, within a singl ntrpris. SLMToolBox Businss usrs Modl Srvic Rquirmnts Dsign Srvic Systm Transform BSMTIM Rus Rfrnc Modls Businss Procsss (Ext Act) BSM Modls Dcision Structurs (GRAI) Dfin KPIs Assss cost & xcution tim Analysts / spcialists Data Modls UML Procss Modls BPMN TIM Modls Dvlopprs Dvlop IT Artfacts Srvic Dvlopmnt Platform TSM Modls Modl Rpository Figur 15 - Dsign a nw srvic within a singl ntrpris This scnario is drivn by thr main us cass: 1. Modl srvic rquirmnt (supportd by th SLMToolBox BSM modling faturs) 1. Rus rfrnc modls : th businss usr has th possibility to brows th modl rpository and sarch for a convnint rfrnc modl to start modling th srvic rquirmnts in a BSM modling projct 2. A BSM modl is initializd and nrichd trough th tmplat ditor (for gnric srvic dscription) and xtndd with graphical modls; th BSM modls ar stord within th modl rpository, shard with th rst of th MSEE IT systm. Th ovrall modling procss at BSM lvl follow th BSM Srvic Modling mthod, drivd from D11.2 Srvic concpts, modls and mthod: Modl Drivn Srvic Enginring 3. Th govrnanc systm of th srvic is modld through th GraiGrid ditor 4. Th KPIs of th srvic ar dfind on th basis of th GRAI grid modl 5. Businss procss ar laboratd with th Extndd Actigram Star languag MSEE Consortium Dissmination: Public 38/143

39 6. Som of ths procsss can thn b simulatd in ordr to assss thir xcution tim and cost 2. Dsign srvic systm (supportd by th SLMToolBox TIM modling faturs) 1. Th first stp of th dsign phas is to rtriv th BSM modls from th modl rpository and to initializ a TIM modling projct, thanks to automatic modl transformation tchniqus 2. A TIM modl is initializd and nrichd trough th tmplat ditor (for gnric srvic dscription) and xtndd with graphical modls ; th BSM modls ar stord within th modl rpository, shard with th rst of th MSEE IT systm 3. UML modls ar laboratd via th UML modlr 4. Extndd Actigram star procss modls from th BSM modling projct can b automatically transformd into BPMN procss modls, ithr collaboration diagram or procss modls. Th rsulting BPMN modls ar attachd to th currnt TIM modling projct 5. BPMN procss modls can b modifid / nrichd by th usr, within th TIM modling projct 3. Dvlopmnt of IT componnts / artifacts (supportd by th Srvic Dvlopmnt Platform) 1. Th dvlopmnt platform rtrivs th TIM modls from th modl rpository 2. TSM modls ar initializd from th TIM modls and nrichd with softwar cod in ordr to dvlop xcutabl softwar componnts Scnario 2: Dsign & dploy a nw srvic within a VME SLMToolBox Import Assts Modl Srvic Rquirmnts BSM Modls Publish Srvic/Asst Businss usrs Analysts / spcialists Dsign Srvic Systm TIM Modls Modl Rpository Assts Rpository Dvlopprs Enrich Procss Modls Srvic Dvlopmnt Platform Procss Modls BPMN Dploy & Excut Ecosystm Procss Innovation Ecosystm Platform Figur 16 - Dsign & dploy a nw srvic within a VME MSEE Consortium Dissmination: Public 39/143

40 This scnario is drivn by thr main us cass: 1. Modl srvic rquirmnt (supportd by th SLMToolBox BSM modling faturs) 1. Th modling activitis at th BSM lvl ar similar to th prvious scnario. Howvr, in th contxt of a virtual ntrpris, w assum that th modlr should b abl to rtriv th dscription of th assts of his partnrs. In practic, th usr of th SLMToolBox is abl to connct to th Assts Rpository, to brows and sarch for rlvant assts to includ in its srvic modls; so that h is abl to compos a nw srvic, on th basis of xisting assts xposd by th mmbrs of th VME. 2. Modl srvic rquirmnt (supportd by th SLMToolBox BSM modling faturs) 1. Th modling activitis at th TIM lvl ar similar to th prvious scnario. Howvr, in th contxt of a virtual ntrpris, w assum that th modlr should b abl to publish th dscription of th srvic having bn modld; so that th VME is now awar of th charactristics of th nw srvic bing dvlopd. In practic, w propos that th modling activitis of th virtualization procss for tangibl / intangibl assts would b supportd by th SLMToolBox, until th assts dscription would b publishd on th Assts rpository. 2. Oprational procsss ar modld with th BPMN ditor of th SLMToolBox and shard with th dvlopmnt platform 3. Enrich procss modls (supportd by th Srvic Dvlopmnt Platform) 1. In this cas, th srvic dvlopmnt platform will rtriv BPMN procss from th modl rpository; and provid th mans for nriching ths procsss so that thy can b dployd and xcutd on th Innovation Ecosystm Platform; in ordr to orchstrat th activitis of th VME mmbrs. MSEE Consortium Dissmination: Public 40/143

41 5. Dtaild dsign 5.1. Systm nvironmnt Ovrviw As dfind in th gnral architctur of th MSEE IT Systm, th SLMToolBox is dsignd as a modul bing part of th MSEE IT Systm. Th MSEE IT Systm is th intgratd nvironmnt that will provid all th srvics, applications, platforms and tools dvlopd in th diffrnt tchnical work packags of th MSEE projct. As dpicts th following figur, th SLMToolBox is idntifid as on of th MSEE usr dsktop softwar. Th figur bllow dpicts th ovrall intgration points btwn th MSEE IT platforms at M18 (sourc: D Tst Plan and Documntation). Figur 17 - MSEE IT systm intgration ovrviw It is possibl to idntify thr platforms which mainly support th srvitization procss: th Dvlopmnt Platform will provid tools for businss modling and srvic lifcycl managmnt, through th SLM ToolBox, but also for th tchnical dvlopmnt of IT srvics and applications; th Srvic Dlivry Platform, that will b in charg of managing srvic rgistration and dlivry, as wll as smantic sarch and invocation; th Mobil Platform will xtnd th two mntiond platforms in ordr to b accssd by mobil dvics. In this gnric architctur, th SLMToolBox has th rsponsibility to support srvic nginring activitis, up to th implmntation of th rsulting IT assts, which is handld by th Gnric Srvic Dvlopmnt Platform. MSEE Consortium Dissmination: Public 41/143

42 Intraction with othr platforms Th following tabl summarizs th intractions btwn th SLMToolBox and othr MSEE IT platforms. Platform Dvlopmnt Platform Dvlopmnt Platform Dvlopmnt Platform Mobil Platform Dvlopmnt modul *Innovation Ecosystm Platform (IEP) Typ of Intraction Dirct Indirct Indirct Indirct Dirct (?) Dscription Dirct accss to th modl rpository for srvic modl publication & rtrival (BSM & TIM modling projcts) Provid UML class diagrams (TIM lvl) Provid BPMN2.0 class diagrams (TIM lvl) Provid UML class diagrams (TIM lvl) Rtriv / Publish virtualizd assts from / to th mmbrs of a VME Tabl 20 - SLMToolBox platform intractions Focus: Intractions with th Gnric Srvic Dvlopmnt Platform Mdia Modl rpository Modl rpository Modl rpository Modl rpository Assts Rpository In th contxt of srvic nginring, srvic dvlopmnt is th procss that follows th dcision for th implmntation of a srvic or front-nd application. Th Dvlopmnt Platform taks ovr aftr th initial concptual cration of a srvic or application and facilitats th transition from th initial concpt to a BSM, thn a TIM and finally to a TSM modl. From a functional prspctiv, th Dvlopmnt Platform ultimatly aims to transform th BSM and TIM modls into th TSM. This is don in a two stag procss: during th first stag a BSM to TIM transformation is prformd by th SLM Toolbox, which is part of th Dvlopmnt Platform, as xplaind in th following sctions of this chaptr. At th scond stag a TIM to TSM transformation by th Dvlopmnt Platform itslf is compltd, according to th platform s implmntation procdur. Through th SLM Toolbox, th BSM input is convrtd from a mor concptual to a mor spcific output, known as Tchnology Indpndnt Modling (TIM) output. This product (TIM) is th intrnal input for th Dvlopmnt Platform. Th TIM vntually is convrtd to th TSM (Tchnology Spcific Modl) which producs th input for th MSEE Srvic Dlivry Platform. Dvlopmnt of th BSM, TIM and TSM modls is prformd by businss analysts, businss usrs and softwar dvloprs oprating th UIs xposd by th Dvlopmnt Platform and th SLM Toolbox at th various stags of th dvlopmnt procss. Actors ar xpctd to us th various UI lmnts of both moduls to compos and manipulat ths thr classs of modls Modling workflow and collaboration with th srvic dvlopmnt platform In this simpl workflow scnario, th procss bgins with th SLM Toolbox, whr th Businss usr initially crats a BSM modl. Aftr diting and manipulation, th BSM modl is finalizd and stord in th Modl Rpository Modul. Aftrwards, a Businss analyst rtrivs th BSM modl and, using th SLM Toolbox again, constructs a TIM modl. Th TIM modl is cratd through automatic transformation functions (th SLM Toolbox s Modl Transformation Tools) and dirct diting. Th rsulting TIM modl is th stord in th Modl Rpository Modul. MSEE Consortium Dissmination: Public 42/143

43 Finally, a Softwar Dvlopr initializs a TSM modl. Th Softwar Dvlopr rtrivs th corrsponding TIM modl dirctly into th Dvlopmnt Platform. Thn, this platform supports th softwar implmntation activitis for front-nd application or wb srvic dvlopmnt and th rgistration of ths softwar artifacts to th Dlivry Platform. Figur 18 - Modling workflow and collaboration with th srvic dvlopmnt platform MSEE Consortium Dissmination: Public 43/143

44 5.2. Modlling languags dscription This sction provids som rfrncs for th diffrnt modling languags supportd by th ditors providd in th SLMToolBox modling nvironmnt Intgratd graphical ditors Th modling languags supportd by spcific ditors ar mainly drivd from th GRAI Intgratd Mthodology (GIM). Th GIM propos svral modling languags to dscrib th various parts of th company, which can b xtndd to th dscription of a srvic systm. Modling Domain Dscription Languag GRAI Grid Dcision Th GRAI grid (G. Doumingts, 1998) taks up th hirarchical and functional approach. It allows idntifying th st of dcision cntrs of th studid systm, as wll as thir links. Th GRAI grid is prsntd in th form of a matrix with: Th managrial axis or control axis which rprsnts th various dcision lvls which can b found in th ntrpris. This axis is dcomposd hirarchically in svral lvls, dfind by th horizon and th priod of dcision making. Th function axis which dscribs th various activitis rquird to th product lif cycl. It is dcomposd into svral functions which group a st of activitis having a sam idntifid finality (nginring, manufacturing, quality, maintnanc, dlivry, rcycling...). Extndd Actigram Star GRAI Nts Businss procss Dcision ntworks Each function of this axis can b dcomposd in thr control functions: to manag th products (intrnal or xtrnal, it mans procurmnt and purchasing), to manag th rsourcs (human or tchnical) and to plan (to synchroniz at ach lvl product and rsourc managmnt). Extndd Actigram intnds to provid a st of simpl graphical artifacts for businss procss modling. Initially, th GIM dfind th Extndd Actigram formalism inspiring from IDEF3 languag. This vrsion has bn xtndd in ordr to facilitat th transformation of Extndd Actigram procsss toward BPMN2.0 formalism. A nw vrsion of th EA languag has bn proposd as th Extndd Actigram Star modling languag. Grai Nts provid formalism for dynamical dscription of th activitis, rlatd to th dcision cntr concpt of th GraiGrid formalism. As for th GraiGrid, it has bn spcifically dsignd in GIM, in ordr to modl th dynamic aspcts of dcision activits. Th GraiNt languag mainly involvs th following concpts: activitis, information support, logical oprators and communication symbols. Tabl 21 - Intgratd graphical ditors MSEE Consortium Dissmination: Public 44/143

45 Extrnal ditors Th modling languags corrsponding to xtrnal ditors rfr to standardizd modling languags. Modling Languag Domain Rfrncs UML Class Diagram Modl IT data modls Typically, th UML class diagram is th main building block of objct orintd modling. It is usd both for gnral concptual modling of th systmatics of th application, and for dtaild modling translating th modls into programming cod. In th fram of srvic systm modling, as dfind in MDSEA architctur, class diagrams ar usd to modl data ntitis and thir rlationships in ordr to rprsnt th data modls of th srvic systm. (OMG Unifid Modling Languag (OMG UML), Suprstructur, V2.1.2, 2007) UML Us Cas BPMN2.0 Modl usr intraction with IT systms Modl dtaild businss procsss Us cass ar a mans for spcifying rquird usags of a systm. Typically, thy ar usd to captur th rquirmnts of a systm, that is, what a systm is supposd to do. Th ky concpts associatd with us cass ar actors, us cass, and th subjct.. (OMG Unifid Modling Languag (OMG UML), Suprstructur, V2.1.2, 2007) Businss Procss Modl and Notation (BPMN) is a standard for businss procss modling that provids a graphical notation for spcifying businss procsss in a Businss Procss Diagram (BPD) basd on a flowcharting tchniqu. (Businss Procss Modl and Notation (BPMN) vrsion 2.0, 2011) Tabl 22 - Extrnal ditors MSEE Consortium Dissmination: Public 45/143

46 5.3. Ovrall objct modl This sction dscribs th structur of som of th most important mtamodls manipulatd by th modling nvironmnt of th SLMToolBox. Ths mtamodls ar built on th basis of th cor tmplats dfind in th dlivrabl D11.2: Srvic concpts, modls, mthod at CIM-PIM-PSM Modling architctur ovrviw MDSEA dfins a st of constructs and rlationships (dscribd with tmplats ) which ar spcific to th domain of srvic systm modling, at 3 modling lvls: BSM/TIM/TSM (D Srvic concpts, modls and mthod: Modl Drivn Srvic Enginring, 2012, p. 26). For ach abstraction lvl, MDSEA suggst a st of rfrncs to standard or formr graphical modling languags (which ar domain agnostic), in ordr to xtnd and complt th rprsntation of th systm to b modld, undr diffrnt prspctivs (.g.: dcision structur; procss; us cass; ). This typ of modling architctur is basd on a viw modl pattrn (or viwpoints framwork ) (ISO/IEC/IEEE 42010:2011, Systms and softwar nginring Architctur dscription) as it dfins a cohrnt st of viws to b usd, in th construction of a manufacturing srvic. Th purpos of viws and viwpoints is to nabl humans to comprhnd vry complx systms, to organiz th lmnts of th problm and th solution around domains of xprtis and to sparat concrns. In th nginring of physically intnsiv systms, viwpoints oftn corrspond to capabilitis and rsponsibilitis within th nginring organization Figur 19 - Modling architctur ovrviw MSEE Consortium Dissmination: Public 46/143

47 Both BSM (Businss Srvic Modls) and TIM (Tchnology Indpndnt Modls) ar structurd in th sam mannr. A cor modl gathrs a st of gnric (mta-) data in ordr to qualify th srvic to b modld (spcifid / dsignd) ; this cor modl rfrs to xtrnal graphical modling languags (.g. : UML) so that crtain aspcts of th srvic modl can b laboratd in mor dtails with th hlp of graphical languags. This structur allows to map viw spcific modling languags (.g.: GraiGrid, UML Class Diagram) with domain spcific constructs (i..: MDSEA BSM) without introducing modifications or rstrictions to th MDSEA mtamodl. From th usr point of viw, it allows th possibility to dit cor information, indpndnt from any spcific modling languag, and to rtriv and rus this data undr diffrnt viws, accomplishd with th hlp of svral graphical diagrams. With this approach, MDSEA Cor Constructs rmain agnostic from any rprsntation formalism. Thir implmntation is ralizd by a cor modl, which acts as domain spcific (Srvic Systm Modling) glu btwn svral modling languags. Thus, w can rus standard modling languags without introducing modifications to thir mtamodls (.g.: BPMN, UML ). Graphical languags such as Extndd Actigram or GraiGrid can continu to volv, with (almost) no impact on MDSEA Cor mtamodls (i..: BSM) BSM cor Mtamodl Th following figur givs a rprsntation of th BSM constructs in UML class diagram format. S figur in: Annx 2 Dtaild dsign : 10.1 Mta modl BSM TIM cor Mtamodl Th following figur givs a rprsntation of th TIM constructs in UML class diagram format S figur in: Annx 2 Dtaild dsign : 10.2 Mtamodl - TIMExtndd Actigram Star Mtamodl (BSM) Th primary goal of Extndd Actigram Star is to provid a common and simpl modling notation that is undrstandabl by businss usrs, for th dscription of businss procss. In comparison to othr initiativs such as BPMN, Extndd Actigram rlis on a rduc st of graphical lmnts and focus on th businss lvl of ntrpris procss. By its simpl and accssibl syntax, Extndd Actigram Star intnds to rduc th gap btwn th idation and th dsign of businss procss. To achiv this goal, th dsign of th languag Extndd Actigram Star rlis on prvious work, dvlopd in th fram of th GRAI Mthodology, which dfins GRAI Extndd Actigram as a procss modling languag, among othr graphical formalisms, for ntrpris modling and dcision cntric analysis. It is to not that in its initial vrsion, GRAI Extndd Actigram has bn dsignd on th basis of IDEF3 mthodology (Blinn, 1989), which dfins graphical notation for procss flow dscription, in th fram of systm nginring. Extndd Actigram Star facilitats th modling of businss procss in an ntrpris offring a dynamic viw of th procss bing modld. It is addrssd to businss usrs rsponsibl of th cration of th first modl, businss popl rsponsibl of th managmnt and monitoring, and to tchnical dvloprs rsponsibl of th dvlopmnt of businss procss modling tools. As a graphical modling languag, Extndd Actigram Star will provid businss usrs and analysts standards to visualiz businss procsss in an ntrpris, and thus with a comprhnsibl and asy way to handl ths procsss. MSEE Consortium Dissmination: Public 47/143

48 Thus, Extndd Actigram Star is a proposition of a nw, mor dvlopd vrsion of GRAI Extndd Actigram. It is basd on a spcific dvlopmnt stratgy: Kp th cor principls of GRAI Extndd Actigram Add nw concpts in ordr to support abstraction, and to as th implmntation of softwar Grai Grid Mtamodl (BSM) This mtamodl is drivd from an analysis of xisting documntation of th GRAI mthodology and inspird from th dsign of th modling tool GRAITools, which offr th mans to modl GraiGrid diagrams in cohrnc with th GRAI mthodology. Th following figur givs a rprsntation of th constructs of th GraiGrid rprsntation formalism S figur in: Annx 2 Dtaild dsign : 10.3 Mtamodl Grai GridMapping: BSM GraiGrid This figur illustrats th intgration of th Cor Constructs of th BSM modling lvl with th GraiGrid languag. W can notic that thr constructs of BSM ar dpndnt on th corrsponding constructs in th GraiGrid Languag. Figur 20 - Mapping: BSM GraiGrid Mapping: BSM Extndd Actigram Star This figur illustrats th intgration of th Cor Constructs of th BSM modling lvl with th ExtnddActigram languag. W can notic that two constructs of BSM ar dpndnt on th corrsponding constructs in th ExtnddActigram Languag. Figur 21 - Mapping: BSM Extndd Actigram Star MSEE Consortium Dissmination: Public 48/143

49 5.4. Srvic modling faturs Summary of modling ditors Th modling nvironmnt will support th srvic systm modling activitis by providing ditors for domain spcific modls (BSM, TIM) and rlatd modling languags to nhanc th dscription of th BSM and TIM modls. In our functional approach, w propos to provid a st of languag spcific modling ditors for ach modling languag. Th following tabl givs an ovrviw of th modling ditors to b includd in th SLMToolBox; for ach modling lvl (BSM; TIM). Modling Lvl Goal Modling Langag Editor BSM BSM BSM BSM BSM Dscrib srvic at high lvl Dscrib simpl businss procsss Dscrib dcisional structurs of th organization Modl th xcution part of a dcision structur Dscrib Information Structurs BSM Tmplats Spcific Dvlopmnt Extndd Actigram Star Spcific Dvlopmnt Grai Grid Grai Nts UML (Us Cas ; Class Diagrams ; ) Spcific Dvlopmnt Spcific Dvlopmnt Opn Sourc Plugin (PAPYRUS) TIM Dscrib srvic at high lvl TIM Tmplats Spcific Dvlopmnt TIM Dscrib dtaild businss procsss BPMN2.0 Opn Sourc Plugin (BPMN2.0 Modlr) TIM Spcify th IT artfacts UML (Us Cas ; Class Diagrams ; ) Opn Sourc Plugin (PAPYRUS) Tabl 23 - SLMToolBox - Modling ditors ovrviw Ths modling ditors ar intgratd within th sam nvironmnt and tchnical platform (Eclips Juno) in ordr to maintain data introprability; cohrnc btwn modls and improv th usability of th tool, from th usr prspctiv F#1.02 UML Editors Rquirmnts UML diting capabilitis ar rquird in ordr to 1) captur th domain modl at th BSM lvl 2) laborat TIM modls so that th Dvlopmnt Platform can gnrat cod skltons from th UML modls. Th UML modllr must satisfy th following constraints: Intgrat with th tchnical platform of th SLMToolBox (Eclips Platform) Comply with UML2 standard XMi rprsntation format Support th following UML diagram typs : o Us Cas diagrams o Class Diagrams o Componnt Diagrams MSEE Consortium Dissmination: Public 49/143

50 o Squnc Diagrams o Activity Diagrams Intgration of Papyrus Papyrus is a ddicatd tool for modling within UML2; th tool is opn sourc and basd on th Eclips nvironmnt. Ky faturs: Eclips UML2 complianc Full rspct of th UML2 standard as dfind by th OMG Full rspct of th DI2 (Diagram Intrchang ) standard Extndabl architctur of Papyrus that allows usrs to add nw diagrams, nw cod gnrators, tc. Profil dvlopmnt support facilitis for UML2 profils Figur 22 - UML Editor F#1.04 Improvd Extndd Actigram Star Editor Th languag Extndd Actigram Star hav bn modifid with rspct to its last spcification (vrsion 4.0). As a rsult, ths modifications should b rflctd in th Extndd Actigram star ditor of th SLMToolBox. Ths modifications wr basd on th managmnts of: Start/End vnts in Extndd Activitis. Rsourc rols of SupportFlows. Ths modifications wr mainly addd to EA* modling constructs in ordr to facilitat th transformation from EA* to BPMN2.0 modls and for a bttr rprsntation of businss procsss through EA* diagrams. MSEE Consortium Dissmination: Public 50/143

51 Start/End vnts in Extndd Activitis In ordr to idntify th ntry and xit of a procss, notion of starting and nding Extndd Activitis wr addd. An Extndd Activity s natur (Starting, Ending or non) is dtrmind by a st of conditions summarizd in th tabl blow whr isstarting and isending ar Boolan attributs addd to th ExtnddActivity concpt: Extndd Activity Condition isstarting = fals isending = fals isstarting = tru isending = fals isstarting = fals isending = tru isstarting = tru isending = tru Graphical Rprsntation Act1 Act2 Act3 Act4 Figur 23 - Starting and Ending Extndd Activitis Act1 is nithr a Starting nor an Ending ExtnddActivity Act2 is a Starting ExtnddActivity Act3 is an Ending ExtnddActivity Act4 is a Starting and Ending ExtnddActivity Modling ruls: At last on starting ExtnddActivity and on nding ExtnddActiviy should b dfind in a procss or in on of its Structural ExtnddActivitis. Svral Starting and Ending ExtnddActivitis ar allowd in a diagram. This figur highlights th diffrnc btwn EA* diagrams bfor th dfinition of th Start/End attributs. Figur 24 - Start/End in EA* diagram (bfor and aftr) MSEE Consortium Dissmination: Public 51/143

52 Rsourc rols of SupportFlows Th rol of vry rsourc in a procss should b wll dfind in ordr to undrstand th xact rsponsibility of ths rsourcs. Rsourc s rol can b: Rsponsibl for: Th IT or Human rsourc is rsponsibl for th supportd Extndd Activity. It rprsnts a gnral rol lik managr or customr in cas of Human rsourcs, or information systm in cas of IT rsourc participats in: Th rsourc participats in th xcution of th supportd Extndd Activity without bing dirctly rsponsibl for it Ths rols ar rprsntd in th EA* diagram through support flows which connct rsourcs and Extndd Activitis. SupportFlows Condition rsourcrol = rsponsiblfor rsourcrol = participatsin Figur 25 - rsourcrol of a SupportFlow Graphical rprsntation Two diffrnt graphical rprsntations ar supportd for rsponsiblfor and participatsin rsourcrols. Modling Ruls : A rsourc supporting can support svral Extndd Activitis and can possss diffrnt rols A Matrial rsourc can only participat in th Excution of an Extndd Activity Bfor Aftr Figur 26 rsourcrol in EA* diagrams (bfor and aftr) In th first diagram, thr ar two IT rsourcs Configurator Dscriptions Storag and Bivolino information systm. Th diagram s ambiguity concrning th rol of ach rsourc hids som information from th usr. Whil in th scond diagram it is clar that Bivolino Information systm is rsponsibl for th two Extndd Activitis whil th Configurator dscriptions Storag only participats in th Extndd Activity s xcution. MSEE Consortium Dissmination: Public 52/143

53 Cohrnc ruls Procss ExtnddActivity Procss is an ssntial concpt of th languag. It is a st of rlatd, structural or atomic activitis logically chaind and triggrd by flows and vntually using oprators and connctors. Elmnts constituting a Procss can b dividd in two catgoris: nods (FlowNod) and flows (Flow). A Procss is rprsntd by on diagram. Th following figur is a graph rprsntation of a procss and its dcomposition of ExtnddActivitis. Figur 27 EA* Procss - objct diagram Th graph can b summarizd in th following points: P1 rprsnts th procss to b modld. P1 is composd of two ExtnddActivitis: Act1 and Act2. Act1 is a structural Extndd Activity connctd to Procss P2 ( isa association rlation). Act2 is an atomic ExtnddActivity, and can t b composd of othr FlowElmnts. P2 is composd of thr atomic ExtnddActivitis: Act3, Act4, and Act5. Evry Structural Activity is connctd to a Procss via an isa rlation. Procss - ProcssConnctor Th Procss connctor indicats that th origin or th dstination blongs to th domain of study and that it is modld. Th domain of study hr is all procsss that blong to th ntrpris. Class nam ProcssConnctor Inhrits from Connctor Attribut Typ Dscription / Usag procssrfrnc Rfrnc A rfrnc to th Procss rfrncd by this connctor Figur 28 - ProcssConnctor attributs W can notic that a ProcssConnctor has a rfrnc pointing to a Procss. This rlation is dscribd in th following figur. procss1 : Procss procssconnctor : ProcssConnctor procss2 : Procss Figur 29 - Procss ProcssConnctor rlation In th abov figur, procss1 is th procss to b modld, it is composd of a procssconnctor which is in its turn pointing to anothr Procss (procss2). MSEE Consortium Dissmination: Public 53/143

54 F# VME orintd GRAI Grid Editor (BSM Lvl) GRAI GRID for Virtual Manufacturing Entrpris In th MSEE projct, a virtual manufacturing ntrpris (VME) is a tmporary allianc of companis for th liftim of a joint production of srvic. VMEs ar such ntitis, which, from th point of viw of thir srvic to th customr, appars to b on ntity, but in rality ar formd from svral autonomous ntitis, or partnrs. Th proprty that diffrntiats a virtual ntrpris from an ordinary valu chain is th fact that thr is a singl locus, which taks full rsponsibility for th ntir valu chain of its product or products, vn though th task is carrid out by many participants and for that rason thy coopration must b harmonic. Th GRAI Grid modling languag is usd for modling th dcisional structur of th spcific ntrpris. Th GRAI grid concpt rlis on th fact that any managmnt dcision that nds to b takn will always b mad with rfrnc to a spcific tim horizon. Managrs typically dfin stratgic, tactical, oprational and ral-tim managmnt lvls. Ths lvls implicitly involv a hirarchy of dcision functions structurd according to dcision horizons or priods. Ths clls rprsnt dcision cntrs which can hav two typs of connctions; non-hirarchical and hirarchical connctions. In a VME, th us of th Grai- Grid allows to rprsnt dcisions concrning product and rsourc managmnt and planning in various ntrpris ntitis. For this purpos, w introduc a nw concpt w call Collaborativ Grai Grids. Ths concpts prmits to mrg (combin) th Grai Grid of ach partnr in ordr to provid a whol Grai Grid for th Virtual Entrpris. This sction is a proposition of Improvd Grai Grid ditor for a VME orintd Grai Grid Editor Collaborativ Grai Grid In ordr to raliz th VME orintd Grai Grid ditor, two options will b laboratd and dtaild. Combination of partnrs A Virtual Manufacturing Entrpris (VME) intgrats N manufacturing ntrpriss. Th dcisional structur of ach manufacturing ntrpris is dfind by a Grai Grid. In ordr to laborat th dcisional structur of th VME, w propos to combin and to structur svral grids. Th concpt of this proposition is adaptd to th modlling of collaborativ procsss. For xampl, a VME intgrats two manufacturing ntrpriss (ENT1 and ENT2). Th dcision structurs of ENT1 and ENT2 ar rspctivly DS1 and DS2. Th dcision structur (DSVME) of th VME rsults from th combination of DS1 and DS2 as dpictd in th tabl bllow. In ordr to modl informational and dcisional flows of th VME, w also dvlop flows btwn diffrnt dcision and information cantrs of th diffrnt dcision structurs (DS1 and DS2). Th usr of th SLMToolBox at BSM lvl is usually awar of th diffrnt dcision structurs (Grai Grid) that blong to th VME partnrs and th dpndncis btwn thm. As a rsult h is abl to modl this collaboration in a on combind Grai Grid. MSEE Consortium Dissmination: Public 54/143

55 Grai Grid DS1 Grai Grid DS2 Grid Combination VME Grai Grid: DSVME Figur 30 - Combination of two GraiGrids (concpt) To mak th Grai Grid simplr and asir to rad, th following graphical notation is proposd in th following figur. Figur 31 - Combination of two GraiGrids (mockup) A nw tab Entrpris is to b addd in th graphical objct Paltt (right sction of th SLMToolBox in Grai Grid Editor), which contains a graphical objct (rctangl) that dfins th had of vry ntity collaborating in th VME Grai Grid. MSEE Consortium Dissmination: Public 55/143

56 Automatic gnration of VME Grai Grid Th usr of SLMToolBox can modl a VME Grai Grid from scratch or automatically gnrat th VME Grai Grid from xisting Partnrs Grai Grids. For this purpos, two possibilitis ar proposd to th usr whn h starts to crat a Grai Grid for th VME. Ths possibilitis ar proposd thanks to th wizard shown in th nxt figursfigur 32. Th usr can xcut th following stps: Th usr can slct th radio button Crat VME Grai Grid Click to th button Nxt Th list of xisting Grai Grids is proposd. This list is organizd as a tr. Grai Grids ar classifid and structurd by Partnr in th tr. Th usr can slct on or mor Grai Grids Click on th button Finish A VME Grai Grid is cratd from th combination of th slctd Grai Grids. Th usr can add information and dcision flows btwn dcision and information cntrs. Figur 32 - VME Grai Grid Gnration wizard Th following tabl contains th thr grai grids corrsponding rspctivly to th E-Tailr, Bivolino, and DHL Transport Grai Grids in th top row. In th bottom row, is dpictd th VME Grai Grid rsulting from th combination of thr grai grids prviously mntiond. Grai Grid : E-Tailr Grai Grid : Bivolino Grai Grid : DHL Trasport Grid Combination Figur 33 - Combination of 'n' GraiGrids MSEE Consortium Dissmination: Public 56/143

57 F# VME orintd Extndd Actigram Star Editor (BSM Lvl) A VME is an organizational form that marshals mor rsourcs than it currntly has on its own, using collaborations both insid and outsid of its boundaris, prsnting itslf to th customr as on unit. It is a st of (lgally) indpndnt ntrpriss that shar rsourcs and skills to achiv a mission/goal (D11.2). In ordr to modl ths rlations and collaborations btwn partnrs, collaboration diagrams should b dvlopd (wr ncssary) at th various abstraction lvls of th MDSEA (BSM- TIM-TSM). Th Extndd Actigram Star languag modls businss procsss at th businss lvl (BSM), it offrs th concpt of connctors (IntrnalConnctors, ExtrnalConnctors, and ProcssConnctors) which rprsnts collaboration btwn ntitis within th sam organization (singl ntrpris) or btwn diffrnt organizations (partnrs in a VME). But th prsntation of such collaborations is somhow poor and nd to b mor radabl by th SLMToolBox usrs at BSM lvls. This sction is a proposition of Improvd Extndd Actigram Star ditor for a VME orintd Extndd Actigram Star Editor In ordr to raliz th VME orintd Extndd Actigram Star ditor, two options will b laboratd and dtaild Modl collaboration btwn partnrs in on EA* diagram Th usr of th SLMToolBox at BSM lvl is usually awar of th diffrnt procsss that blong to th VME partnrs and th dpndncis btwn thm. As a rsult h is abl to modl this collaboration in a on dtaild EA* diagram. Suppos th usr startd on modling a businss procss which collaborats with othr VME partnrs, using th currnt Extndd Actigram Editor (V2.0.3A), th diagrams would not b abl to rval th collaboration btwn partnrs sinc thr is no graphical rprsntations which diffrntiat btwn activitis blonging to diffrnt partnrs. Figur 34 - EA* diagram in th currnt vrsion of SLMToolBox In th abov EA* diagram two VME partnrs ar collaborating togthr in ordr to provid a support srvic for a spcific product. Partnr 1 is rsponsibl for clint s call rcption, incidnt captur, and incidnt classification btwn functional or tchnical. For any prson rusing th diagram, it is not obvious that it is basd on collaboration btwn two VME partnrs. It is clar that som graphical notations should b addd to rval this collaboration. MSEE Consortium Dissmination: Public 57/143

58 To mak th diagram simplr and asir to rad, th following graphical notation is proposd in th following figur. Figur 35 - EA* diagram with collaboration graphical notations A nw tab VME Partnr is to b addd in th graphical objct Paltt (right sction of th SLMToolBox), which contains a graphical objct (dashd rctangl) that dfins th boundaris of vry ntity collaborating in th diagram Automatic gnration of Collaboration diagrams Anothr option is th automatic gnration of collaboration diagrams starting from an EA* diagram modld for a singl ntrpris. This scnario xplains how to obtain a VME orintd EA* diagrams from a singl ntrpris orintd EA* diagrams: - Th usr of th SLMToolBox modls th procss (dfind in sction 2.1) but within th boundaris of Partnr2 only ; using an Extrnal Connctor objct, rfrncing to a particular procss of Parnr#1 - Figur 36 - EA* diagram in a singl ntrpris - Thn th usr with a right click chooss Gnrat collaboration diagram. MSEE Consortium Dissmination: Public 58/143

59 Figur 37 - right click and choos "Gnrat collaboration diagrams" - Th usr gts his collaborativ diagram basd on th procss rfrncd by th xtrnal connctor. Partnr1 Partnr2 Figur 38 - Gnratd EA* collaboration diagram F# Rus VME assts dscriptions Introduction SP1 modling approach for srvic nginring and SP2 modling approach for assts virtualization may bnfit from ach othr in th sns whr : 1) Th srvic modls dvlopd with SP1 tools may rfrnc xisting virtualizd assts ; in ordr to compos larg srvic modls, involving th participation of svral partnrs, in th contxt of a VME 2) Th SLMToolBox could vntually provid its modling capabilitis for th virtualization of tangibl & intangibl assts toward a smantic data rprsntation format, which would b thn publishd on th MSEE Assts Rpository Currntly, it appars that SP1 / SP2 approachs ar charactrizd by: 3) Two distinct paradigms MSEE Consortium Dissmination: Public 59/143

60 - SP1 : «Modl Cntric» approach for srvic nginring in a singl ntrpris (rquirmnt ; dsign ; implmntation) - SP2 : smantic/ontological approach for assts managmnt in a VME (virtualization ; composition ; xposition ; ) - No intgration btwn «srvic modls» & «assts rprsntations» 4) Two distinct architcturs - Indpndnt procsss (modling / virtualization) - Indpndnt languags (GRAI+UML+BPMN / Linkd USDL) - Indpndnt formats (XMI / OWL) - Indpndnt ditors (SLMToolBox / Protégé) - Indpndnt rpositoris (WP4.2 modl rpository /WP2.6 assts rpository) Mapping: MDSEA Mtamodls / In-Tangibl assts ontology In ordr to valuat th rlvanc / fasibility for intrfacing SP1 modlling tools/procsss with SP2 assts managmnt tools/procsss from th logical prspctiv, w must assss in dtail th actual corrspondnc btwn both information mta-structurs Mapping: BSM Cor / In-Tangibl assts ontology S tabl in: Annx 2 Dtaild dsign - Mapping: MDSEA Mtamodls / In- Tangibl assts ontology BSM Following th dtail of th diffrnt points: For th Procss class, thr is no associatd individual both in th tangibl and intangibl assts ontologis. It is ncssary to add a Procss class undr Tangibl and Intangibl classs in both tangibl and intangibl assts ontologis. Both in tangibl and intangibl assts ontologis, thr is no individual corrsponding to Dcision class. To addrss this lack, it is ncssary to add a Dcision class in th tangibl assts ontology. Lik for th Dcision class, thr is no class corrsponding to DcisionStructur. To rprsnt a dcision structur, it ncssary to add a DcisionStructur class undr th Intangibl class in th intangibl assts ontology. In th intangibl assts ontology, th INDESIT organization is rprsntd an individual with TradMarks typ. This classifir is spcific. To kp th cohrnc with th BSM mtamodl, it is ncssary to add an Organization class in intangibl assts ontology. Both in tangibl and intangibl assts ontologis, thr is no individual and no typ corrsponding to th Customr class. For a srvic objct, th classifir is too spcific. In ordr to rprsnt a srvic in th intangibl tangibl assts ontologis, it is ncssary to add a Srvic class undr th tangibl and intangibl classs. Both for th stakholdr and customr objcts, thr no corrsponding classs in th intangibl and tangibl assts ontologis. Th product class is absnt in th intangibl and tangibl assts ontologis. MSEE Consortium Dissmination: Public 60/143

61 Mapping: TIM Cor / In-Tangibl assts ontology S tabl in: Annx 2 Dtaild dsign Mapping: MDSEA Mtamodls / In- Tangibl assts ontology - TIM Following th dtail of th diffrnt points: In svral cass thr is no association btwn TIM Objct attributs and th individual attributs. In som cass, th classifir is too grric. For xampl, for PhysicalMan individual, th typ Tangibl is too gnric. To addrss this anomaly, it will b important to add a PhysicalMan class undr th Tangibl class. For th Procss class, thr is no associatd individual both in th tangibl and intangibl assts ontologis. It is ncssary to add a Procss class undr Tangibl and Intangibl classs in both tangibl and intangibl assts ontologis. In th intangibl assts ontology, th INDESIT organization is rprsntd an individual with TradMarks typ. This classifir is spcific. To kp th cohrnc with th BSM mtamodl, it is ncssary to add an Organization class in intangibl assts ontology. For a srvic objct, th classifir is too spcific. In ordr to rprsnt a srvic in th intangibl tangibl assts ontologis, it is ncssary to add a Srvic class undr th tangibl and intangibl classs Analysis W can notic that thr is a significant gap btwn th MDSEA mtamodl constructs and th Assts Ontologis concpts. In svral cass thr is no association btwn BSM Objct attributs and th individual attributs. This mans that most of th data modld at BSM lvl can not b transformd in a smantic dscription, compatibl with th In/Tan assts ontologis In som cass, th classifir is too gnric. For xampl, for PhysicalMan individual, th typ Tangibl is vry gnric (to addrss this limitation, on possibility could b adding a PhysicalMan class undr th Tangibl class in th taxonomy). Gnrally, it appars that th taxonomis on which In/tan assts ontologis ar basd on; do not match with th smantic structur of th BSM mtamodl dfind in MDSEA. It mans that BSM objcts cannot b mappd at a dtaild smantic lvl in th in/tan assts taxonomis. MSEE Consortium Dissmination: Public 61/143

62 Extnsion of MDSEA Mtamodls for introprability with In-Tangibl assts ontologis In ordr to rduc th smantic mismatch btwn SP1 modling architctur and SP2 assts rprsntation and improv introprability; svral altrnativs can b considrd. Th most trivial would b to modify dirctly on of th smantic structurs (ithr th MDSEA mtamodls; or th In/tan assts taxonomis) and to align its contnt so that th mapping would b improvd. Anothr approach, which would avoid a strong impact / dpndncy btwn both modling architcturs, would b to laborat an uppr smantic lvl, which rol would consist in managing smantic introprability btwn SP1 and SP2 modling structurs. In this prspctiv, w can imagin that such an uppr smantic lvl could b stablishd, ithr on th basis of a modl drivn approach or an ontological approach. Th following figur brifly suggsts an architctur basd on th modl drivn approach: Figur 39 - Gnric MSEE mtamodl Th proposd solution consists in xtnding th MDSEA mtamodls with an uppr MSEE mtamodl packag ; rsponsibl for th mapping and cohrnc btwn som modling constructs of MDSEA (ithr BSM or TIM lvls) and som ontological constructs of th Intangibl / Tangibl assts ontologis. Th main advantags of this approach would b: - Maintaining th sparation of concrns btwn SP1 modling architctur (focusd on srvic spcification & dsign) and SP2 smantic structurs (focusd on th virtualization and composition of assts for Ecosystms and VMEs) - Fdrating th knowldg dvlopd on th modling sid for srvic nginring purposs and on th ontological sid for srvic virtualization purposs - Acting as a smantic bridg btwn both sids by modling th mapping btwn quivalnt concpts and potntial nriching ths concpts with mor gnric knowldg / mtadata MSEE Consortium Dissmination: Public 62/143

63 Rfrncing VME assts within srvic modls Srvic Modling, at th lvl of th VME could bnfit of th assts dscriptions alrady availabl within th VME. In this approach, a srvic modl, at BSM lvl, could xplicitly rfrnc xisting srvics/assts xposd by th mmbrs of th VME. Thus: th usr of th SLMToolBox would compos srvic modls of th VME from svral assts alrady availabl Sarch & brows th assts rpository In this scnario, usr of th SLMToolBox can import intangibl/tangibl Assts from th asst rpository in ordr to rus thm to nrich BSM modls with rfrnc to xisting assts. To import a dscription of a tangibl/intangibl asst from th USDL Rpository, th usr must to connct first to th USDL Rpository in ordr to sarch and brows it. Th connction to th rpository is carrid out through a connction form Figur 40 - Connct to th Assts Rpository Onc connctd, th rpository can b sarch and browsd through a wizard, according to th accss rights grantd to th usr by th rpository. Figur 41 Brows th assts rpository MSEE Consortium Dissmination: Public 63/143

64 EA*: Rfrnc an xisting asst/srvic, xtndd actigram star procsss Extndd actigram star languag could b xtndd to support th possibility to includ a rfrnc to on or svral virtualizd assts in th sam businss procss modl, at BSM modlling lvl. Thanks to this fatur, a businss usr would hav th possibility to laborat a srvic at BSM lvl, and to spcify how xtrnal assts / srvics would b orchstratd by businss procsss in ordr to dlivr th xpctd srvic. Mor gnrally, such functionality would nabl th laboration of larg srvic modls, which would aggrgat and compos availabl assts in th VME. 1 st Us cas: rfrnc an asst as an activity rsourc Th following scrn mock-ups illustrat how a tangibl asst rfrnc could b importd within an xtndd actigram procss diagram: 1) From th xtndd Actigram graphical ditor, th usr can includ ithr an intangibl or a tangibl asst in th form of a graphical objct Figur 42 - EA* diagram 2) Th following wizards provid a rad accss to th asst rpository, so that th modlr can sarch and slct an appropriat asst to includ in th xtndd Actigram procss modl Figur 43 - Brows asst rpository MSEE Consortium Dissmination: Public 64/143

65 3) Onc slctd, a tangibl asst can b includd in th procss modl, and linkd to a spcific activity on th diagram thanks to a support flow link. In this cas, th cutting machin asst is usd by th dsign shirt activity. Figur 44 - EA* : rfrnc an asst as an activity rsourc 2 nd Us cas: rfrnc an asst as a procss activity In this scond us cas, w propos to rfrnc an intangibl asst (i..: a srvic) as an atomic activity within an xtndd actigram procss modl. In such cas, th ralization of th so calld atomic activity (quivalnt to th task concpt in BPMN languag) would b dlgatd to an xtrnal asst, ownd by on of th mmbrs of th VME F# Publish USDL srvic dscriptions to asst rpository Assts Virtualization procss could bnfit of th data capturd within srvic modls via th SLMToolBox. This would avoid rptition and nforc cohrnc in th procss of dscribing srvics and thir componnts & rsourcs (ithr in th form of Modls SP1 or in th form of virtualizd assts SP2), according to th following scnario: 1) As a singl ntrpris : modl a srvic and th rsourcs involvd (Tool : SLMToolBox ; Format : XMI ; Languag : BSM/TIM modling languags ; Rpository : Modl Rpository) 2) From this srvic modl: xtract th rprsntation of on or svral componnts (rsourcs; srvics;...); dscrib it as an asst (Tool :???) 3) Enrich th rprsntation of th asst ; publish it so that th asst is now visibl by th mmbrs of th cosystm (Tool :??? ; Format : OWL ; Languag : Linkd-USDL ; Rpository : Assts Rpository) W propos to support stps 2 and 3 through an xtnsion of th modlling faturs of th SLMToolBox. In any cas, th dtaild spcifications of ths modlling faturs must b laboratd on th basis of th volutions of th modlling architctur; ndd for improving th smantic compatibility btwn srvic nginring and assts virtualization domains. MSEE Consortium Dissmination: Public 65/143

66 F# BSM2TIM Modl Transformation This transformation has th rol to rus th information collctd at th businss lvl and rprsntd in th form of BSM modls. In rgard to th modlling mthodology dfind in MDSEA, this information must b rusd at th TIM lvl in ordr to procd to th dsign of th srvic and its supporting srvic systm. A modl transformation will support th cration of a TIM modlling projct, basd on an xisting BSM modlling projct. This transformation will consum a BSM srvic systm modl and will produc a nw TIM srvic systm modl, with th information which can b logically mappd from BSM to TIM mtamodls Mapping of BSM and TIM concpts Th following tabl propos a tntativ mapping btwn BSM constructs and TIM constructs. BSM Condition TIM BsmSrvic TimSrvic BsmProcss TimProcss BsmRsourc typ = TimPhysicalManRsourc physicalman typ = IT TimEntrprisApplicationRsourc typ = human TimHumanRsourc BsmOrganization BsmVirtualEntrpris TimOrganization, TimOrganizationUnit BsmEntrpris TimOrganization, TimOrganizationUnit BsmStakholdr, BsmCustomr, BsmValu, (Ths objcts ar not mappd) BsmPartnr, BsmComponnt, BsmFunctionality, BsmDcision, BsmDcisionStructur, BsmPrformancIndicator, BsmVEParticipation Tabl 24 - Mapping BSM mtamodl / TIM mtamodl - W can obsrv that th mapping btwn BSM and TIM modls is only partial. Thr is at last lvn constructs of BSM which hav no corrspondnc at th TIM lvl. W can also obsrv that ach BSM construct that hav a corrspondnc in th TIM lvl, is compltly mappd, so w can rtriv all thir information at th TIM lvl BsmOrganization-BsmProcss rlationship At th BSM lvl a 0 to many rlation xists btwn BsmOrganization concpt and BsmProcss. Th information prsntd by this rlation nds to b prsrvd whn passing from BSM to TIM lvl. But sinc thr is no dirct rlation btwn TimOrganization and TimProcss, th BSMOrganization will b transformd to a TimOrganization composd of a TimOrganizationUnit which possss rfrncs to TimProcsss. Th figur blow provids furthr xplications. BsmOrg is a BsmOrganization with rfrncs to two BsmProcsss. BsmOrg is transformad to TimOrg (of typ TimOrganization) and to OrgUnit (of typ TimOrganizationUnit). Th OrgUnit possss rfrncs to two TimProcsss which ar th rsult of th transformation of BsmProcss1 and BsmProcss2. MSEE Consortium Dissmination: Public 66/143

67 BSM TIM TimOrg BsmOrg OrgUnit BsmProcss1 BsmProcss2 TimProcss1 TimProcss Mockups Figur 45 - BsmOrganization-BsmProcss rlationship Svral wizards will b addd to th SLMToolBox cration wizards in ordr to crat a TIM projct out of an xisting BSM projct. Th following figurs rprsnt a scnario to b followd by th usr: Right click in th projct Explorr viw choos nw / othr Slct Crat a TIM Srvic Systm Modling projct wizard Choos Crat a TM Srvic Systm Modling projct from BSM projct Choos a BSM projct from a list of availabl projcts MSEE Consortium Dissmination: Public 67/143

68 A TIM projct is cratd, with th.tim fil opnd in th TIM ditor F# EA2BPMN Modl Transformation This transformation has th rol to rus th information capturd for businss procss modlling at th BSM lvl and to initializ corrsponding BPMN modls that ar compliant with th OMG spcification in th vrsion 2.0. EA* to BPMN2.0 transformation is a fatur supportd by th SLMToolBox which prforms a vrtical transformation (from BSM to TIM) from an Extndd Actigram Star diagrams (BSM lvl) to BPMN2.0 diagrams (TIM lvl). Th usr chooss an availabl EA* diagram (modld at BSM lvl), and thn transforms it into a BPMN2.0 diagram at TIM lvl. Th usr intrst is to incras productivity through tim saving and to nabl introprability. Th transformation from Extndd Actigram star diagrams into BPMN2.0 diagrams is smiautomatic transformation basd on a mapping that dfins rlations btwn concpts of th modling languags S : Annx 2 Dtaild dsign EA Star to BPMN Collaboration Diagram Modl Mapping S : Annx 2 Dtaild dsign EA Star to BPMN Collaboration Diagram Transformation Ruls Transformation to BPMN collaboration diagram Th mapping of concpts proposd for th transformation crats corrspondncs and links btwn concpts and thir rlations from EA* to BPMN languag. It is a translation of constructs and thir rlations from on mtamodl to anothr. As a rsult, dp analysis and undrstanding of th EA* and BPMN mtamodls, rprsnt th main ky to start in translation and drawing th links. nks MSEE Consortium Dissmination: Public 68/143

69 Illustration of th transformation concpt Th transformation s concpt is dscribd with th support of BIVOLINO s customizd configurator xampl. This xampl dscribs intractions from two diffrnt viws Usr viw: onlin customrs and th E-Tailor wb portal. Systm viw: Bivolino Information systm and th E-Tailor wb portal. Th customizd configurator procss is first modld at th BSM top lvl whr both viws ar modld in th sam EA* diagram. Thn th rsultd EA* diagram is manually dcomposd at th BSM bottom into two sparat diagrams: usr procss and systm procss. Ths two diagrams ar latr transformd using th EA* to BPMN2.0 transformation fatur into a BPMN diagram ach. Th rsultd BPMN collaboration diagrams ar thn rgroupd togthr manually by th usr at TIM top lvl. Finally th rsultd diagram is manually nrichd in ordr to mov from TIM top to TIM bottom. This figur rprsnts th applid scnario in ordr to transform an EA* diagram into a BPMN diagram. Figur 46 - EA* to Collaboration BPMN2.0 scnario MSEE Consortium Dissmination: Public 69/143

70 Th figurs blow dscrib th proposd scnario stp by stp: 1) EA* diagram of th Onlin E-Tailor customr intraction with th E-Tailor wb portal in ordr to buy a customizd shirt onlin: 2) EA* diagram of th Bivolino information systm intraction with th E-Tailor wb portal for th buy a shirt onlin procss. Th Bivolino information systm is rsponsibl to provid th customizd configurator and th rgistration of th chosn product configurations: 3) automatic transformation of th usr viw EA* diagram into a collaboration BPMN2.0 diagram 4) Automatic transformation of th systm viw EA* diagram into a collaboration BPMN2.0 diagram 5) Mrging of th two rsulting BPMN2.0 diagrams 6) Manual nrichmnt in ordr to pass into TIM bottom lvl MSEE Consortium Dissmination: Public 70/143

71 Scrn mockups In ordr to crat a Collaboration BPMN2.0 diagram (TIM) from an xisting EA* diagram (BSM) using th SLMToolBox, th following scnario should b followd by th usr: 1) Right click on th TIM projct (or th procss : 2) Slct crat BPMN2.0 Diagram, 3) Two options ar availabl, ithr to crat a BPMN2.0 diagram from xisting EA* diagram or to crat a nw on from scratch. Th usr slcts th first option and thn clicks nxt: 4) Two typs of BPMN2.0 diagrams ar availabl: Collaboration and Procss diagrams. Th usr slcts Crat a Collaboration BPMN2.0 diagram thn click nxt MSEE Consortium Dissmination: Public 71/143

72 5) A list of all availabl Extndd Actigram Star diagrams is displayd. Th usr slcts a diagram and click finish: 6) A Collaboration BPMN2.0 diagram is cratd, placd in its corrsponding TIM projct, and opnd in th BPMN2.0 ditor Transformation to BPMN procss diagram In th EA* to BPMN2.0 transformation fatur, th usr can choos two typs of BPMN2.0 diagrams: Procss and Collaboration diagrams. Th advantag of a modl transformation aiming at crating BPMN procss diagrams is to provid compatibl BPMN modls with th BPM modul of th Innovation Ecosystm Platform. So that such procss diagrams can b nrichd, dployd and xcutd on th IEP. Th mapping of concpts proposd from EA* to Procss BPMN2.0 diagrams diffrs from that to Collaboration BPMN2.0 diagrams du to th diffrnc in th natur of th two diagrams. Th mapping is accompanid with conditions which govrns th cration of rlations btwn concpts. S : Annx 2 Dtaild dsign EA Star to BPMN Procss Diagram Modl Mapping S : Annx 2 Dtaild dsign EA Star to BPMN Procss Diagram Modl Mapping Scrn mockups Similarly to th prvious transformation (from Extndd Actigram Star to Collaboration BPMN diagram); in ordr to crat a Procss BPMN2.0 diagram (TIM) from an xisting EA* diagram (BSM) using th SLMToolBox, th following simplifid scnario should b followd by th usr: 1) Right click on th TIM projct (or th procss : 2) Two typs of BPMN2.0 diagrams ar availabl: Collaboration and Procss diagrams. Th usr slcts Crat a BPMN2.0 procss diagram : MSEE Consortium Dissmination: Public 72/143

73 3) A Procss BPMN2.0 diagram is cratd, placd in its corrsponding TIM projct, and opnd in th BPMN2.0 ditor F#1.12 Grai Nts Modling Editor (BSM lvl) Th GRAI Nts rprsnt th xcution of th whol or a part of a dcision cntr according to th GRAI modling concpts (modl of a dcision cntr activitis) (Vallspir, Mrl, & Doumingts, 1992) (Vallspir, Mrl, & Doumingts, 2002) Graphical notation Th following tabl shows th constructs of th graphical syntax of th languag. Elmnt Dscription Notations Activity Part of th bhaviour of a dcisionmaking cntr. An activity is dynamic and provids on or mor ntitis. Th activitis ar namd and numbrd. Excution Dcision Entity Rfrnc oprators Physical or abstract objct that blongs to th control systm. Th ntitis ar ncssary to th cours of th activitis or ar producd by thos ons. Th ntitis ar namd. Rfrnc oprators ar usd whn it is ncssary to indicat th origin or th dstination of an ntity whn this origin or this dstination is xtrnal with th diagram. Squntial link Tim rlationship btwn activitis MSEE Consortium Dissmination: Public 73/143

74 Logical oprators Projct ID AND Oprator Paralll fork or join Fan-in Fan-out OR Oprator Inclusiv fork or join Fan-in Fan-out Modlling ruls Activity Thr ar two kinds of activitis: Excution: it a dtrministic activity and giv th sam valu to th rsult for th sam valus of th convrgnt ntitis (triggr and supports). Exampl: activity managd compltly by a rul, procdur, programm, tc (s ). Figur 47 An xcution activity Dcision: it is an activity bing abl to giv svral valus to th rsult for th sam valus of th convrgnt ntitis. Exampl: choic of a solution in uncrtain contxt (s) Figur 48 Dcision activity Entity Thr ar svn naturs of ntitis: Objctiv: Lvl of prformanc attndd aftr th ralization of th activity. Dcision variabls: Elmnt on which on can play during th activity implmntation. Critrion: Hlp to th choic of th actions on th dcision variabls. Ruls: Spcification of th bhaviour of an activity or a part of this on. MSEE Consortium Dissmination: Public 74/143

75 Prformanc indicator: Rport on a prformanc. Information: Entity of informational natur unspcifid. Rsourc: Concrt mans, tchnical or human, ncssary to th implmntation of th activity. Thr rols ar possibl for an ntity as shown in : Rol Dscription Notations Support Entity rquird for th progrss of an activity. Rsult Triggr Entity producd by an activity Entity rquird for th progrss of an activity and of which th disposal triggrs th activity. - Th triggr of an activity can also consist of an xognous logical condition. In this cas, this on is indicatd as an ntity triggr. - Th triggr can also consist in th priod of th lvl whr th dcision cntr is locatd. In this cas, no triggr is mntiond Rfrnc oprators Tabl 25 - GRAI Nts - Entity Rols Rfrnc oprators ar usd whn it is ncssary to indicat th origin or th dstination of an ntity whn this origin or this dstination is xtrnal with th diagram (s ). Origin Dstination Tabl 26 - GRAI Nts - Rfrnc oprators Situations for which ths oprators ar ncssary: R: numbr of th nt, A: numbr of th origin or dstination activity R/A: nam of th systm or srvic out of th study domain whn an ntity circulats btwn th studid systm and its nvironmnt, whn an ntity circulats from on dcision cntr to anothr on, whn th nt is too larg to ntr on a pag Logical oprators It appars combinations or dcompositions in th GRAI nts which rsult in divrgncs and convrgncs into AND and OR, from ntitis to activitis and rciprocally. Ths situations ar rprsntd by logical oprators. Th rprsntation of ths oprators follows th gnral rul: AND ar rprsntd by doubl faturs ( ) OR ar rprsntd by simpl faturs ( ) MSEE Consortium Dissmination: Public 75/143

76 GRAI Nts Editor Scrn mockup Th following figur illustrats th intgration of th GRAI Nts Editor within th SLMToolBox modling nvironmnt Mtamodl Figur 49 - Grai Nts Editor - Scrn Mockup Th following givs a rprsntation of th Grai Nts mtamodl. S figur in: Annx 2 Dtaild dsign Mtamodl Grai Nts Mapping with BSM mtamodl & GraiGrid mtamodl Th following figur illustrats th intgration of th Cor Constructs of th BSM modlling lvl with th GraiGrid and GraiNts languags. S figur in: Annx 2 Dtaild dsign Mtamodl Mapping Grai Nts / BSM / Grai Grid W can notic that: Thr constructs of BSM ar dpndnt on th corrsponding constructs in th GraiGrid Languag. Two constructs of BSM ar dpndnt on th corrsponding constructs in th GraiNts Languag. On constructs of GraiGrid is dpndnt on th corrsponding construct in th GraiNts Languag. MSEE Consortium Dissmination: Public 76/143

77 5.5. Srvic nginring faturs F#2.1 Light Businss Procss simulation This sction will laborat on th SLMToolBox light businss simulation fatur, by giving a brif introduction about srvic and procss simulations, simulation critria, Existing businss procss simulation tools, and th simulation scnario proposd for this fatur Introduction to simulation, in th contxt of modling Onc a srvic is dsignd or modld, its implmntation may b capabl of dlivring th dsird output but not for th xpctd cost or within th dsird timfram. Also, a srvic that has bn dsignd may b functional but may not b optimal. Th analysis and undrstanding at th dsign stag of th srvic hlp in its optimization. Simulation is th procss of virtualizing ral world modls in ordr to tst thir corrctnss, ffctivnss and fficincy in rspons to spcific problm spac. It is composd of xprimnts in ordr to dtrmin how th systm can b improvd, volvd, and to intrprt how futur changs will affct th modld systm. Aftr problm dfinition, abstraction and modling, th modl can thn b run and tstd to assss its bhavior in particular circumstancs, i.. whn particular objcts and ntitis in th modl ar givn particular valus. Rsults ar thn intrprtd, analyzd, and thn dcisions to rach modl and systm optimization. A simulation modl should incorporat th prformanc dimnsions on is intrstd in. In most cass it should b possibl to simulat tim and cost aspcts. Othr rlvant prformanc dimnsions ar quality and flxibility. Simulation oftn posssss svral limitations: - Simulation dos not gnrat th solution tchniqus - Modls ar somtim, xpnsiv, and tak a long tim to dvlop - Modls do not produc answrs by thmslvs - Not all situations can b valuatd - Th usr has to provid all th constraints for th problm which h wants to xamin Simulation in MDSEA At BSM (Businss Srvic Modl) lvl two distinct viws of th srvic can b laboratd: - Static viw (formalism : GraiGrid) Functions ; Dcisions lvls ; Flows ; Objctivs & PIs - Dynamic viw (formalism : Extndd Actigram Star) Procss xcution squnc Usr/Systm intraction Static modl is mor structural than bhavioral, hlps in dpicting static constitunts of th systm, rigid as it is tim indpndnt viw of a systm, and can t b changd in ral tim. On th othr hand, a Dynamic modl is a rprsntation of th bhavior of th static componnts of th systm, and consists of a squnc of oprations, stat changs, activitis, and intractions. Dynamic modl is flxibl as it can chang with tim as it shows what an objct dos with many possibilitis that might aris in tim. As a rsult, in ordr to simulat a srvic systm, simulations will b built on th basis of Businss Procss modls and in spcific on th dynamic Extndd Actigram Star diagrams. MSEE Consortium Dissmination: Public 77/143

78 Ths simulations will b basd on crtain critria: - Tim (stimation of th tim ndd for a procss xcution, and of tasks within this procss. W should distinguish hr btwn: minimum stimatd tim, maximum stimatd tim, and avrag procss stimatd tim ) - Cost (th cost is rprsntd by th cost of rsourcs allocatd for th procss s xcution ) In addition th srvic s quality is assssd through th valuation of tim and cost critria from on sid and srvic s objctivs on th othr sid. Th valuation of quality as a function of tim, cost and objctivs will b laboratd latr in sction (Simulation fatur) Businss Procss Simulation (BPS) Businss procsss ar in a continuous improvmnt cycl in which dsign and rdsign play an important rol. Various possibilitis to chang a procss ar prsnt and th bst altrnativ dsign should rplac th currnt procss. Making an intuitiv choic may lad to unplasant surpriss and lowr procss prformanc instad of yilding th xpctd gains. Simulation is on of th tchniqus suitabl for th support of rdsign. Th simulation of businss procsss hlps in undrstanding, analyzing, and dsigning procsss. With th us of simulation th (r)dsignd procsss can b valuatd and compard. Simulation provids quantitativ stimats of th impact that a procss dsign is likly to hav on procss prformanc and a quantitativly supportd choic for th bst dsign can b mad Gnral Simulation critria Businss procss simulation is basd on svral critria or indicators which should b idntifid bfor running any simulation. Ths indicators rprsnts inputs to simulation modls which would b procssd by th simulation ngin. - Procss duration: Procss duration is th tim from th start of th procss till its nd. From a customr prspctiv it is th tim from th rqust till th dsird rsult is rachd. - Waiting tim: Transfrring goods (or papr) from on machin (or dsk) to anothr can tak som tim. During this tim th procss is idl and waits. Ths tims ar oftn not includd in businss procss modls. And if all rsourcs (popl or machins) ar busy, th procss has to quu. During this tim it is idl again. Waiting tim is oftn not modld. - Procssing tim: This is th total tim spnt in diffrnt activitis. - Procss costs: Th sum of all costs causd by th run of a singl procss instanc. Basically w can idntify two typs of costs: Popl prforming a human activity (mploy costs), rsourcs ndd to fulfill a human or automatd activity (matrial costs). - Rsourc utilization: If th maximum numbr of rsourcs is givn, it is possibl to calculat th utilization from historical data Existing Businss Procss Simulation tools ARIS ARIS Simulation is a profssional tool for th dynamic analysis of businss procsss. It is an intgral part of th ARIS Toolst; procsss rcordd in th ARIS Toolst ar usd as th data basis for businss procss simulation. ARIS Toolst is dvlopd by IDS Schr AG (s and can b classifid as an ntrpris modlling tool with a strong mphasis on businss procsss. Entrpris modlling is supportd by a numbr of diffrnt MSEE Consortium Dissmination: Public 78/143

79 viws (procss, function, data, organization and product) and th modlling approach calld ARIS Hous. Th procss modlling part supports th dfinition of businss procsss rprsntd in Evnt-drivn Procss Chains (EPCs). Othr modlling tchniqus supportd in th ARIS Hous ar,.g. valu chains (also to modl th control flow), organization charts (to modl rlationships btwn rsourcs), EPCs and and function allocation diagrams (for supplmntary information such as data and systms). Th simulation functionality shows whthr th spcifid procsss ar xcutabl at all and it answrs qustions about throughput tims and utilization lvls of th rsourcs, tc. Whn starting a simulation, th simulation modul of th tool is startd and th modl is transfrrd. Th simulation toolbar shows buttons for start and stop, on tim stp and simulation stps and options for animations. Th simulation rsults ar availabl in Excl spradshts and includ statistics on vnts, functions, rsourcs, procsss and costs. Only raw data is availabl. Protos Protos is a modlling and analysis tool dvlopd by Pallas Athna and it is mainly applid for th spcification of in-hous businss procsss. Protos is suitabl to modl wll-dfind Ptri Nt structurs. Nvrthlss, it also prmits fr hand spcifications of businss procsss without formal smantics,.g. to support initial and concptual modlling. Whn formal Ptri Nt smantics hav bn applid, translation to various othr procss-basd systms is fasibl as wll,.g. to th workflow managmnt systm COSA and th workflow analyzr Woflan. Th main us of Protos is to dfin modls of businss procsss as a stp towards ithr th implmntation of quality managmnt systms, th rdsign of a businss procss, communication nhancmnt btwn procss stak holdrs or th implmntation of workflow managmnt systms. Th procss can b analyzd with rspct to data, usr and control logic prspctiv, and by making us of simulation. Th simulation ngin is implmntd in Protos vrsion 7.0. Th xisting ngin of th Ptri Nt basd tool ExSpct has bn intgratd in th Protos nvironmnt and it facilitats th simulation of th businss procss as has bn spcifid in th Protos modl bfor. In addition to th standard procss spcification, simulation data can b addd for tasks, connctions and rsourcs such as th (stochastic) procssing tim and th numbr of rsourcs rquird. Furthrmor, procss charactristics ar addd such as th arrival pattrn for cass and th numbr and lngth of simulation runs. Th simulation rsult can b obtaind from an Excl spradsht and includs man and 90% and 99% confidnc intrval of utilization rats, waiting tims, srvic tims, throughput tims and costs. Arna Arna is a gnral purpos simulation tool dvlopd by Rockwll Automation. Th Arna product family consists of a Basic Edition for uncomplicatd procsss and a Profssional Edition for mor complx larg scal projcts in manufacturing, distribution, procsss, logistics, tc. Th Profssional Edition also provids (and allows dfinition of) tmplats for complx rptitiv logic,.g., for packaging and contact cntrs. Whn opning th tool, a numbr of procss panls ar availabl,.g., for basic and advancd procsss and for rporting. Th modl can b cratd by drag and drop from th procss panl to th modl window. By doubl-clicking on th icons, options for th diffrnt building blocks can b st such as dlay typs, tim units and th possibility to rport statistics. Many mor building blocks ar availabl and can b attachd whn ncssary. Whn a modl has bn cratd and is compltly spcifid (from th Arna viwpoint) and it is syntactically corrct, it can b simulatd.warm-up and cooldown priods can b spcifid, as wll as run lngth and confidnc intrvals. MSEE Consortium Dissmination: Public 79/143

80 Svral statistics ar providd by dfault, but th largr part nds to b addd manually by adding rcord building blocks whr ncssary. In a prvious study, d Vrd t al considrd th suitability of Arna to simulat businss procsss. Thy statd that a wak point in simulating businss procsss is th tim consuming and complicatd procss to crat simulation modls. Thy took advantag of th possibility to dvlop thir own tmplat with prdfind building blocks, which thy considrd to b succssful in svral simulation studis thy carrid out. Jbpm JBoss jbpm is a vry flxibl businss procss ngin which is availabl undr th opn sourc LGPL licns2. Th cor of jbpm is a light-wight, xtnsibl workflow ngin writtn in pur Java that allows you to xcut businss procsss using th latst BPMN 2.0 spcification. It can run in any Java nvironmnt, mbddd in your application or as a srvic. On top of th cor ngin, a lot of faturs and tools ar offrd to support businss procsss throughout thir ntir lif cycl: - Eclips-basd and wb-basd ditor to support th graphical cration of your businss procsss (drag & drop) - Pluggabl prsistnc and transactions basd on JPA / JTA - Pluggabl human task srvic basd on WS-HumanTask for including tasks that nd to b prformd by human actors - Managmnt consol supporting procss instanc managmnt, task lists and task form managmnt, and rporting - Optional procss rpository to dploy your procss (and othr rlatd knowldg) - History logging (for qurying / monitoring / analysis) - Intgration with Sam, Spring, OSGi, tc. BPM maks th bridg btwn businss analysts, dvloprs and nd usrs, by offring procss managmnt faturs and tools in a way that both businss usrs and dvloprs lik it. Domain-spcific nods can b pluggd into th paltt, making th procsss mor asily undrstood by businss usrs. jbpm supports adaptiv and dynamic procsss that rquir flxibility to modl complx, ral-lif situations that cannot asily b dscribd using a rigid procss. W bring control back to th nd usrs by allowing thm to control which parts of th procss should b xcutd, to dynamically dviat from th procss, tc. jbpm is also not just an isolatd procss ngin. Complx businss logic can b modld as a combination of businss procsss with businss ruls and complx vnt procssing. jbpm can b combind with th Drools projct to support on unifid nvironmnt that intgrats ths paradigms whr you modl your businss logic as a combination of procsss, ruls and vnts. jbpm5 is th latst community vrsion of th jbpm projct. It is basd on th BPMN 2.0 spcification and supports th ntir lif cycl of th businss procss (from authoring through xcution to monitoring and managmnt). Th currnt jbpm5 snapshot offrs opnsourc businss procss xcution and managmnt, including - mbddabl, lightwight Java procss ngin, supporting nativ BPMN 2.0 xcution - BPMN 2.0 procss modling in Eclips (dvloprs) and th wb (businss usrs) - procss collaboration, monitoring and managmnt through th Guvnor rpository and th wb consol - human intraction using an indpndnt WS-HT task srvic - tight, powrful intgration with businss ruls and vnt procssing MSEE Consortium Dissmination: Public 80/143

81 Bonita Opn Solution BonitaSoft is a lading BPMS solutions (workflow) proposd in OpnSourc mod, locatd in Franc, China and th USA and is rprsntd in mor than 20 countris through its ntwork of partnrs. BonitaSoft is th publishr of Bonita Opn Solution, a platform BPMS (businss procss modling simulation). Bonita Opn Solution BPM suit is th most world downloadd opn with mor than 500,000 downloads in arly It combins thr solutions in on: an innovativ Studio for procss modling, a powrful BPM and workflow ngin, and a brakthrough usr intrfac. Standard simulation capability availabl in Bonita Opn Solution allows to load paramtrs and provids xcution simulation rports. Advancd simulation capability availabl that gnrats simulation rports without rqusting any input, and provids indications usful for improving th procss Tools valuation Th valuation of th prvious simulation tools is basd on four basic aspcts: - BPMN2.0 compatiblity - simulation capabilitis: possiblity to simulat tim and cost aspcts us of diffrnt simulation scnarios animation or rplay of th simulation - rsult analysis capabilitis: statistical rsults asy to rad formats - product s licns typ: opn sourc Th following tabl summarizs an valuation of th tools with rspct to th dfind critria. Tool critria BPMN2.0 compatibl tim/cost simulation simulation scnarios simulation animation statistical rsults asy to rad formats opn sourc Not supportd Partially supportd Supportd ARIS Protos Arna Jbpm Tabl 27 - Evaluation of Businss Procss Simulation Tools Bonita Opn Solution MSEE Consortium Dissmination: Public 81/143

82 From th abov valuation and dpnding on th chosn critria, on can conclud that Bonita Opn sourc (BOS) is th tool which fulfill th bst our valuation critrias. It is an opn sourc tool, compatibl with th BPMN2.0 OMG spcifications, provids tim and cost simulations, svral simulation scnarios can b xcutd with simulation priods dfinition, th output of th simulation is in th form of statistical rsults which allows th comparison and analysis of rsults, and th rports formats ar asy to rad (PDF and HTML) SLMToolBox Simulation Scnario In ordr to simulat a businss procss using th light businss simulation fatur th following scnario should b followd: 1) Th usr is supposd to modl his businss procss at BSM lvl using th Extndd Actigram Star (EA*) ditor (or simply h can us an xisting EA* diagram which rprsnts his businss procss). Figur 50 - Simulation Scnario - Sourc Extndd Actigram Procss Diagram Th procss modld is a call srvic in an ntrpris which provids support to it s clints who ar facing problms using th ntrpris s product. Th procss is composd of thr tasks: captur incidnt, classify incidnt, and snd msg to clint. A managr is rsponsibl for th xcution of th thr tasks (th whol procss), and an IT systm participats in th xcution of th snd msg to clint. First th procss starts by capturing an incidnt which corrsponds to answring a clint s call and taking all information concrning th problm h facd. Th incidnt is thn classifid (tchnical or functional problm). Finally a msg is snd to th clint informing him about th rason of his problm and how it can b solvd. MSEE Consortium Dissmination: Public 82/143

83 2) Aftr modling th businss procss using EA* ditor, th modl is transformd into a BPMN2.0 diagram and thn opnd with BONITA BPMN procss dsignr Figur Simulation Scnario - Businss Procss within Bonita procss dsignr 3) Th nxt stp consists to injct simulation paramtrs into th procss. Th usr starts by allocating rsourcs to th procss. In this xampl, thr ar two typs of rsourcs th rcptionist_wk and incidnt_analyst Th attributs of a rsourc ar as follow: Nam: rsourc s nam. Quantity: rsourc s quantity availabl for th procss s xcution Targt quantity: th targt quantity th usr is trying to rach for th procss s xcution Cost currny: choos th cost currny of th rsourc from th list Cost by utilization: th rsourc s cost for vry utilisation Cost by unit tim: th rsourc s cost which can b by hour minut, hour, day, wk, month or yar MSEE Consortium Dissmination: Public 83/143

84 Aftr th allocation of rsourcs for th procss and dfining it stimatd xcution duration, it is tim to injct simulation paramtrs into tasks and flows. Th usr stimats xcution duration and maximum xcution tim of vry task and allocats th ncssary rsourcs. 4) Bfor starting th simulation, th usr should crat a simulation profil in ordr to dfin th: numbr of instanc to b injctd during th simulation simulation priod Figur 52 - Simulation Scnario - Simulation Profil MSEE Consortium Dissmination: Public 84/143

85 5) Finally th simulation can b xcutd, th usr chooss a simulation profil, th sampling intrval (for xampl th usr chooss to tak a sampl of th simulation vry 4 hours), and clicks on th run button. Figur Simulation Scnario - Simulation launch 6) A rport is producd at th nd of th simulation, which is of html and pdf format. Inaddition all graphs usd in th rport ar stord in on foldr. Th rport is basd on statistics prsntd in th form of graphs, which contains th following information: Excution tims (Minimum, avrag, maximum, and maximum thrshold) of simulatd procss instancs through th total simulation timspan. Figur 54 - Simulation Scnario - Excution tims (1) From this graph, w can notic that during th day th procss is not ovrchargd and working normally. But som calls had arrivd just bfor 19h:00 (rsourc s working hours ar from 8h00 to 19h00), and thus ths calls wr not tratd until th nxt day which xplains th incras in xcution tim at night. Changing th numbr of instancs for diffrnt simulations will affct th rsults shown in th graphs blow and thus can giv a global ida about th optimal numbr of instancs that can b tratd with rspct to a prstimatd xcution tim. Task xcution tim: from th task xcution graphs w can notic which task is ovrchargd and thus affction th ovrall xcution tim of th procss. MSEE Consortium Dissmination: Public 85/143

86 F#2.2 Availability of rfrnc modls A library of rfrnc modls should b built with th hlp of th SLMToolBox, so that a nw usr would b abl to choos and rus a pr-initializd modlling projct; in ordr not to start th modlling from scratch and bing guidd by rlvant modl tmplats. Such fatur has no impact on th SLMToolBox on itslf as it dos not rquir any nx softwar fatur to provid thr rfrnc modls. Th laboration of rfrnc modls by th scintific partnrs of SP1 will also srv as a qualification phas for th SLMToolBox softwar. Whn finalizd, such modls will b uploadd on th modl rpository with appropriat accss rights; usrs can brows / sarch and download ths rfrnc modling projcts from th modl rpository browsr within th SLMToolBox nvironmnt F#2.3 Srvic nginring mthodology A simpl usr guid should b laboratd, basd on th srvic nginring mthodology dvlopd by IAO and strongly connctd to th functionalitis of th SLMToolBox in ordr to driv th modlling activitis accordingly to th stps of th srvic nginring mthod. Such usr guidanc could b achivd in two possibl forms: 1) A raw usr documntation prsnting th srvic nginring mthod modls and rlatd scrnshots of th SLMToolBox. 2) A dynamic and contxtual hp, dirctly intgratd within th SLMToolBox modlling ditors. In th lattr cas, a contxtual hlp modul could b addd to th SLMToolBox so that th usr can b guidd along th modlling phass supportd by th softwar tool. Eclips Hlp Modul Figur 55 - Eclips nvironmnt - Hlp modul MSEE Consortium Dissmination: Public 86/143

87 5.6. Srvic govrnanc faturs F#3.1 KPI dscription wizards Th figur bllow dpicts th MSEE PI mthod phass and us cass associatd to ach phas. Figur 56 MSEE PI mthod Th SLMToolBox will covr th first four phass. Th following sctions giv th dtail of ach us cas Crat GRAI Grid Diagrams This scnario is supporting th usr in th cration of a nw Grai Grid diagram. In this cas, th platform will dlgat th xcution to th grai grid ditor componnt. A 2 stp wizard will ask th usr to ntr or slct an ntrpris nam and to ntr or slct th nam of th grai grid. For this, drop-down lists will b populatd with th nams of xisting organizations and dcision structur of th BSM modl, attachd to th currnt BSM Modling projct. MSEE Consortium Dissmination: Public 87/143

88 Add an Objctiv in a Dcision cntr This scnario supports th cration of on or svral Objctivs objt pr Dcision Cntr in a GRAI Grid Diagram. To add a nw dcision variabl, th usr can xcut th following stps: Slct a dcision cntr Slct th objctivs, dcision variabls and KPIs tab in th bottom part of th Usr Intrfac Th tab is dividd in two parts. Th first part contains th objctivs associatd to th dcision cntr. Th scond part givs th dscription of th slctd objctiv in th objctiv list Th usr can rmov an xisting objctiv by clicking on th button Th usr can modify th nam, cod and dscription of th slctd objctiv Th usr can add a nw objctiv by clicking first on th button. Two cass ar possibl to add an objctiv. o In th first cas, th usr can slct an xisting objctiv. This functionality allows th usr to rus th xisting objctivs alrady spcifid for othr dcision cntrs in th Grai Grid o In th scond cas, th usr can dfin a nw objctiv from scratch. A form is proposd and th usr can fl th rlvant information. MSEE Consortium Dissmination: Public 88/143

89 Add a dcision variabl This scnario supports th cration of on or svral Dcision variabls objt pr Objctiv associatd to a Dcision cntr in a GRAI Grid Diagram. To add a nw dcision variabl, th usr can xcut th following stps: Slct a dcision cntr Slct th objctivs, dcision variabls and KPIs tab in th bottom part of th Usr Intrfac. Th tab is dividd in two parts. Th first part contains th list of objctivs associatd to th slctd dcision cntr. Th scond part contains th dscription (Nam, Cod, Dscription and th dcision variabls) of th currnt objctiv. Click on th button to add a dcision variabl. Two possibilitis ar proposd. o Th first possibility allows th usr to slct an xisting dcision variabl. For this purpos, a st of xisting dcision variabls is proposd as a list box. So, th usr can slct a dcision variabl in th list and click on th button Finish to validat th choic. o Th scond possibility aims to add nw dcision variabl from scratch. In this cas, th usr must click on th button Add nw dcision variabl and to fill-in th dscription of this lattr thanks to th form dpictd in th following figur : Th usr can rmov an xisting objctiv by clicking on th button MSEE Consortium Dissmination: Public 89/143

90 Add a Prformanc Indicator in a Dcision variabl This scnario supports th cration of on or svral Prformanc Indicators objt pr Dcision Variabl associatd to an Objctiv of a Dcision cntr in a GRAI Grid Diagram. This figur givs an ovrviw of th wizard usd to add nw dcision variabls. To add a nw dcision variabl, th usr can xcut th following stps: Slct a dcision cntr Slct th objctivs, dcision variabls and KPIs tab in th bottom part of th Usr Intrfac Slct an objctiv Slct a dcision variabl Click on th button to add a KPI. Two possibilitis ar proposd o Th first possibility allows th usr to slct an xisting KPI. For this purpos, a st of xisting KPIs is proposd as a list box. So, th usr can slct a dcision variabl in th list and click on th button Finish to validat th choic o Th scond possibility aims to add nw KPI from a rfrnc list (VRM). So, th usr can sarch th dscription of th KPI in a KPI rfrnc List by clicking on th button Sarch a KPI. In this list, KPIs ar classifid pr catgory and domain : MSEE Consortium Dissmination: Public 90/143

91 o Th usr can also crat nw KPIs from scratch by clicking on th button Add nw KPI and fill-in th KPI dscription: Th usr can rmov an xisting KPI by clicking on th button MSEE Consortium Dissmination: Public 91/143

92 5.7. Intgration faturs F#1.03 Intgration with WP4.2 modl rpository Contxt Th first rlas of th SLMToolBox (M12) providd its own prototyp implmntation of th modl rpository, as th official modl rpository wr plannd to b dlivrd by WP4.2 at M18. Th initial choic was to rly on th CDO (Connctd Data Objcts) ( as xplaind in th D15.2 ( Modl prsistnc and sharing). It appard that this tchnology would imply som limitation for its intgration as th basis for th MSEE Modl Rpository, dlivrd by WP4.2. Th atomicity lvl of th CDO modl rpository is at th objct lvl. This lvrag powrful faturs for th managmnt of larg and cntralizd modls; but this also implis that th modlling ditors manipulating th modls objcts ar awar of th CDO prsistnc mchanism and implmnt spcific intrfacs Limitations of CDO In trm of intgration, it mans that any MSEE tool/componnt/modul accssing th modl rpository must implmnt th CDO clint API in ordr to manipulat (rtriv / stor) modl contnt on th modl rpository. This is dfinitly a limitativ approach as th tools dvlopd on th basis of th Eclips Platform (SLMToolBox ; Gnric Srvic Dvlopmnt platform ; Mobil platform dvlopmnt modul) cannot bnfit of most of th clips modlling ditors (.g. : Papyrus UML ; BPMN2.0 ; ) as ths componnt do not (yt) intgrat nativly with th CDO tchnology. WP4.5 mad th choic of rplacing th modl rpository implmntation, with a mor opnd prsistnc paradigm which would dcoupl th managmnt of modls objcts within th modlling tools and within th modl rpository. This mans that th modl artfacts would b now managd at th lvl of modl in th rpository Intgration with WP4.2 modl rpository Rgarding th SLMToolBox, this choic has a significant tchnical impact on th prsistnc managmnt layr of th modlling nvironmnt, in trm of dvlopmnt rwork. Figur 57 - UML componnt diagram SLMToolBox / GSDv Intgration This figur dpicts th tchnical architctur, which aims at supporting th intractions btwn th modl rpository and th SLMToolBox. MSEE Consortium Dissmination: Public 92/143

93 Scrn mockups Th following scrnshot illustrats th intgration of th modl rpository clint within th nvironmnt of th SLMToolbox. Figur 58 - Intgration of th modl rpository clint viw Th clint modul is providd by SINGULAR as a componnt of th Dvlopmnt Platform, in th form of an clips plugin. Onc intgratd within th SLMToolBox, it is accssibl through a graphical viw, offring th following functionalitis: Stup a connction to a modl rpository srvr instanc Brows th modl rpository contnt Crat / dlt foldrs on th modl rpository Upload / download modl fils on / from th modl rpository MSEE Consortium Dissmination: Public 93/143

94 6. Tchnical dsign 6.1. Tchnical rquirmnts and slctd tchnologis Tchnical platform Th tchnical platform must fulfill th following rquirmnts: To b opn, modular and xtnsibl Rly on bst of brd opn sourc tchnologis Eas th intgration with third party MSEE IT platforms and tools Th Eclips Platform rmains th main tchnical foundation for th SLMToolBox nvironmnt. Considring its background in rsarch projcts, th larg community supporting th dvlopmnt of th cor platform and its rich cosystm of plugins, th Eclips Platform ( is considrd as on of th most viabl opn sourc solutions for building domain spcific modling nvironmnts (Danil Amyot, 2006) Modl manipulation In this approach, th Eclips Modling Framwork EMF ( provids a modling infrastructur for dscribing mtamodls and diting modls with th hlp of Ecor format and cod gnration facilitis. Furthrmor, EMF is usd as a foundation by numrous clips projcts, which addrss diffrnt aspcts modling activitis (transformation, prsistnc, diting, visualization ) and that can provid good support for th implmntation of th main faturs of th modling nvironmnt Rich usr intrfacs Whil EMF nativly provids basic diting facilitis for Ecor modls, th Extndd Editing Framwork EEF ( aims at providing nw srvics ddicatd to diting and using mor appaling diting lmnts for EMF modls. As EMF, EEF rlis on a gnrativ approach to provid advancd diting srvics. This approach is particularly suitd for domain spcific mtamodls which do not dfin graphical formalisms to rprsnt modls. In th cas of MSEE, BSM and TIM mtamodls ar dfind as th spcific cor of srvic systm modling, and nd to b ditabl via a rich intrfac, whil no graphical formalism is dsignd for th rprsntation of BSM and TIM modls. Thus, w propos to provid a st of diting faturs, allowing visualizing th BSM and TIM modls undr th form of a tr viw and a st of forms to dit thir structur and attributs. In this cas, EEF prforms as a good candidat, to provid spcific diting faturs for BSM and TIM modl constructs Graphical modl diting As prsntd and valuatd in th prvious sction, Graphiti ( offrs powrful mans for building graphical diagrams ditors upon EMF basd domain modls. Graphiti provids a st of common usr orintd faturs out of th box such as diagram layout, undo/rdo actions, kyboard shortcuts handling, rich graphical objct dsign ; which allow th dvlopr to focus on domain spcific cod. Furthrmor, it provids convnint xtnsion points to intgrat Graphiti ditors in a larg Eclips application. MSEE Consortium Dissmination: Public 94/143

95 Modl transformation In svral us cass, th modling ditor of th SLMToolBox will hav to support spcific modl transformations, mostly to support th continuity btwn th srvic concpts & rquirmnts phas to th srvic dsign phas, implying th transformation of BSM modl data to TIM modl data. In othr cass, th SLMToolBox will hav to support th intgration of standard xtrnal modls and graphical modl to modl transformation (xampl: Extndd Actigram Star modls to BPMN modls). In this contxt, modl transformation is idntifid as a transvrsal fatur to b implmntd in th Modling Environmnt. To fulfill this nd, ATL Transformation Languag ( ( is idntifid as a good option, as it is dvlopd on th top of th Eclips Platform and rlis on transformation ruls dscription to produc targt modls from a st of sourc modls. ATL has bn dvlopd as an answr to th QVT Rqust for Proposal; it is spcifid as both a mtamodl and a txtual concrt syntax. Th implmntation of th ATL Intgratd Environmnt in Eclips intgrats with EMF as it supports modls conforming to th Ecor format, among othrs Dynamic simulation of BPMN modls Th nrichmnt of BPMN procss with simulation paramtrs; xcution of th simulation procss and gnration of simulation rports is dlgatd to an xtrnal standalon application: Bonita Opn Solution. BPMN modls will b laboratd within th SLMToolBox (BPMN modlr); possibly initializd from EA* procss modls thanks to modl transformation. BPMN2.0 diagram fils will b xportd / importd within Bonita Opn Solution application Modl rpository intgration Th modling nvironmnt must offr storag capabilitis in ordr to prsist modls along thir lifcycl, and to allow th capability to rtriv thm and to updat thm. Morovr, as som of th modls (at TIM lvl) will b shard with th Gnric Srvic Dvlopmnt platform, th modls should b prsistd in a cntral rpository accssd via both systms. Finally, as multipl instancs of th SLMToolBox and th Srvic Dvlopmnt Platform may accss th sam modls in a collaborativ way, this rpository has to handl cass such as concurrnt accss and diting conflict rsolution. Th SLMToolBox will intgrat th Modl Rpository clint componnt, which provids accss to th MSEE modl rpository Assts rpository intgration Th accss to th assts rpository will b managd through a clint plugin componnt, intgratd to th modling nvironmnt of th SLMToolBox. Connction; brows; sarch; rtriv and publish actions will b managd through th manipulation of th REST API of th assts rpository; via th clint plugin. MSEE Consortium Dissmination: Public 95/143

96 6.2. Tchnical architctur Ovrviw Th following figur givs an ovrviw of th svral tchnical componnts that compos th modling nvironmnt of th SLMToolBox. W diffrntiat th application componnts which ar spcifically implmntd and ar part of th domain of th srvic systm modling tool, from th tchnical componnts which rfrs to xisting dvlopmnt artifacts, lik framwork, libraris and APIs. Figur 59 - Modling Environmnt - Tchnical Architctur Ovrviw Ths tchnical componnts ar uss as th basic building blocks of th application and ar issud from th tchnical analysis dscribd in th prvious sction Tchnical moduls For Eclips Platform, EMF, EEF, Graphiti and ATL, rfr to th dscription in th uppr sction ( tchnical rquirmnts & slctd tchnologis ) Application moduls App modul Th application modul is th main application containr of th modling nvironmnt of th SLMToolBox. It is mainly rsponsibl to compos and provid th graphical intrfac to th usr undr th form of svral viws, bing usd to navigat through th modling projct contnt and dit srvic systm modls. It coordinats th xcution of th undrlying faturs of th modling nvironmnt, and contains th logic of th graphical prsntation of th ovrall application. To fulfill its rol, this modul havily rlis on th clips cor platform MSEE Consortium Dissmination: Public 96/143

97 API, to bnfit from th artifacts it provids for standalon applications (viws, xplorrs, wizards ) Modl objcts modul This modul ncompasss th dfinition of th modl objcts of th domain of th application and thir intrrlationships. It provids an implmntation of th concptual modl of th application undr th form of a st of java bans. This implmntation is gnratd with th EMF cod gnration faturs, from th dfinition of th mtamodls in Ecor format at th dvlopmnt tim. This modul plays a cntral rol in th application as it provids th objcts instancs to th othr moduls, rsponsibl for procssing, prsnting and prsisting ths objcts Editors modul This modul is rsponsibl for providing indpndnt graphical modling ditors to th application. Two typs of ditors ar providd: 1. Graphical ditors allow th diting of diagrams with th hlp of graphical lmnts, rlatd to a spcific modling languag (for instanc: Extndd Actigram Star). Whil th diagrams ar ditd, th ditor stors th diagram in a spcific fil and dlgats th prsistnc of th modl data to th application srvic modul. Each ditor rlis on th Graphiti framwork, in ordr to provid standard diting facilitis and to offr a rich st of graphical lmnts to th usr. 2. Th scond st of ditors is dsignd for domain spcific purpos and allows diting BSM and TIM modls. To dsrv this goal, a tr viw is providd to brows th modl contnt, and a st of proprty shts to dit th attributs of th modl objcts. As for th graphical ditors, th prsistnc and th updat of th modl data is dlgatd to th appropriat srvic in th application srvic modul Application srvics modul This modul is rsponsibl to handl th domain logic of th application, which is indpndnt from th prsntation mchanisms and from th data storag faturs. It is logically dcomposd in four sub componnts: 1. Th modl transformation componnt packags th transformation ruls that apply to th domain of srvic systm modling, along MDSEA principls. It rlis on ATL to provid modl to modl transformation routins and xposs its faturs to th application modul. 2. Th Import/Export componnt is rsponsibl to handl th procsss that ar ncssary for importing standard modls (xampl: BPMN modls) in a srvic systm modl projct and xporting modls in standard rprsntations (xampl: USDL modls). For spcific logic, rlatd to th transformation of MDSEA modls to a standard rprsntation, this componnt rlis on th modl transformation componnt. 3. Th Modl Srvic componnt provids th basic srvics that ar ndd by th ditors, modl transformations and import/xport componnts to manipulat modl objcts. This componnt acts as a façad and provids a unifid intrfac to rtriv, chck, modify and crat MDSEA modl substs. 4. Finally, th Data Srvics componnt provids an intrfac in ordr to handl th prsistnc of th modl objcts. It abstracts and ncapsulats all th accss with th modl rpository to obtain and stor data. This componnt is dsignd along th DAO pattrn, which hids th prsistnc implmntation dtails from its clints. MSEE Consortium Dissmination: Public 97/143

98 Non-functional Rquirmnts covrag This sction intnds to chck th covrag of th non-functional rquirmnts by th tchnical approach in th dsign of th modling nvironmnt: ID Constraint Natur Tchnical mans NFC- Introprability 01 NFC- 02 NFC- Modl- 01 NFC- Modl- 02 NFC- Modl- 03 NFC- Modl- 04 NFC- Modl- 05 NFC- Modl- 06 NFC- Modl- 07 Th systm must intgrat samlssly with th gnral architctur of th IT MSEE systms Th SLMToolBox must b implmntd with th hlp of modrn and provn tchnologis to insur its maintainability Th Modling Environmnt must rly on a modular architctur which will guarant its xtnsibility in th fram of potntial futur dvlopmnt Th TIM modls must b providd to th Srvic Dvlopmnt Platform to nabl application dvlopmnt basd on tchnical indpndnt modls built with th SLMToolBox Th modls should b abl to b xportd in standard formats to insur th introprability of th modling nvironmnt Th modls should b shard in a cntral rpository in ordr to as thir sharing and diffusion btwn multipl actors Th stup of th modling nvironmnt on a workstation should rquir as lss prinstalld componnts as possibl Th modls can b partially visualizd or ditd through a wb basd nvironmnt Th modling nvironmnt could support collaborativ work to allow multipl usrs to work togthr on th sam modls Maintainability Extnsibility Introprability Introprability Cntralization Usability Usability Collaboration Th cntral modl rpository is idntifid as th uniqu contact point with th othr MSEE IT systms. Us of Opn Sourc «Eclips Platform Tchnology» (EMF + Ecor framworks) Indpndnt from othr MSEE systms. Modls ar shard in a cntral and domain agnostic modl rpository. Us of standard modling languags (x: BPMN, UML ). Export to standard spc. Compliant formats. Modls ar shard in a cntral and domain agnostic modl rpository. Th application is packagd as standalon softwar. Th SLMToolBox modling nvironmnt will b Standalon. Th modls could b accssd with spcific «wb basd» tools, pluggd on to th cntral rpository. As a modl data rpository, CDO offrs DAWN as a sub componnt, offring collaborativ faturs such as ral tim modl diting MSEE Consortium Dissmination: Public 98/143

99 managmnt, conflict handling for modling usr intrfacs basd on CDO. This tchnical componnt will b invstigatd in mor dtail during th scond cycl of th MSEE Projct. Tabl 28 - Modling Environmnt - Non-functional Rquirmnts covrag 6.3. Graphical intrfac dscription Layout ovrviw Th Eclips platform givs th foundations for th composition of th graphical layout of an clips plugin application. Th major constructs allow providing prspctivs to th usr, which ar composd of svral viws and ditors (DAN RUBEL, 2006). A viw is a graphical artifact, which is rsponsibl for providing accss to faturs of th application, such as th prsntation of spcific information or mans for diting this information. Th following figur givs an ovrviw of th modling nvironmnt graphical layout. It is composd of svral viws, and on graphical ditor, prsntd in on modling prspctiv Viw: Projct xplorr Figur 60 - Modling nvironmnt - Graphical Layout This viw provids th graphical rprsntation of th modling projct structur. Th projcts contnt is dcomposd in svral fils and dpictd as a hirarchical structur (tr viw). Thus th usr can accss th BSM or TIM modl, and th rlatd diagrams, sortd by point of viw. For th two modling projct typs supportd by th Modling Editor, th corrsponding diagrams ar structurd as follow: BSM modling projct: Point of viw Diagram Extnsion Editor MSEE Consortium Dissmination: Public 99/143

100 Dcision Grai Grid.graigrid Grai Grid Editor Grai Nts.graint Grai Nt Editor Procss Extndd Actigram Star.astar EA Star Editor Function Actigram.Actigram Actigram Editor Us cas (UML).xmi (?) UML us cas IT diagram ditor Class Diagram (UML).xmi (?) UML class diagram ditor TIM modling projct: Point of viw Diagram Extnsion Editor Procss BPMN2.0.bpmn2 BPMN2.0 Editor IT Class Diagram (UML).xmi (?) UML class diagram ditor Th modl xplorr allows th usr to prform th following actions: Crat / rnam / dlt / opn a BSM modling projct Crat / rnam / dlt / opn a TIM modling projct Crat / rnam / dlt / opn a spcific diagram Import / xport diagrams or modls Editor: Domain spcific ditor Th ditor viw is th main artifact supporting th intractions of th usr with th svral modling ditors plugins providd by th SLMToolBox modling nvironmnt. It is handld by th corrsponding ditor. Dpnding on th typ of ditor, it allows th usr to manipulat modls contnt with th hlp of graphical componnts in th fram of a diagram for a graphical ditor (.g.: GraiGrid, BPMN ) or with th hlp of a hirarchical rprsntation of th modl for a non-graphical modl ditor (.g.: BSM, TIM). Th ditors allow th usr to prform th following gnric actions: sav modl, add / dit / mov / dlt a modl objct. In addition, th graphical modling ditors provid a st of gnric diting faturs, such as: Export diagram, zoom in / out, print diagram Viw: Proprtis This viw provids th mans for consulting and diting th attributs of a spcific objct of th currnt modl, in th activ ditor. Its contnt is gnratd dynamically by th modl ditor, rgarding th objct which is slctd in its currnt instanc. It provids a st of basic forms, allowing th usr to modify th attributs valus, according to thir typ (.g.: txt valu, numbr, rfrnc ) Wizards A wizard supports th xcution flow of complx faturs which ncssitats a rich usr intraction scnarios or multistp scnarios. To dsrv this purpos, a wizard provids a st of forms, allowing th usr to input rquird information and to prform choics. Wizards ar mainly providd for faturs such as: modling projct cration, mapping languag spcific objcts with BSM or TIM objcts and modl transformation. MSEE Consortium Dissmination: Public 100/143

101 7. Conclusion This dlivrabl lad to th spcification blu print for th dvlopmnt of th scond vrsion of WP1.5 tools: Srvic lifcycl Managmnt ToolBox. Th high lvl scop and vision of th systm has bn xplaind and basd on ths thr fundamntal pillars: Srvic modling; Srvic nginring; Srvic govrnanc. A st of cohrnt functionalitis basd on th MDSEA modling architctur is laboratd, in rlation with th scintific concpts and rquirmnts from SP1 dlivrabls at M18 (WP1.1, WP1.2, WP1.3 and W1.4). Among ths faturs, w can notic th improvmnt and nrichmnt of th modling functionalitis; an xtnsion of th BSM functionalitis for th spcification of th srvic govrnanc basd on a rfrnc PI list; a Proposition for an approach basd on businss procss for th assssmnt of srvic xcution cost and duration. Th scond vrsion of th SLMToolBox will b implmntd on th basis of th first prototyp, which was rlasd at M12. Sinc thn, th arly softwar was xprimntd through th application of srvic nginring activitis for INDESIT and BIVOLINO us cass. This first prototyp was also analyzd from th tchnical prspctiv at th intgration stag of th ovrall MSEE IT systm (work packag WP4.5). As a consqunc, svral rcommndations wr takn in account and lad to th inclusion / prioritization of critical faturs in th scond vrsion of th softwar (in particular: intgration with th modl rpository modul; inclusion of a BPMN modlr in an intrmdiat vrsion; intgration of a UML modlr in a pr-rlas of vrsion 2). On can notic that du to intgration issus, th choic was mad in collaboration with SP4 partnrs to rmov th support for th CDO tchnology and to rly on a lss intrusiv tchnical approach for th managmnt of modl prsistnc and sharing. Although th scond vrsion of th SLMToolBox is a major volution of th first prototyp; th tchnical platform rmains practically unchangd and th ovrall architctur provs its modularity and xtnsibility. Accordingly, this spcification documnt tnds to b fatur drivn in th sns whr larg functionalitis ( faturs ) wr xtractd from th rquirmnt analysis phas, and th nw logical architctur of th softwar do not introduc dp modifications of th ovrall softwar. Th dfinition of ths faturs aims at isolating loosly coupld sts of functionalitis which can b implmntd in an incrmntal approach. A clar dvlopmnt roadmap is proposd, and follows th mthodological rcommndations, laboratd in D15.1. Two functional intrmdiat vrsions of th softwar will b rlasd bfor M24. Th partnrs in WP1.5 will striv to provid th rlvant support to th nd usrs through th xcution of thir us cass in th utilization of th SLMToolBox as th main supporting tool for srvic nginring activitis. Th fdback of this implmntation will b rgularly assssd and analyzd; in paralll th rmaining SP1 dlivrabls will b analyzd during th dvlopmnt phas of th SLMToolBox. Through this pragmatic concurrnt nginring approach, th objctiv is to prform th rlvant adaptations on th functionalitis of th softwar; so that th final vrsion (M24) will bnfit from arly usr assssmnt and xprinc fdback. In trm of prspctivs, on th tchnical sid, th SLMToolBox is dsignd to fulfill th intgration rquirmnts of th ovrall MSEE IT Architctur; but th possibility to allow a standalon usag outsid of th scop of MSEE is considrd as a cor constraint. Th capability of th softwar to b rusd as a sparat and slf-consistnt tool nabls futur scnarios in which th SLMToolBox may b lvragd in cass that hav diffrnt tchnological rquirmnts from thos of MSEE. On th sid of us cass, th xtnsion of modling faturs to th managmnt of virtualizd assts has bn introducd; this opportunity will b xplord into mor dtails in th following priod with th contribution of SP2 partnrs, onc th architctur (data modls; softwar support) for assts virtualization and managmnt will b finalizd. From th rsarch prspctiv, this us cas would bring th challng of fdrating MSEE ontological and smantic approachs with MDSEA modl cntric architctur. MSEE Consortium Dissmination: Public 101/143

102 8. Rfrncs OMG Unifid Modling Languag (OMG UML), Suprstructur, V (2007). Businss Procss Modl and Notation (BPMN) vrsion 2.0. (2011). MSEE Projct - Dscription of Work. (2011, 06). D Srvic concpts, modls and mthod: Modl Drivn Srvic Enginring. (2012). D12.1 Rport about Srvic Scnarios. (2012). D MSEE Srvic-Systm Functional and Modular Architctur. (2012). An outlin of th cor lmnts of an SLA. (s.d.). Blinn, P. G. (1989). Automatd IDEF3 and IDEF4 Systms Dsign Spcification Documnt. Tchnical rport. NASA Johnson Spac Cntr. D15.2: Spcifications and Dsign of Srvic Lifcycl Managmnt ToolBox. (s.d.). DAN RUBEL, I. (2006). Th hart of Eclips. Danil Amyot, H. F.-F. (2006). Evaluation of Dvlopmnt Tools for Domain-Spcific Modling Languags. Fitz-Gibbon, C. T. (1990). Prformanc Indicators. BERA Dialogus (2). G. Doumingts, B. V. (1998). "GRAI grid, dcisional modling" ; in Handbook on Architctur of Information Systm. Intrnational Handbook on Information Systms. Springr Vrlag. (s.d.). (s.d.). (s.d.). (s.d.). (s.d.). (s.d.). ISO/IEC/IEEE 42010:2011, Systms and softwar nginring Architctur dscription. (s.d.). MSEE Consortium Dissmination: Public 102/143

103 9. Annx 1 Collction & xtraction of rquirmnts 9.1. Rquirmnts survy DOMAINS Srvic Systm Modling Modl Transformation Usr Orintd FEATURES Rus cosystm / vm assts into srvic modls (rtriv in/tan assts dscriptions) Initiat TIM projcts on th basis of an xisting BSM projct data Spcify th data structurs of th srvic systm (UML Class Diagram) Initializ BPMN procsss from EA* diagrams «Ergonomic» improvmnts on xisting To build modls (BSM/ ditors TIM) and projct wizards at th lvl of th VME + Minor bug fixs Assist usrs to nrich modls at transformation tim, using a knowldg bas To publish and shar rfrnc modls among cosystm mmbr according to thir maturity Modl GRAI Nts at BSM lvl «Ergonomic» improvmnts on xisting ditors and projct wizards + Minor bug fixs Export USDL rprsntations fromth srvic modls Collaborativ Modling Syntactic modl validation Faturs Enrich modls with smantic anotations Manag multipl vrsions of th srvic systm modls Dynamic linking btwn GraiGrid and Extndd Actigram Intgration FEATURES Provid compatibl Businss Procsss modls to th IEP To virtualiz in/tan assts through TIM modls Provid sufficint TIM modl contnt to th GSDEV PTF Non Functional FEATURES Stor modl and diagram data in a singl cntralizd rpository Srvic Govrnanc Slct rlvant KPIs according to bst pratics Dfin prformanc objctiv valu for th KPIs Provid rusabl KPI dscriptions to th BI modul of th IEP Srvic Enginring Srvic Systm Simulation Gnrat a synthsis rport basd on srvic systm modls Estimat th duration of th srvic dlivry Configur th Srvic Enginring projct (moduls ; phass ; plannings ; chcklists ; ) Estimat th cost of th srvic dlivry B guidd by a srvic nginring mthodology for th dsign of th srvic systm Estimat th quality of th rsulting srvic Export pr-filld Srv-Lab configuration fils Rly on a HLA distributd Us GDEVS as a simulation simulation architctur modling languag (REST) 24 Figur 61 - Rquirmnts survy

104 9.2. Rquirmnts mapping Figur 62 - Rquirmnt mapping MSEE Consortium Dissmination: Public 104/143

105 10. Annx 2 Dtaild dsign Mta modl BSM Figur 63 - BSM cor Mtamodl MSEE Consortium Dissmination: Public 105/143

106 10.2. Mtamodl - TIM Figur 64 - TIM cor Mtamodl MSEE Consortium Dissmination: Public 106/143

107 10.3. Mtamodl Grai Grid Figur 65 - Grai Grid Mtamodl (BSM) MSEE Consortium Dissmination: Public 107/143

108 10.4. Mtamodl Grai Nts Figur 66 - GRAI Nts Languag Mtamodl MSEE Consortium Dissmination: Public 108/143

109 10.5. Mtamodl Mapping Grai Nts / BSM / Grai Grid Figur 67 - Mapping with BSM mtamodl & GraiGrid mtamodl Mapping: MDSEA Mtamodls / In-Tangibl assts ontology BSM Th following tabl illustrats th BSM cor mta-modl and th Intangibl and tangibl assts ontologis mapping. W rcall that ths ontologis ar dfind rspctivly in WP22 and WP23. BSM Cor Mtamodl <<class>> Rsourc <<attributs>> - typ {physicalman, IT, human, undfind} - rol - capability - constraint <<rlationships>> Com from:organization Contribut to:procss Contribut to:srvic Intangibl / Tangibl Assts Ontologis Intangibl Ontology Cas 1: if rsourc.typ = human <<typ>>: Human_Rsourc <<attributs>> Nam (OK) Location(KO) Matriculation_Numbr(KO) <<objct propry assrtions>> null Intangibl Ontology Cas 2: if th Rsourc.typ = IT <<typ>>: Tchnical_Intangibl_Assts <<attributs>> Dscription (KO) Organization(OK:Organization.nam) Main_Functions(OK:Rsourc.capability) MSEE Consortium Dissmination: Public 109/143

110 <<class>> Procss <<attributs>> - objctiv - triggr - output - constraint <<rlationships>> Contribut to: Srvic Contribut to: Organization Contribut to: Rsourc Contribut to: Procss Contribut to: Dcision <<class>> Dcision <<attributs>> - dcisiontyp{priodic, vntbasd} - constraint - objctiv - variabl - vnt <<objct propry assrtions>> null Tangibl Ontology Cas 3: if th Rsourc.typ = physicalmans <<Typ>> Tangibl <<attributs>> Dscription (KO) Organization(OK) Main_Functions(OK:Rsourc.capability) <<Objct Proprty assrtions>> null <<rlationships>> Contribut to: Procss Contribut to: Organization Contribut to: PrformancIndicator Contribut to: DcisionStructur <<class>> DcisionStructur <<attributs>> <<rlationships>> Contribut to: Dcision <<class>> PrformancIndicator <<attributs>> - typ{customrorintd, providrorintd} - objctiv - dscription - rquirdinfo - rquirdprocssing MSEE Consortium Dissmination: Public 110/143

111 <<rlationships>> Contribut to: Srvic Contribut to: Dcision <<class>> Organization <<attributs>> - typ{hirarchical, dcntralizd cntralizd} - dscription <<rlationships>> Contribut to: Dcision Contribut to: Procss <<class>> Customr <<attributs>> - lvlofeducation - catgoris - gndr{mal, fmal} - ag - annualrvnu - targtdusagfrq - rquirmnt - constraint - dscription Intangibl Ontology <<Typ>> Extrnal_Rlational_Intangibl_Assts <<attributs>> null <<Objct Proprty assrtions>> null <<rlationships>> Contribut to: Srvic <<class>> Functionality <<attributs>> - typ {Information procssing, matrial handling, transportation } - dscription <<rlationships>> Contribut to: functionalty Contribut to: Srvic Contribut to: Product <<class>> Srvic <<attributs>> - domain - objctiv - natur - constraint - dscription Intangibl Ontology <<Typ>> Extrnal_Rlational_Intangibl_Assts <<attributs>> null <<Objct Proprty assrtions>> null Intangibl Ontology <<Typ>> Human_Intangibl_Assts <<attributs>> Dscription (OK :Srvic.dscription) Organization(OK :Srvic.Procss.Organization) <<Objct Proprty assrtions>> null <<rlationships>> Contribut to: PrformancIndicator Contribut to: Procss Contribut to Rsourc Contribut to: Customr MSEE Consortium Dissmination: Public 111/143

112 Contribut to: Functionality Contribut to: Partnr Contribut to: Stakholdr Contribut to: Valu Contribut to: Product <<class>> Partnr <<attributs>> - catgory - comptnc - concrn - constraint - contribution - dscription <<rlationships>> Contribut to: Srvic <<class>> Stakholdr <<attributs>> - typ{human, organization} - concrn - constraint - rol <<rlationships>> Contribut to: Srvic <<class>> Valu <<attributs>> - dscription <<rlationships>> Contribut to: Srvic <<class>> Product <<attributs>> - typ - tchcharactristics - function <<rlationships>> Contribut to: Srvic <<class>> Componnt Intangibl Ontology <<Typ>> Extrnal_Rlational_Intangibl_Assts <<attributs>> typ(ok:partnr.cconstraint) loyalty(ko) dscription(ok:partnr.dscription) Organization(KO) Kind(OK:Partnr.catgory) <<Objct Proprty assrtions>> null Intangibl Ontology Cas 1: if th Stakholdr.typ = human <<Typ>> Human_Rsourc <<attributs>> Nam (OK) Location(KO) Matriculation_Numbr(KO) <<Objct Proprty assrtions>> null Intangibl Ontology Cas 2: if th Stakholdr.typ = organization <<Typ>> null <<attributs>> null <<Objct Proprty assrtions>> null Tangibl Ontology <<Typ>> Tangibl <<attributs>> Availability(KO) Rlatd_Tchnology(KO) Dscription(OK:Product.tchCharactristics) Drawing(KO) ID(KO) Labl(KO) Robustnss(KO) Providr(OK:Product.Srvic.Procss.Organization) Inspction_Intrvall(KO) <<Objct Proprty assrtions>> null MSEE Consortium Dissmination: Public 112/143

113 <<attributs>> - cost <<rlationships>> Com from: Product Tabl 29 - Mapping : BSM Cor / In-Tangibl assts ontology Mapping: MDSEA Mtamodls / In-Tangibl assts ontology - TIM Th following tabl illustrats th TIM cor mta-modl and th Intangibl and tangibl assts ontologis mapping. TIM <<class>> Rsourc <<attributs>> function <<rlationships>> Com from: OrganizationUnit Contribut to: Procss Contribut to: Srvic ONTOLOGY Intangibl Ontology <<Typ>> Human_Rsourc <<attributs>> Nam (KO) Location(KO) Matriculation_Numbr(KO) <<Objct Proprty assrtions>> null Intangibl Ontology <<Typ>> Tchnical_Intangibl_Assts <<attributs>> Dscription (KO) Organization(OK:Rsourc.OrganizationUnit.nam) Main_Functions(KO) <<Objct Proprty assrtions>> null Tangibl Ontology <<Typ>> Tangibl <<attributs>> Dscription (KO) Organization(OK:Rsourc.OrganizationUnit.nam) Main_Functions(KO) <<Objct Proprty assrtions>> null <<class>> Human <<attributs>> capability skills ducationlvl quantity constraint xpctdprformanc <<rlationships>> Com from: OrganizationUnit Inhrit: Rsourc <<class>> PhysicalMan <<attributs>> - capability Intangibl Ontology <<Typ>> Human_Rsourc <<attributs>> Nam (OK) Location(KO) Matriculation_Numbr(KO) <<Objct Proprty assrtions>> null Tangibl Ontology <<Typ>> Tangibl <<attributs>> MSEE Consortium Dissmination: Public 113/143

114 - tchnicalcharactristics - typ - constraint - xpctdprformanc - oprationmod Dscription (KO) Organization(OK) Main_Functions(OK:Rsourc.capability) <<Objct Proprty assrtions>> null <<rlationships>> Inhrit:Rsourc <<class>> EntrprisApplication <<attributs>> - charactristics - dscription - typ unctionality <<rlationships>> inhrit: Rsourc <<class>> Procss <<attributs>> - objctiv - triggr - rsult - constraint - workflow Intangibl Ontology <<Typ>> Tchnical_Intangibl_Assts <<attributs>> Dscription (KO) Organization(OK:Organization.nam) Main_Functions(OK:Rsourc.capability) <<Objct Proprty assrtions>> null <<rlationships>> Contribut to: Srvic Contribut to: OrganizationUnit Contribut to: Rsourc Contribut to: Procss <<class>> Organization <<attributs>> - typ{hirarchical, dcntralizd cntralizd} - dscription - rsponsibility - authorization <<rlationships>> Com from: OrganizationUnit <<class>> OrganizationUnit <<attributs>> - id - nam - function - rsponsibility - authorization <<rlationships>> Com from :OrganizationUnit MSEE Consortium Dissmination: Public 114/143

115 <<class>> Srvic <<attributs>> - domain - objctiv - natur - automationlvl - accss - consumption <<rlationships>> Contribut to: Procss Contribut to: Rsourc Contribut to: Srvic <<class>> Information <<attributs>> - informationentity - rlationship Intangibl Ontology <<Typ>> Human_Intangibl_Assts <<attributs>> Dscription (OK :Srvic.dscription) Organization(OK :Srvic.Procss.Organization) <<Objct Proprty assrtions>> null <<rlationships>> Contribut to: EntrprisApplication Tabl 30 - Mapping : TIM Cor / In-Tangibl assts ontology EA Star to BPMN Collaboration Diagram Modl Mapping Th following tabl summarizs th mapping of EA* concpts to BPMN concpts. Th mapping is accompanid with conditions which govrns th cration of rlations btwn concpts. EA* Condition BPMN2.0 Modl Dfinitions Procss Procss, Participant Extndd Structural Activity Sub Procss Activity Atomic It is supportd by Human UsrTask It is supportd by IT (no human intraction SrvicTask LogicalOprator DivrgingOr Gatway Divrging Exclusiv Gatway ConvrgingOr Convrging Exclusiv Gatway DivrgingAnd Paralll Gatway ConvrgingAnd Paralll Gatway Rsourc Matrial Data Objct Human Rsponsibl for Lan Participats in Rsourc (addd to th list of rsourcs of a task) It Rsponsibl for Lan Participats in Rsourc (addd to th list MSEE Consortium Dissmination: Public 115/143

116 of rsourcs of a task) Flow Control Flow If th sourc is an MssagFlow ExtrnalConnctor or IntrnalConnctor and targt is an atomic ExtnddActivity If th sourc is an Catching Mssag Evnt, ExtrnalConnctor or Mssag flow, and Squnc IntrnalConnctor and targt Flow is a structural ExtnddActivity If th sourc is a DataObjct, and associations ProcssConnctor or ExtnddActivity OutputInputFlow If th sourc is an MssagFlow ExtrnalConnctor or IntrnalConnctor (and targt is an atomic Extndd Activity) If th sourc is an Catching Mssag Evnt, ExtrnalConnctor or Mssag Flow, and Squnc IntrnalConnctor (and targt Flow is a structural Extndd Activity or LogicalOprator) If th sourc is a SquncFlow ProcssConnctor, ExtnddActivity, or LogicalOprator (and targt is an ExtnddActivity or procss connctor or logical oprator) If th sourc is a structural ExtnddActivity or logical oprator (and targt is an Throwing Mssag Evnt, Mssag Flow, Squnc Flow ExtrnalConnctor or IntrnalConnctor) If th sourc is an atomic MssagFlow ExtnddActivity (and targt is an Extrnal or Intrnal Connctor) SupportFlow If sourc is a matrial rc Association Connctor ExtrnalConnctor Participant (Pool) ProcssConnctor Call Activity IntrnalConnctor Particiapnt (Pool) (Black Box) Tabl 31 - EA* 2 BPMN - Transformation Mapping (Collaboration Diagram) EA Star to BPMN Collaboration Diagram Transformation Ruls Atomic ExtnddActivity Condition1: A Human rsourc is rsponsibl for th ralization of th Extndd Activity. In this cas th atomic Extndd Activity is mappd to a UsrTask. Condition2: An IT rsourc is rsponsibl for th ralization of th Extndd Activity. MSEE Consortium Dissmination: Public 116/143

117 Rsourc In this cas th atomic Extndd Activity is mappd to a SrvicTask. Condition1: th valu of th rsourcrol is rsponsibl for. In this cas th rsourc (Human or IT) is mappd to a lan, in which th supportd ExtnddActivity blongs to th lan. Condition2: th valu of th rsourcrol is participats in. In this cas th rsourc (Human or IT) is addd to th list of rsourcs to th supportd ExtnddActivity. ControlFlow Condition1: Sourc is an ExtrnalConnctor or IntrnalConnctor and targt is an atomic ExtnddActivity. In this cas it is mappd to a MssagFlow. Condition2: Sourc is an ExtrnalConnctor or IntrnalConnctor and targt is a structural ExtnddActivity. This cas is a 1 to n rlation, in which th Control Flow is mappd to a combination of MssagFlow, catching MssagEvnt, and a SquncFlow. Condition3: Sourc is a ProcssConnctor or ExtnddActivity. It is a 1 to n rlation, in which th Control Flow is mappd to a combination of DataObjct and two Associations. OutputInputFlow Condition1: Sourc is an ExtrnalConnctor or IntrnalConnctor and targt is an atomic Extndd Activity. In this cas th OutputInput Flow is mappd to a MssagFlow. Condition2: Sourc is an ExtrnalConnctor or IntrnalConnctor and targt is a structural Extndd Activity or LogicalOprator. This cas is a 1 to n rlation, in which th Control Flow is mappd to a combination of MssagFlow, catching MssagEvnt, and a SquncFlow. Condition3: Sourc is a ProcssConnctor, ExtnddActivity, or LogicalOprator and targt is also on of ths thr options. In this cas it is mappd to SquncFlow. Condition4: Sourc is a structural ExtnddActivity or LogicalOprator, and targt is an ExtrnalConnctor or IntrnalConnctor. This cas is a 1 to n rlation, in which th Control Flow is mappd to a combination of MssagFlow, throwing MssagEvnt, and a SquncFlow. Condition5: Sourc is an atomic ExtnddActivity and targt is an ExtrnalConnctor or IntrnalConnctor. In this cas it is mappd to a MssagFlow. SupportFlow Condition1: Sourc is a Matrial rsourc. In this cas it is mappd to an Association EA Star to BPMN Procss Diagram Modl Mapping EA* Condition BPMN2.0 Procss Procss MSEE Consortium Dissmination: Public 117/143

118 Flow Control Flow If th sourc is a ProcssConnctor or ExtnddActivity ls OutputInputFlow If th sourc is a ProcssConnctor, ExtnddActivity, or LogicalOprator (and targt is an ExtnddActivity or procss connctor or logical oprator) ls DataObjct, and associations Not mappd SquncFlow Not mappd SupportFlow If sourc is a matrial Association rsourc ls Not mappd Connctor ExtrnalConnctor Not mappd ProcssConnctor Call Activity IntrnalConnctor Not mappd Tabl 32 - EA* 2 BPMN - Transformation Mapping (Collaboration Diagram) EA Star to BPMN Procss Diagram Transformation Ruls Procss An EA* Procss is mappd to a BPMN2.0 Procss, this Procss won t b rprsntd graphically by a pool (in contrast to Collaboration BPMN2.0 diagrams) ControlFlow Condition1: if th sourc is a ProcssConnctor or ExtnddActivity (Atomic or Structural), thn it is mappd to a squnc flow Condition2: if condition 1 is not applicabl thn a ControlFlow is not mappd OutputInputFlow Condition1: Sourc is a ProcssConnctor, ExtnddActivity, or LogicalOprator and targt is also on of ths thr options. In this cas it is mappd to SquncFlow Condition2: if condition 1 is not applicabl thn an OutputInputFlow is not mappd SupportFlow Connctor Condition1: if sourc is a matrial rsourc, thn it is mappd to an Association Condition2: if sourc is of anothr typ, thn it is not mappd If th connctor is a ProcssConnctor thn it is mappd to a CallActivity. Any othr typ of connctors is not mappd. MSEE Consortium Dissmination: Public 118/143

119 11. Annx 3 Tchnology Indpndnt Modls Mthodological Approach Scop Th scop of this documnt is to summariz th mthodological foundations for th laboration of modls at th TIM lvl. Th BIVOLINO us cas is usd as a rfrnc tst cas for th MDSEA approach. This analysis focus on th TIM (Tchnology Indpndnt Modls), in th continuity of th modls laboratd at th BSM lvl, by I-VLAB with th collaboration of BIVOLINO. Thrfor, whil dvloping th rlvant TIM modls for BIVOLINO, it is th opportunity to laborat th mthodological approach which should driv th analysis activitis within th TIM lvl. Hnc, w hav dtaild in a ddicatd sction of th documnt, a gnral mthodological approach for laborating analysis and dsign modls at th TIM lvl. Th approach proposd in this documnt will b rusd within th 4 tst cass of th MSEE projct (BIVOLINO, IBARMIA, INDESIT and TP-VISION) for th laboration of TIM modls in thir srvitization tst cass. This mthodology is basd on 1) th spcific modlling contxt of MSEE, which blong to th MDSEA approach, 2) bst practics from softwar nginring and Modl Drivn Dvlopmnt domains (MDE) from which w xtractd svral rcommndations which w considr hlpful to kp th modls and th futur systm alignd with th businss rquirmnts. In practic, ths rcommndations aim to modl th sufficint aspcts of th systm, at th right lvl of dtails Background According to th spcification of MDSEA, th modlling at th TIM lvl focuss on th IT aspct of th srvic systm. Th TIM modlling lvl aims at capturing th information which will b ncssary to gnrat th softwar cod for th configurator customizr systm, indpndntly of th tchnology. Th modlling activitis at th TIM lvl corrspond to th PIM lvl, dfind by th OMG in th Modl Drivn Architctur (MDA) approach. From a mor traditional softwar projct prspctiv, th TIM modls corrspond to th dtaild spcifications of th systm (i..: dtaild analysis and functional dsign), which will srv as a basis for th implmntation of th systm, by dvloprs and softwar nginrs (tchnical dsign and dvlopmnt). As a part of th MDSEA Framwork, th TIM lvl acts as a bridg btwn th businss aspcts of th srvic systm (capturd at th BSM lvl) and th tchnological aspcts lading to th implmntation of th IT Systm (prformd at th TSM lvl). In othr words, th TIM modls must connct th rquirmnts with th tchnical implmntation of th softwar systm. Thrfor, th TIM modls must fulfil two contracts : 1. With BSM : To kp th systm analysis and dsign prfctly alignd with th businss rquirmnts in ordr to dlivr th xpctd srvic (Objctiv #2) 2. With TSM: To provid nough dtails to dscrib th complt bhavior of th systm to b implmntd so that th dvlopr can focus on implmntation and tchnical dcisions (Objctiv #1) Contnt of th study W considr th modlling activitis at th TIM lvl must covr th following phass of a softwar systm dvlopmnt projct: 1. Th dtaild analysis phas: laborating th functionalitis of th systm, basd on a strong connction with th businss rquirmnts, 2. Th functional dsign phas: providing a prcis and unambiguous dscription of th structur, architctur and bhavior of th systm to b implmntd Th initialization of th analysis modls will b basd on th information gathrd at th lowr lvls of th BSM modls. Som of th BSM modls will b usd to automatically initializ analysis modls at th TIM lvl, thanks to modl transformation tchniqus. Th dtaild information to laborat th analysis and thn, th dsign, will b addd manually to th modls. MSEE Consortium Dissmination: Public 119/143

120 In a nutshll, th analysis and dsign modls aim to answr th following qustions: Why and how th usr dos intract with th systm? In which scnarios? (us cas modls, procss modls) Which squnc of activitis is prformd by th usr? By th systm? Dpnding on which logic? (procss modls, squnc diagrams) How is th systm organizd? (logical architctur) What ar th data structurs manipulatd by th systm? (data modls) So that th systm and th prsons rsponsibl for implmnting th systm knows xactly what to implmnt, and can concntrat on prforming th right tchnical choics and to laborat xcutabl cod (according to objctiv #1) Pr rquisits According to th MDSEA approach, th modlling activitis at th TIM lvl com aftr th dvlopmnt of BSM modls, which dlivr a businss analysis of a srvitization cas. As xplaind prviously, th analysis at th TIM lvl nds to rus th BSM modls to satisfy th rquirmnts xprssd at th businss lvl. Thrfor, BSM modls should provid nough dtails to answr th following qustions: What businss goal ths procsss will contribut to achiv? In what procss th systm will b involvd? How xactly th systm will b usd within concrt scnarios? (Which actors will intract with th systm? Dpnding on which conditions?) What ar th sub-functions of th systm? Concrning th BIVOLINO us cas, such information was collctd through: Th analysis prformd by I-Vlab in th form of BSM modls (Businss Srvic Modls), Th spcification documnts providd by BIVOLINO, Phon call mtings with BIVOLINO s xprts and I-VLAB Limits By dfinition, th TIM (Tchnology Indpndnt Modls) nforc to: 1) Stay indpndnt of th tchnology which will b slctd for th implmntation of th systm, at th TSM lvl. 2) Avoid th considration of tchnical challngs (.g. : prformanc, introprability, data volumtry, intgration ) which ar addrssd at th TSM lvl (Tchnology Spcific Modls) Accordingly, this study will only focus on th spcification of th systm from a functional prspctiv ( how th systm bhavs?) and from a logical prspctiv ( how to dcompos and organiz th systm? ). Th choic of th tchnologis and th intgration dtails of th systm will b thn laboratd at th TSM lvl ( how th systm is built? ). To b mor concrt, th analysis dos not answrs th following qustions : Which tchnical componnts ar ndd to build th systm? (platforms, languags, databass, APIs, framworks ) How th systm dos intgrat within its tchnical nvironmnt? (For xampl, in th cas of BIVOLINO: ntrpris information systm, -tailrs wb portals ) What hardwar rsourcs ar ndd to run th systm and to guarant its prformanc? Whr/how th softwar componnts will b dployd? Yt, th analysis at th TIM lvl aims to provid maningful information in ordr to hlp th tchnical dcisions at th TSM lvl, thanks to th following charactristics laboratd at th TIM lvl: complxity of th systm, modularity of th componnts, data structurs, typology of th usrs MSEE Consortium Dissmination: Public 120/143

121 Succss factors Anothr mthodological aspct inducd by MDSEA is th notion of tmporal squnc btwn th laboration of BSM, TIM and TSM modls. Du to th fact that modl transformation should support th transition from on lvl to anothr, th stratgy for th dvlopmnt of srvic systms is to adopt a watrfall approach, avoiding th possibility to laborat th thr modlling lvls concurrntly, as th contnt of on lvl is strictly dpndant on th uppr lvl. To illustrat this vrtical approach, it is assumd that th choics at th BSM lvl will hav a significant impact on th TIM lvl; whthr modlling choics at th TIM lvl will hav no impact on th uppr lvl (BSM) th sam pattrn applis to th rlation btwn TIM and TSM lvls. Finally, this lads to considr that rquirmnts modifications at th BSM lvl will introduc considrabl modifications within TIM and by consqunc TSM modls. This approach introducs risks in th dvlopmnt procss, du to an upfront rquirmnt dfinition, and an upfront dsign bfor any implmntation considrations. Concrning th activitis prformd at th TIM lvl, this risk must b modratd with a strong collaboration btwn BSM and TIM for rquirmnt validation as wll a strong collaboration btwn TIM and TSM for dsign validation. Succss factors: Shard rfrnc vision of th businss goals and th implmntation scnarios Involvmnt of th stakholdr / businss rprsntativs within th systm analysis Anticipating critical tchnical / nonfunctional constraints sinc th analysis TIM Modling architctur As for th BSM modlling lvl, w propos a st of guidlins at th TIM lvl, so that th analyst rlis on a wll-dfind modlling architctur and can concntrat on th laboration of th modls to satisfy th businss rquirmnts TIM Modling viws In ordr to provid a complt dsign to th TSM lvl, w propos to modl th systm at TIM lvl according to four complmntary and ssntial viws: Figur 68- TIM Modling viws Th rspctiv rols of th four proposd viws ar th following: Intraction viw: to dscrib xtrnal intractions of th systm (usrs, third party systms) Architctural viw: to dscrib th dcomposition of th systm in logical sub componnts Bhavioral viw: to dscrib th intractions within th systm and btwn its componnts MSEE Consortium Dissmination: Public 121/143

122 Structural viw: to dscrib th static faturs of th systm (objcts, data structurs, ) TIM rprsntations (modling languags) Each viw contains svral complmntary rprsntations of th systm, dvlopd with appropriat graphical modlling languags or graphical notations. In th domain of softwar nginring, th Unifid Modlling Languag (UML) dfind by th OMG, provids a standard graphical notation allowing dfining th most ssntial aspcts of softwar systms. Du to th srvic domain of MSEE, th IT systms involvd within th production of srvics may b support complx businss procsss, implying svral actors; subsystms and third partis. Hnc, w propos to us BPMN2.0 to spcify th procsss involving intractions btwn human actors, th systm and its subcomponnts. Not 1: it is important to undrlin that having rcours to formal or smi-formal graphical modlling languags (.g. : UML, BPMN, ) for building th analysis modl of th softwar bring powrful bnfits such as : nforcing cohrnc thanks to a standard syntax, guiding th work of th analyst, lvraging (smi-)automatic modl transformations to gnrat th softwar implmntation (MDA) But such formalisms must b compltd with spcific, non-formal rprsntations (.g.: gnral architctur diagram, usr goals dscription, usr rols, usr intrfac flow diagrams ) in ordr to 1) facilitat th undrstanding of th nvisiond systm by th actors involvd within th projct (businss rprsntativs, analysis, nginrs, dvloprs, ) 2) and to dscrib critical aspcts of th systm which cannot b covrd with modlling languags (Exampl : gnral architctur diagrams, graphical intrfac dsign, ) but which ar ssntial for th implmntation of th systm.. Not 2: although th slctd modlling formalisms for th TIM modls (UML; BPMN) ar indpndnt of any spcific tchnology or tchnical platform, ths formalisms offr thir full bnfits in crtain IT contxts, such as: 1) objct orintd softwar dvlopmnt for UML; 2) Srvic orintd architcturs (SOA) for BPMN Intraction viw Th intraction viw is critical for dscribing how th systm will b usd within concrt scnarios. This viw aims at dscribing th xtrnal (visibl) aspcts of th systm, as It might hav a strong influnc on its intrnal dsign. Rprsntation Objctivs & Commnts Formalisms Us cass (xtndd with actor Rols and Goals) To dscrib at high lvl, th intractions btwn human actors and th systm, through svral us cass. In th TIM lvl, us cas diagrams ar usd to summariz and communicat th scop of th systm to b dvlopd within th projct. Idntify th actors which will intract with th systm ( Who will us th systm? ), Rmind th goals which th usr tnds to achiv with th systm ( Why th usr intracts with th systm? ), Provid an ovrviw of th rquirmnts of th systm from a usr prspctiv ( What activitis dos th systm supports? ). Rcommndations : Involv th businss rprsntativ in th laboration of us cas diagrams Dscrib th actors with as much dtails as possibl (xampl : us prsonas ) Exampl : UML Us cas diagram MSEE Consortium Dissmination: Public 122/143

123 Usr cntrd procsss Figur 69 - UML Us Cas Diagram - Exampl To dscrib in dtails th businss procsss which involv intractions of human actors with th systm and/or third party systms ( How th systm is usd within concrt scnarios? ). Th objctiv is to bring a focus on th usr activitis, to clarify th organizational contxt in which th systm is involvd : Dscrib th logic of th procsss involving th systms and th usrs, according to th us cass prviously modld Idntify and communicat th dtails concrning how th usr will us th systm Th choic of BPMN is to provid a standard notation that is radily undrstandabl by businss stakholdrs including businss analysts who crat and rfin th procsss, tchnical dvloprs rsponsibl for implmnting th procsss, and businss managrs who monitor and manag th procsss. Exampl : BPMN2.0 Collaboration diagram Figur 70 - BPMN - Usr cntrd procss - Exampl Usr Flow Intrfac To dscrib th squnc of scrns through which th actors will intract with th systm. No standard formalism. (Optionally : UML Activity Diagrams) Exampl : Usr intrfac Figur 71 - Usr intrfac flow - Exampl To dsign th graphical intrfac lmnts which will convy th information xchangs btwn th actors and th No standard formalism. MSEE Consortium Dissmination: Public 123/143

124 systm, Exampl : Figur 72 - Usr intrfac mockup - Exampl Tabl 1 - Intraction viw MSEE Consortium Dissmination: Public 124/143

125 Architctural viw Rprsntation Objctivs Formalisms Gnral architctur To giv a gnral pictur of th us cas : th rol of th systm, its nvironmnt, th main flows of information Exampl : No standard formalism. Figur 73 - Gnral Architctur diagram - Exampl Domain modl To captur th main businss ntitis and th rlationships btwn thm. UML Class diagram Th initial domain modl will b usd to hlp guid th dvlopmnt of th logical architctur as wll as th structural viw of th systm (data and objcts). nitialdomainmodl Exampl : Logical architctur Figur 74 - Domain modl - Exampl To isolat th moduls of th systm from a logical prspctiv: thir organization, intractions and rsponsibilitis. To prform this dscription, w start with th BPMN modls, focusing on th systm bhavior. In ordr to achiv a structurd dscription of th systm, th stratgy is to isolat indpndnt componnts of th systm and to organiz thm within svral packags. Rcommndations : Insur th consistnc of th componnts with th procss modls Stay at th logical prspctiv, avoiding implmntation considrations Exampl : UML Componnt diagram MSEE Consortium Dissmination: Public 125/143

126 Figur 75 - Logical architctur - Exampl Tabl 2 - Architctural viw Bhavioral viw Rprsntation Objctivs Formalisms Systm procss To dscrib in dtails th bhaviour of th systm and th unit of work involvd in th intraction with th actors of th procsss which must b supportd by th systm. Th objctiv is to bring a focus on th bhaviour of th systm, in ordr to rprsnt th logic which is prformd by th systm, indpndntly of th logic of th usr. Exampl : BPMN2.0 Collaboration diagram Figur 76 - BPMN systm cntrd procss - Exampl Procssings To spcify th particular procssings involving th collaboration of svral objcts of th systm. UML diagram Squnc Th squnc diagrams rprsnt th collaboration of objcts basd on a tmporal squnc. It shows how th objct intracts with othrs in a particular scnario of a us cas. Exampl : MSEE Consortium Dissmination: Public 126/143

127 Figur 77 - UML Squnc Diagram - Exampl Tabl 3 - Bhavioral viw Structural viw Rprsntations Objctivs Formalisms Data modl To dscrib th data structurs manipulatd by th systm. Rcommndations : Th data modls should b alignd with th domain modl to rflct th smantic and th concpts idntifid at th domain lvl Exampl : UML Class diagram Figur 78 - Data modl - Exampl Objct modls To dscrib th softwar objcts at th lowr lvl, indpndntly of any tchnology. Exampl : UML Class diagram MSEE Consortium Dissmination: Public 127/143

128 Figur 79 - Objct modl - Exampl Tabl 4 - Structural viw TIM Modling lvls In th sam philosophy of th work prformd by I-VLAB at th BSM lvl, w propos to adopt a vrtical dcomposition of th modls, so that th complxity of th systm can b laboratd incrmntally. Th modling starts with high lvl analysis modls and w progrss toward dtaild dsign modls that can b rusd for th gnration of th xcutabl softwar at TSM lvl. Th following figur dpicts th TIM architctur. In particular, it shows which rprsntations ar usd at which lvls, as wll as th dpndncis btwn ths modls. Figur 80 - TIM Modls dcomposition Th four modlling lvls ar organizd along two modlling phass: Analysis and Dsign. Th following tabl xplains th goals and charactristics of ach modlling lvl: TIM Lvl 1 : to validat and rfin th rquirmnts TIM Lvl 2 : to spcify th functionalitis of th systm in dtails TIM Lvl 3 : to dsign th architctur of th systm TIM Lvl 4 : to prpar th softwar dsign, with objct modls and th procssings to b prformd by th systm MSEE Consortium Dissmination: Public 128/143

129 11.5. TIM Modling procss Modling phass First, modls from BSM, lvl #5 ar transformd toward Usr-cntrd procsss modls at TIM, lvl#1, thanks to a smi-automatic modl transformation (from Extndd Actigram Star diagrams to BPMN2.0 diagrams). Thn, starts th procss of laborating TIM modls. This work is laboratd along 4 succssiv itrations, aiming to rfin th modls toward dtaild dsign modls, through th four succssiv lvls. This part is th most critical as it is ncssary to nrich th modls to kp th alignd with th businss rquirmnts and to achiv a sufficint lvl of dtails. Ths modls will b laboratd in an itrativ approach, involving priodic validation of th stak holdrs (in our cas: BIVOLINO). This procss aims to achiv a rlvant dtail lvl, so that th modls ar constantly alignd with th businss rquirmnts and can b transformd at th TSM lvl, and thn into xcutabl cod (in conformanc to objctivs #1 and #2). Thrfor, HARDIS will provid svral vrsions of th TIM modls to BIVOLINO and will procd to succssiv rfinmnts for complting th analysis and dsign modls. Finally, th modls of TIM at th lvl 4 ar transformd toward TSM lvls, in ordr to mak th tchnical dsign of th systm and to gnrat cod Contnt of th itrations Th following tabl dscribs th contnt of th four itrations w propos to laborat th TIM modls for a srvitization us cas, thir spcific goals, and which modlling viw will b laboratd: Intraction Viw Architctural Viw Bhavioral Viw Structural Viw Itration #1 Goal : to validat th rquirmnts Itration #2 Goal : to spcify th functionalitis Itration #3 Goal : to dsign th architctur of th systm Itration #4 Goal : to prpar th softwar dsign Us cass (UML Us Cass Diagrams) Usr cntrd procsss (BPMN) Usr Intrfac flow diagrams Usr Intrfac graphical dsign Gnral architctur diagram Domain Modl (UML Class Diagrams) Logical architctur (UML Componnt Diagrams) Tabl 5 - TIM Modling Itration Plan Systm cntrd procsss (BPMN) Procssings (UML Squnc Diagram) Data modl (UML Class Diagrams) Objct Modls (UML Class Diagrams) Th itration procss follows th modlling lvls dfind in th TIM modlling architctur. Through this procss, th four modlling viws ar laboratd concurrntly with succssiv lvls of dtails. MSEE Consortium Dissmination: Public 129/143

130 Rcommndations 1) Introduc an itration #0 within th modling approach : o Rviw BSM modls and idntify th scop of th systm to b dtaild at th TIM lvl o Build a clar vision of th to b systm, shard with all th involvd partis (stakholdrs, businss analysis, systm analysis, dvloprs) o Idntify th tchnological risks sinc th initialization of th TIM modls o Evaluat svral scnarios for th gnral architctur of th systm 2) Adopt an itrativ approach, in ordr to rfin th analysis and dsign modls succssivly and to validat th continuous alignmnt with rquirmnts 3) Involv th businss analyst in th validation of ach modling itration 4) Involv th dvlopmnt tam within th laboration of th dsign modls 5) For complx or unstabl rquirmnts, adopt an incrmntal approach for th TIM modling and th implmntation of th systm at TSM. Run succssiv TIM + TSM modling incrmnts ovr diffrnt substs of th rquirmnts MSEE Consortium Dissmination: Public 130/143

131 12. Annx 4 BIVOLINO Customizd Configurator TIM Modls Scop Th scop of this documnt is to prform th analysis and dsign of th BIVOLINO configurator customizr systm. According to th BIVOLINO us cas which is th objct of this study, th analysis focuss on th functional spcification of two complmntary systms: Th configurator customizr : which provids support for tailrs to build spcific shirt configurators in ordr to targt spcific customrs and product rang Th customizd configurator : which rsults of th usag of th prvious systm, and which provids support to onlin customrs for slcting and configuring thir own shirts, on th Tailr s portal Th cas study of BIVOLINO dscribd within this documnt will srv to valuat and improv th mthodology for th laboration of modls at th TIM lvl, within th contxt of srvitization, introducd by th MSEE projct. Th challng of th analysis prformd at th TIM lvl is to achiv th following: Objctiv#1: to laborat th dscription of th systm so that a dvlopr can implmnt it (ithr manually or smi-automatically thanks to cod gnration tools), Objctiv#2: to kp this dscription prfctly alignd with th rquirmnts capturd at th BSM lvl Background Th contnt of this analysis was laboratd with th contribution of BIVOLINO and I-VLAB. HARDIS has ngagd this work aftr I-VLAB had constitutd a first analysis and modling work at th BSM lvl concrning th BIVOLINO us cas. Th following documnts was analysd in dpth by HARDIS and a sris of tlcos took plac in ordr to rfin th analysis, on th priod of Dcmbr 2012, to January Input documnts: Rfrnc Purpos Dat Dcomposition Srvic Modl Bivolino ToolBox v 0.4.doc MSEE _Prp 2èm rviw_ Tlco _Bivolino_ v0 3 doc.doc MSEE _Prp 2èm rviw_ Tlco _Bivolino_ v0.5.doc MSEE _Prp 2èm rviw_ Tlco _Bivolino_ v0 6.doc MSEE _Prp 2èm rviw_ Tlco _Bivolino_ v0 7.doc Summary CC & affilat wizard (1).docx Initializ th modlling of th SLM of th Customizd Configurator us cas (BSM lvl) Minuts of th Tlco on Dcmbr 19th,2012 BSM modlling with BIVOLINO Minuts of th Tlco on Dcmbr 20th,2012 BSM modlling with BIVOLINO Dcmbr 20 th minuts - Rvisd by BIVOLINO Dcmbr 20 th minuts Updatd by I-VLAB Scrn mockups by BIVOLINO 19/12/2012 MSEE Consortium Dissmination: Public 131/143

132 ms-bivolinodatabas.doc.docx RE: MSEE: validation modling bivolino: us cas: Continuation : prparation mting Exp : byvot@bivolino.com BIVOLINO configurator databas physical modl Domain modls of configurator customizr 19/12/ /12/2012 Foundational documnts: Rfrnc MSEE D11.2 Srvic concpt modls mthod at CIM-PIM-PSM lvl V2.pdf Tabl 33 - Input documnts Purpos Dfinition of th MDSEA architctur (modlling lvls, srvic mtamodls, modlling languags). MSEE_dlivrabl_D15.2. Vrsion 1.1.pdf D41.1 MSEE Srvic-Systm Functional and Modular Architctur v1.2.pdf MSEE_D42.1 Gnric_Srvic_Dvlopmnt_Platform_s pcifications_and_architctur_v_0.9_intr nal_rviw_vrsion Spcification & Dsign of th modlling faturs of th SLMToolBox (rsponsibl for BSM & TIM modlling) Gnral spcification of th ovrall MSEE IT Systm architctur Spcification & Dsign of th Gnric Srvic Dvlopmnt Platform (rsponsibl for TSM modlling & softwar dvlopmnt) Qustions to b addrssd Tabl 34 - Foundational documnts Itration Qustion Answr 1 Which xact functionalitis hav alrady bn dvlopd for th configurator customizr systm? Which spcific functionalitis of th systm BIVOLINO xpcts to b gnratd through th modling of MSEE? W idntify 2 sub-systms to b dvlopd : 1) Th systm which an tailr uss to crat / modify a customizd configurator 2) Th systm which provids th customizd configurator as a srvic to th wb portal of th tailr Which on has to b dvlopd? Th softwar which is usd to customiz th configurator ; and th softwar which will provid th customizd configurator as a srvic will b implmntd manually by BIVOLINO. A rfinmnt of th BSM analysis is mandatory in ordr to idntify th most rlvant systm to b dvlopd within MSEE (.g. : Singl sign on implmntation ; subscription procss ; billing procss ; baskt intgration fatur ; ) MSEE Consortium Dissmination: Public 132/143

133 Dos th systm rsponsibl to srv an on dmand customizd configurator to th -tailrs (dpnding on th ID of th affiliait) is alrady dvlopd? Dos on Tailr can / must dscrib svral affiliats within th configurator customizr systm? Is it xpctd that th configurator customizr produc a nw xcutabl instanc of customizd configurator (i..: a nw xcutabl application) ach tim th usr asks for a nw configurator? Or dos this systm will produc a configuration data st to b intrprtd by a uniqu and gnric configurator? (a configurator configuration profil to b intgratd by a Mta configurator?) Dos th configurator customizr should b usd only for shirts or othr kind of products? Dos th login functionalitis (for th tailr on th Bivolino portal) has to b dvlopd and thrfor modld within th configurator customizr analysis? Do th -tailrs nd th customizd configurator to b adaptd to th graphic styl of thir wb sit? If ys, how is it nvisiond to fulfill this rquirmnt with th systm of BIVOLINO? Dos on tailr (xampl : Mark & Spncr) can dclar svral affiliats (xampl : M&S Franc ; M&S UK ; )? Can svral affiliats (xampl : M&S UK ; M&S Brazil ; ) can us th sam configurator? In this cas, a configurator should b abl to b associatd to svral affiliats. Tabl 35 - Qustions to b addrssd It is currntly bing dvlopd by BIVOLINO. Can. It will produc a configuration profil (i.. : data). Also boxrs. Th graphical intgration is prformd manually by BIVOLINO, thanks to a CSS fil. Ys. MSEE Consortium Dissmination: Public 133/143

134 12.4. Ovrall modling architctur Th following figur dpicts how th ovrall TIM modling architctur is instantiatd in our cas study: th configurator customizr of BIVOLINO Gnral architctur Figur 81 - BIVOLINO Modling Architctur Th following figur dpicts th gnral architctur of th systm as it was prsntd during th prvious phon calls with BIVOLINO and I-VLAB, for th laboration of th lowr BSM lvl modls. Figur 82 - BIVOLINO Configurator Customizr - Gnral Architctur MSEE Consortium Dissmination: Public 134/143

135 This architctur covrs thr us cass : UC#1 Crat a custom configurator: an -tailr portal administrator wants to crat a nw custom configurator so that h can provid customizing faturs to its customrs, for crtain product rangs on its portal. To achiv this goal, th procss involvs th following activitis: 1- As a pr-rquisit: a. Th usr must b authnticatd on th BIVOLINO portal b. H nds to hav at last on affiliat profil (cf. UC#2) 2- Th usr slcts and configurs th rlvant options in ordr to dfin th configurator h wants to achiv. A st of forms allows him: a. To slct th affiliat for which h nds a configurator b. To slct th rlvant options (fabrics, dsign options ) through a configurator wizard. Onc h finishs th configuration of th configurator, th data dscribing all th options h has slctd is savd within a databas (datast : configurator dscription ) 3- As a final stat: th configuration profil of th configurator is savd in th information systm of BIVOLINO. UC#2 Configur my affiliat profil: an -tailr portal administrator nds to crat a nw affiliat profil dscription, so that h will b abl to crat spcific configurators for svral countris and subsidiaris. 1- As a pr-rquisit: a. th usr must b authnticatd on th BIVOLINO portal (it mans, h must hav obtain crdntials from BIVOLINO aftr thy agrd on th trm of th srvic contract ) 2- Th usr slcts and configurs th rlvant options (location, company nam, currncy ) in ordr to dfin th affiliat profil h wants to achiv. A st of forms allows him to slct th rlvant options, through an affiliat wizard. Onc h finishs th configuration of th affiliat, th data dscribing all th options h has slctd is savd within a databas (datast : affiliat dscription ) 3- As a final stat: th configuration profil of th affiliat is savd in th information systm of BIVOLINO. UC#3 Buy a custom shirt onlin: an onlin customr of th -tailr wants to buy a custom shirt, within a particular product rang, so that it prfctly suits to its nds and fashion tasts. 1- As a pr-rquisit: a. th usr has slctd a rubric within th onlin catalog of th -tailr wb sit 2- Th -tailr wb portal rachs th information systm of BIVOLINO and asks to rtriv th wb pags of th custom configurator (dpnding on th idntity of th affiliat and th idntity of th custom configurator). Thn, th BIVOLINO information systm : a. Chck for th validity of th affiliat ID and th configurator ID ; in cas of succss : b. Th datasts corrsponding to th configurator dscription and th affiliat dscription ar rtrivd. c. Th systm gnrats th wb pags to b providd and snds thm to th - tailr wb portal MSEE Consortium Dissmination: Public 135/143

136 3- Th onlin customr slcts and configurs th rlvant options for his custom shirt, according to th options providd by th customizd configurator (dpnding on th configurator dscription datast 4- At th nd of th configuration procss, th onlin customr is invitd to add th shirt to its baskt (optionally) and ithr : a. To go back to th onlin catalog b. Or to procd dirctly to th onlin paymnt 5- As a final stat: onc th tailr has rgistrd th paymnt, th configuration profil of th shirt is savd in th information systm of BIVOLINO. All th ncssary information is availabl for th gnration of th cutfil Scop of th analysis Th following tabl summarizs th us cass dscribd prviously and thir currnt dvlopmnt stat, at th tim of th initialization of th analysis. UC# UC Titl Stat 1 Configur my affiliat profil Alrady implmntd. 2 Crat a custom configurator Alrady implmntd 3 Configur a custom shirt (via a customizd configurator) Will b implmntd manually by BIVOLINO Tabl 36 - Scop of th analysis Us cas analysis (UML Us Cas Diagram) Actors & rols Actor (Who?) Objctiv (Why?) Systms involvd To crat a nw customizd Configurator Customizr configurator for a spcific product rang, in ordr to attract nw onlin customrs. E tailr portal administrator (for xampl : th onlin sals managr of Mark & Spncr Franc) Onlin customr To buy a custom shirt onlin, adaptd to its nds, clothing styl and fashion trnds. Tabl 37 - Actors & rols (through th tailr wb portal) Customizd Shirt Configurator For BIVOLINO, w nd two us cas diagrams in ordr to covr th two main usag scnarios, which ar drivn by th objctivs aformntiond UC#1 : Crat a nw customizd configurator Th first us cas diagram concrns th configurator customizr (usd by th tailr : Back offic procss). MSEE Consortium Dissmination: Public 136/143

137 Figur 83 - UC#1 : Crat a nw customizd configurator Actors This diagram rprsnt th -tailr portal administrator as th main actor and its intraction with th configurator customizr systm Objctiv Th actor s objctiv is to customiz a nw configurator in ordr to provid a nw configurabl cloth (.g. shirt) rang to onlin customrs Pr-rquisits - Th tailr portal administrator must b authnticatd on th BIVOLINO portal Dscription Th diagram dpicts two main uss cass: Th gnration of a nw configurator Its dploymnt on th -tailr portal to satisfy customr dmand. Not that th configurator customizr systm will support only th 1 st us cas ( gnration of a nw configurator ). Thrfor, th dploymnt us cas will not b laboratd in this study. Th gnration of a nw customizd configurator is dividd into two main stps Stp#1 Th first stp allows th dclaration of th usr affiliat thanks to a wizard. In this stp, th usr can crat a nw affiliat if it is a first utilization or modify its affiliat if it alrady xists. In th wizard, th usr must provid or modify its affiliat information, notably, th company nam, th usr nam, mail, fax, tc Stp#2 Onc th affiliat is dclard, th usr can prcd to th scond stp in ordr to gnrat a nw customizd configurator. As for th affiliat dclaration, th gnration of customizd configurator rquirs svral paramtr sttings. For this purpos, th information of th diffrnt paramtrs should b don in a squnc of stps in th wizard. Th stps ar dfind as follows: 1. Provid th configurator idntity (.g. configurator nam, articl, gndr), 2. Add configurator collctions 3. Add fabrics 4. Organiz th mnu structur 5. Add dsign options 6. Add dsign sub-options MSEE Consortium Dissmination: Public 137/143

138 7. Slct th monogram typ 8. Customiz th styl UC#2 : Buy a custom shirt onlin (through a spcific customizd configurator) Th scond us cas diagram concrns th us of a customizd configurator; by an onlin customr through th tailr portal (Front offic procss). Figur 84 - UC#2 : Buy a custom shirt onlin (through a spcific customizd configurator) Actors This diagram rprsnt an onlin tail customr as th main actor and its intraction with a particular customizd configurator, through th tailr wb portal Objctiv Th actor s objctiv is to buy a nw customizd shirt, adaptd to its nds and clothing styl Pr-rquisits - Th tailr portal administrator must b authnticatd on th BIVOLINO portal - On or svral customizd configurator ar dployd and oprational within th tailr wb portal Dscription In this diagram ar dscribd th us cass involvd in th customization of a shirt using a customizd configurator by an onlin customr. Onc th customizd configurator is oprational on an tailr portal, final customrs can us it to configur spcific shirts that mt thir rquirmnts. Th final customr must first slct th dsird product rang. Thn h will b invitd to configur th product through th customizd configurator. To this nd, h must ntr svral paramtrs (.g. siz, color, tc.) of its product thanks to a wizard. Th providd paramtrs srv to gnrat th cut fil which will b usd for manufacturing th final product Usr cntrd procsss (BPMN2.0 Diagram) W nd two BPMN diagrams in ordr to spcify th intraction involvd by th two prvious us cass UP#1 : Crat a nw customizd configurator This modl spcifis th procsss involving intractions btwn th E-Tailr portal administrator and Bivolino configurator customizr. MSEE Consortium Dissmination: Public 138/143

139 Figur 85 - Usr Procss : Crat a nw customizd configurator UP#2 : Buy a customshirt onlin Th following procss dscribs th activitis prformd by an onlin customr, in ordr to slct and configur a custom shirt on th Tailr wb portal, thanks to a customizd configurator, providd by BIVOLINO. Assumptions: - Th customizd configurator is providd As A Srvic (SaaS) by BIVOLINO, to th Tailr (From a tchnical point of viw, th customizd configurator is not installd on th Tailr Wb Portal, but is providd As a Srvic by th information systm of BIVOLINO) Figur 86 - Usr Procss : Buy a shirt onlin MSEE Consortium Dissmination: Public 139/143

140 13. Annx 5 INDESIT Car fr washing srvic TIM modls Scop Th scop of this documnt is to produc simpl TIM modls concrning th Car fr washing srvic so that th Srvic Dvlopmnt Platform can b usd to dvlop th Mobil wb sit (front nd + back nd) with th hlp of th mobil dvlopmnt modul Background Ths modls wr laboratd in collaboration with SOFTECO, which is in charg for th dvlopmnt of IT softwar for th INDESIT MSEE Pilot. Th work prformd with th toolbox consistd in: - R-nginring th tchnical modls providd by SOFTECO with th modling functionalitis of th SLMToolBox at TIM lvl - Driv a mor abstract rprsntation of th INDESIT srvic at th BSM lvl, with th SLMToolBox nvironmnt Gnral dscription / ovrviw of th INDESIT cas (BSM lvl) Th following figur dpicts th gnric srvic dscription information collctd at th BSM lvl, through MDSEA modling tmplats (quivalnt to BSM Cor modl). Figur 87 - Gnral dscription / ovrviw of th INDESIT cas (BSM lvl) MSEE Consortium Dissmination: Public 140/143

141 13.4. Gnric procss (Extndd Actigram languag) Th following modl stablishs a high lvl ovrviw of th ovrall procss, involvd within th carfr washing srvic. Figur 88 - Gnric procss (Extndd Actigram languag) Gnral dscription of th modl (TIM lvl) Th following figur dpicts th gnric srvic dscription information collctd at th TIM lvl, through MDSEA modling tmplats (quivalnt to TIM Cor modl). Figur 89 - Gnral dscription of th modl (TIM lvl) MSEE Consortium Dissmination: Public 141/143

142 13.6. UML us cas diagram Th following figur dpicts main us cass supportd by th Carfr washing mobil wbsit. Figur 90 - UML us cas diagram W can notic that two catgoris of actors ar involvd within th us cass : - Th customr consums onlin srvics so that h has accss to his washing machin usag data as wll as rcommndations ( bst practics - An administrator is in charg for administrating th bst practic list as wll as th associatd rcommndation ruls UML componnt diagram of th high lvl architctur Th following figur dpicts th high lvl systm architctur. Th architctur is composd by thr softwar componnts: - WM Data Acquisition: th WM Data acquisition componnt is in charg of rciving th data coming from th washing machins and to stor thm in th WM Data Rpository. - Carfr Washing REST Srvic: th srvic provids two groups of oprations. Th first group nabls th rgistration of th customrs and of th washing machins. Th scond group provids th information on th washing machins of th customrs (i.. global and dtaild data) and on th bst practics to b proposd. MSEE Consortium Dissmination: Public 142/143