INF5120 ”Modellbasert Systemutvikling” ”Modelbased System Development”

Total Page:16

File Type:pdf, Size:1020Kb

INF5120 ”Modellbasert Systemutvikling” ”Modelbased System Development” INF5120 ”Modellbasert Systemutvikling” ”Modelbased System development” Lecture 10: 18.03.2013 Arne-Jørgen Berre [email protected] or [email protected] Telecom and Informatics 1 Content n Oblig 1 and 2 – details n MOF and EMF n Model transformations, EMFText, MOFScript, Java n Model to Model, ATL, Java n Enterprise Architecture - MagicDraw n ISO RM/ODP n UPDM for MODAF/DODAF n SysML Telecom and Informatics 2 INF5120 - Lecture plan - 2013 n 1 (14/1): Introduction – overview Enterprise Architecture with UML and BPMN and DSLs n 2 (21/1): Service Innovation and Design, AT ONE method/workshop – myServiceFellow (Marika Lüders) n 3: (28/1): Value Networks/VDML BPMN, vs. UML Activity diagrams - Oryx n 4 (4/2): User experience and Touchpoints/UI Design – Balsamiq – (Amela Karahasanovic) n 5 (11/2): UML and Req.Modeling –Agile User stories versus Use cases n 6 (18/2): Business-SoaML, Requirements Modeling, Goal Modeling, BMM, and Non Functional requirements n 7 (25/2): Model driven engineering – Metamodels, DSL, UML Profiles etc. NAV on NFR n 8 (4/3): UML Service Modeling – SoaML, UML 2.0 Service composition, MagicDraw n 9 (11/3): Method Engineering, SW Process frameworks , SPEM/EPF, ISO 24744, FACESEM/ESSENCE (Brian Elvesæter) n 10(18/3): Model driven engineering, transformation technologies, (USDL, ISO 19119) n 11(8/4): MDE and DSL in practice, i.e. CloudML/ThingML – Franck Fleurey n 12(15/4): BPMN and Business Process Management and CMMN and Case Management n 13(22/4): UML and Entity and Information modeling, UML, ISO 19103 n 14(29/4): UML and Semantic models, Facts, SBVR, Ontologies, Rules n 15(6/5): UML and Platform models, realisation, migration, Java, Apps, CloudML n 16(13/5): Conclusion and Summary for INF5120 - Preparation for Exam n Exam: Monday June 3rd, 2013, (4 hours) Telecom and Informatics 3 INF5120 – Oblig plan - 2013 n 1 (14/1): Introduction n 2 (21/1): myServiceFellow/Service Design n 3: (28/1): Oryx n 4 (4/2): Balsamiq n 5 (11/2): Use cases 2.0 n 6 (18/2): Oblig 1 – Group work n 7 (25/2): EMF and Eclipse – Group (3) presentation – Business Model, Business-SoaML n 8 (4/3): Oryx– Group (3) presentation - User stories/use cases, UI, NFR n 9 (11/3): Group presentation(s) on Oblig 1: User stories/use cases, UI/Balsamiq n 10(18/3): Group presentation on Oblig 1 – NFR 1 – Parallell Start on Oblig 2 (individual) and Oblig 3 (group) n - 22/3 : Delivery of Oblig 1 n EASTER n 11(8/4): Walk through of Oblig 1 – Questions on Oblig 2 and 3 n 12(15/4): Delivery of Oblig 2 – “Value Network editor in Eclipse” n 13(22/4): Group work, Oblig 3 – Group (x) presentation n 14(29/4): Group work, Oblig 3 – Group (x) presentation n 15(6/5): Delivery of Oblig 3 – “Concierge – SA Model” n 16(13/5): Walk trough of Oblig 3 - Preparation for Exam n Exam: Monday June 3rd, 2013, (4 hours) Telecom and Informatics 4 Oblig 2 (individual) n Value Network – with Eclipse EMF - “Graphical Domain Specific Language (DSL) Editor for Value Networks” n Create a metamodel for Value Networks in EMF n Create a graphical editor for Value Networks – using Eugenia – (as front end for GMF) Telecom and Informatics 5 MDA-compliant Eclipse technologies n Eclipse Modeling Tools: http://www.eclipse.org/downloads/ n Eclipse Modeling Framework (EMF) n http://www.eclipse.org/emf/ n EMF is a modeling framework and code generation facility for building tools and other applications based on a structured data model. n Eclipse Graphical Editing Framework (GEF) n http://www.eclipse.org/gef/ n The Graphical Editing Framework (GEF) allows developers to take an existing application model and quickly create a rich graphical editor. n Eclipse Graphical Modeling Framework (GMF) n http://www.eclipse.org/gmf/ n The Eclipse Graphical Modeling Framework (GMF) provides a generative component and runtime infrastructure for developing graphical editors based on EMF and GEF. n Eugenia n EuGENia is a tool that automatically generates the .gmfgraph, .gmftool and .gmfmap models needed to implement a GMF editor from a single annotated Ecore metamodel n http://www.eclipse.org/epsilon/doc/eugenia/ n Atlas Transformation Language n http://www.eclipse.org/gmt/atl/ n The ATL project aims at providing a set of transformation tools for GMT. These include some sample ATL transformations, an ATL transformation engine, and an IDE for ATL (ADT: ATL Development Tools). n Eclipse Process Framework (EPF) n http://www.eclipse.org/epf/ n To provide an extensible framework and exemplary tools for software process engineering - method and process authoring, library management, configuring and publishing a process. Telecom and Informatics 6 EMFText - MOF to text n http://www.emftext.org/index.php/EMFText Telecom and Informatics 7 Introduction ATHENA Model-Driven Interoperability (MDI) Framework MDA & Interoperability Metamodelling Reusable MDI Assets UML Profiles & DSLs • Method chunks • Tools and services • Models and metamodels Model Transformations • Model transformations • DSLs and UML profiles • Reference examples Method Engineering Telecom and Informatics 8 Model to Text transformation 1/2 n MDA places modelling at the heart of the software development process. n Various models are used to capture various aspects of the system in a platform independent manner. n Sets of transformations are then applied to these platform independent models (PIM) to derive platform specific models (PSM). n These PSMs need to be eventually transformed into software artefacts such as code, deployment specifications, reports, documents, etc. n It is also common to generate code directly from PIM-like models. (DSL approach) Telecom and Informatics 9 Model to Text transformation 1/2 n QVT, ATL and MOFScript M2M addresses the need of model – to – model transformation (e.g., PIM – to – PIM, PIM – to – PSM and PSM – to – PSM) n The MOF Model to Text (mof2text) standard addresses how to translate a model to various text artefacts such as code, deployment specifications, reports, documents, etc. n Essentially, the mof2text standard needs to address how to transform a model into a linearized text representation. n An intuitive way to address this requirement is a template based approach wherein the text to be generated from models is specified as a set of text templates that are parameterized with model elements. Telecom and Informatics 10 Motivation n Why do we need model-to-text transformation? n Raise the level of abstraction n Systems are getting more complex n Raise of abstraction has proven useful (for instance: Assembly to COBOL) n Automation of the software development process n Decrease development time n Increase software quality n Focus on the creative part n Automatic generation of new artefacts from your models n Java, EJB, JSP, C# n SQL Scripts n HTML n Test cases n Model documentation Telecom and Informatics 11 Alternatives n What are the alternatives? n Programming languages (e.g Java), n Template/scripting languages (e.g XSLT, OaW, Eclipse Java Emitter Templates – JET, OMG MOF Model 2 Text) n Model Transformation Languages (e.g. ATLAS Transformation Language (ATL)), proprietary UML-based script languages, DSL-based approaches, Other MOF- based text/code generators n Properties of the alternatives: n Neither programming languages nor scripting languages tend to take advantage of source metamodels. n However, it can be done programmatically in Java (e.g. using Eclipse Modelling Framework (EMF)) n Model 2 Model Transformation languages such as ATL is metamodel-based, but is not designed with text generation in mind. However, it can be done also in ATL n UML tool script languages are tied to both UML and a vendor, and are not based on standards. n DSLs provides the flexibility of metamodel-based tools; they typically hard code code generation for each domain-specific language. n The difference between a MOF-based approach and a DSL is not significant, as transformations in MOF-based approaches also will depend on a particular metamodel. n Other MOF-based text generators have not been available, but will emerge. Telecom and Informatics 12 OMG Request for Proposal for a model-to- text transformation language n OMG RFP Issued in 2004 n Mandatory Requirements: n Generation from MOF 2.0 models to text n Reuse (if applicable) existing OMG specifications, in particular QVT n Transformations should be defined at the metalevel of the source model n Support for string conversion of model data n String manipulation n Combination of model data with hard coded output text n Support for complex transformations n Multiple MOF models as input (multiple source models) n Optional Requirements n round-trip engineering n detection/protection of hand-made changes for re-generation n traceability is a (possible) means of supporting the last two. Telecom and Informatics 13 MOF to Text Overview n A template-based approach wherein a Template specifies a text template with placeholders for data to be extracted from models. n These placeholders are essentially expressions specified over metamodel entities with queries being the primary mechanisms for selecting and extracting the values from models. n These values are then converted into text fragments using an expression language augmented with a string manipulation library. n Template can be composed to address complex transformation requirements. Large transformations can be structured into modules having public and private parts. Telecom and Informatics 14 MOF to Text Example [template public classToJava(c : Class)] class Employee class [c.name/] { { // Attribute declarations // Attribute declarations [attributeToJava(c.attribute)] String name; // Constructor Department dept; [c.name/] () { Double salary; } } // Constructor [/template] Employee() { [template public attributeToJava(a : Attribute)] [a.type.name/] [a.name/]; } [/template] } Telecom and Informatics 15 Language details 1/3 n Instead of defining two templates separately, a template can iterate over a collection by using the for block.
Recommended publications
  • WG1 Terminology Work of IEC Syc on Smart City Systems
    WG1 Terminology Work of IEC SyC on Smart City Systems Dr. Xiaomi An, Professor at Renmin University of China Convener of WG1, IEC SyC on Smart Cities January 14, 2019, Seoul, Korea Third ITU Workshop on Data Processing and Management for IoT and Smart Cities and Communities INTERNATIONAL ELECTROTECHNICAL COMMISSION Outline • Members of the WG1 • The stages of work of WG1 • The work plan of WG1 • Joint work of WG1 with ISO and ITU • An Integrated methodology frameworks for smart city system concept system building: common concerns of SDOs • An integrated methodology framework for smart city system concept system building: applications to the two NWIPs Members of the WG1 • 35 experts • 11 countries – China 8 – US 7 – India 5 – Korea 4 – RU 4 – GB 2 – CH 1 – DE 1 – JP 1 – SE 1 – ZA 1 Vocabulary NWIP, November 16, 2018 WD, December 11, 2018 Smart City System- Methodology for concepts and taxonomies building: Justification it as an IS, February 12, 2018// Methodology for terminology work and concept system building: an overview, April 20, 2018// Existing concept models of smart city systems from standards developers, May 20, 2018// Concept System Building for Smart City System: Methodology Studies in Progress, June 9, Methodology NWIP, 2018// November 16, 2018 Recommendations for US WD, December meeting, June 26, 2018 2018 Project team of Vocabulary Chair: Xiaomi An Experts: from 6 countries Experts: Document SyCSmartCities/50/NP Country: CH First name Last name Email Alexander Samarin [email protected] Country: CN First name Last
    [Show full text]
  • DELIVERABLE D.A1.1.1 First Version of State of the Art in Enterprise
    IP- Project / Programme ATHENA IP- Project - No 507849 ATHENA - Project Enterprise Modelling in the Context of Collaborative Enterprises ATHENA - Project Number A1 Document Deliverable D.A1.1.1 Save Date 27/08/2004 Programme Integrating and Strengthening the European Research Strategic Objective Networked Businesses and Governments Integrated Project / Programme Title Advanced Technologies for Interoperability of Heterogeneous Enterprise Networks and their Application Acronym ATHENA Project No 507849 ATHENA – Project Name Enterprise Modelling in the Context of Collaborative Enterprises ATHENA - Project No A1 DELIVERABLE D.A1.1.1 First Version of State of the Art in Enterprise Modelling Techniques and Technologies to Support Enterprise Interoperability Work package – A1.1 Leading Partner: ESI Document Owner: Ana Belén García Díez Security Classification: Public July, 2004 Version 1.2 IP- Project / Programme ATHENA IP- Project - No 507849 ATHENA - Project Enterprise Modelling in the Context of Collaborative Enterprises ATHENA - Project Number A1 Document Deliverable D.A1.1.1 Save Date 27/08/2004 Versioning and contribution history Version Description Comments 0.1 First draft. Based on WD.A1.1.1 0.2 Template and assignments. Prepared in Mallorca meeting. 0.3 Template updated: To be completed by y After the Mallorca meeting, University of Bordeaux kindly offered partners themselves to provide inputs for section 13 (Definitions and Acronyms), based on the definitions in existing standards. y Re-organisation of some sections to avoid 5 levels of subsections, which is a disturbing practice that makes the reader lose the context. Distribution to partners (04/06/2004) 0.4 Some minor adaptations of the template to be consistent with the one As requested by proposed by PlatteConsult, and addition of the “Deliverable Process PlatteConsult.
    [Show full text]
  • Industrial Automation
    ISO Focus The Magazine of the International Organization for Standardization Volume 4, No. 12, December 2007, ISSN 1729-8709 Industrial automation • Volvo’s use of ISO standards • A new generation of watches Contents 1 Comment Alain Digeon, Chair of ISO/TC 184, Industrial automation systems and integration, starting January 2008 2 World Scene Highlights of events from around the world 3 ISO Scene Highlights of news and developments from ISO members 4 Guest View ISO Focus is published 11 times Katarina Lindström, Senior Vice-President, a year (single issue : July-August). It is available in English. Head of Manufacturing in Volvo Powertrain and Chairman of the Manufacturing, Key Technology Committee Annual subscription 158 Swiss Francs Individual copies 16 Swiss Francs 8 Main Focus Publisher • Product data – ISO Central Secretariat Managing (International Organization for information through Standardization) the lifecycle 1, ch. de la Voie-Creuse CH-1211 Genève 20 • Practical business Switzerland solutions for ontology Telephone + 41 22 749 01 11 data exchange Fax + 41 22 733 34 30 • Modelling the E-mail [email protected] manufacturing enterprise Web www.iso.org • Improving productivity Manager : Roger Frost with interoperability Editor : Elizabeth Gasiorowski-Denis • Towards integrated Assistant Editor : Maria Lazarte manufacturing solutions Artwork : Pascal Krieger and • A new model for machine data transfer Pierre Granier • The revolution in engineering drawings – Product definition ISO Update : Dominique Chevaux data sets Subscription enquiries : Sonia Rosas Friot • A new era for cutting tools ISO Central Secretariat • Robots – In industry and beyond Telephone + 41 22 749 03 36 Fax + 41 22 749 09 47 37 Developments and Initiatives E-mail [email protected] • A new generation of watches to meet consumer expectations © ISO, 2007.
    [Show full text]
  • EA Management in the German Public Sector: an Initial Perspective on Priorities
    EA Management in the German Public Sector: An Initial Perspective on Priorities Anna Sonnenberger1 and Kurt Sandkuhl2 1,2 BEC, Elmenhorst, Germany 2 Institute of Computer Science, University of Rostock, Germany [anna.sonnenberger, kurt.sandkuhl]@uni-rostock.de Abstract. Worldwide, Enterprise Architectures (EAs) have been gaining popu- larity due to benefits, like, e.g., increased transparency of dependencies between business and technology, reduction of efforts for system customization or opti- mizing integrated and enterprise-wide processes and matching actions. Private businesses and the public sector show significant differences in the use of EA. Thus, the application of reference architectures originating from the private sec- tor for purposes in the public sector creates substantial challenges. For a better understanding of the challenges, it is necessary to identify the most affected EA layers and the insufficiently defined, modeled or described elements of EA models in general. Based on an investigation in the Germany, this paper identi- fies weaknesses of EA in the public sector, like an incompletely modeled tech- nology layer, and also strengths, such as existing definitions, descriptions and models of enterprise objectives. These findings are the foundation for deriving actions and recommendations to strengthening the existing structure and turning it into a coherent overall architecture for federal and state agencies in Germany. Keywords: Enterprise Architecture, Enterprise Architecture Management, Ref- erence Models and Architecture, Public Sector. 1 Introduction Fundamentally, IT is gaining in importance, making the development of IT strategies necessary. A holistic and guiding strategy development cannot be reduced to solely the IT perspective or solely the business perspective. Both must be adapted and tuned to achieve long term goals such as transparency, cost reduction and short term process adjustment [3, 4, 9, 18, 23, 24].
    [Show full text]
  • Model Driven Service Engineering M12 Issue
    Project ID 284860 MSEE – Manufacturing SErvices Ecosystem Date: 02/11/2012 Deliverable D11.2 – M12 issue D11.2 Service concepts, models and method: Model Driven Service Engineering M12 issue Document Owner: Y. Ducq (UB1), G. Doumeingts (I-VLab), C. Lieu (I-VLab), D. Chen (UB1), T. Alix (UB1), G. Zacharewicz (UB1) Contributors: Dissemination: Public Contributing to: WP 1.1 Date: 15.11.2012 Revision: Version 1.0 Project ID 284860 MSEE – Manufacturing SErvices Ecosystem Date: 02/11/2012 Deliverable D11.2 – M12 issue e VERSION HISTORY 1. DATE NOTES AND COMMENTS 2. 02.11.2012 FIRST REVIEW OF D11.1 AND MODIFICATION OF INTRODUCTION AND MAIN PARTS BY UB1 3. 10.11.2012 MODIFICATIONS OF MANY PARTS AS TEMPLATES, MDSE ARCHITECTURE, AND DESCRIPTION OF MODELLING LEVELS 4. 15/11/2012 INTRODUCTION OF THE APPLICATION AT BIVOLINO 5. 16/11/2012 PRESENTATION OF ALL THE MODELS DONE USING THE SLM TOOLBOX 6. DELIVERABLE PEER REVIEW SUMMARY Addressed () ID Comments Answered (A) 1 Exec summary to be emphasised Done 2 MSEE Consortium Dissemination: Public 2/137 Project ID 284860 MSEE – Manufacturing SErvices Ecosystem Date: 02/11/2012 Deliverable D11.2 – M12 issue e TABLE OF CONTENTS 1. EXECUTIVE SUMMARY 8 2. INTRODUCTION 10 3. PRINCIPLES AND CONCEPTS OF SERVICE AND SERVICE SYSTEM MODELLING 11 3.1. From service to servitization 11 3.2. MSEE Servitization Concepts 13 3.3. From Enterprise to Manufacturing Service Ecosystem 15 3.4. Service System and Service System Life cycle Management 16 3.5. The Modeling of the Service System 21 3.6. Architecture for Service System Engineering 29 3.7.
    [Show full text]
  • Sborník Příspěvků 7. Letní Škola Aplikované Informatiky
    MASARYKOVA UNIVERZITA Sborník p řísp ěvk ů 7. letní škola aplikované informatiky Indikátory ú činnosti EMS podle odv ětví Edito ři Ji ří H řebí ček Jan Ministr Tomáš Pitner Bed řichov, 3.– 5. zá ří 2010 Brno 2010 © nakladatelství Littera, 2010 ISBN 978-80-85763-59-1 Slovo úvodem 7. letní škola aplikované informatiky navázala na předchozí letní školy aplikované (environmentální) informatiky v Bed řichov ě, které se zde konají od roku 2002 s výjimkou roku 2004, kdy se letní škola konala v Šubí řov ě a roku 2005, kdy byla hlavní akcí Masarykovy univerzity v oblasti environmentální informatiky 19. mezinárodní konference Informatics for Environmental Protection - EnviroInfo 2005 s nosným tématem Networking environmental information , kterou hostila Masarykova univerzita ve dnech 7. až 9. zá ří 2005 se v brn ěnském hotelu Voron ěž. V letech 2006 a 2009 se letní školy konaly op ět v Bed řichov ě. V letošním roce 7. letní škola aplikované informatiky se konala ve dnech 3. až 5. zá ří 2010 v Bed řichov ě v rámci řešení projektu SP/4i2/26/07 „ Návrh nových indikátor ů pro pr ůběžné monitorování ú činnosti systém ů environmentálního managementu podle odv ětví a systému jejich environmentálního reportingu s hodnocením vazeb mezi životním prost ředím, ekonomikou a spole čností “, zkrácen ě Indikátory ú činnosti EMS podle odv ětví , který je realizován Masarykovou univerzitou v letech 2007 – 2010 v rámci „Resortního programu výzkumu v p ůsobnosti Ministerstva životního prost ředí“ s po čátkem řešení projekt ů v roce 2007 s finan ční podporou Ministerstva životního prost ředí. Odborné diskusi k řešení projektu a problematice dobrovolného reportingu a tvorb ě indikátor ů byla v ěnována nejv ětší část jednání na této letní škole.
    [Show full text]
  • An Enterprise Architecture Framework for the Digital Age
    eKNOW 2018 : The Tenth International Conference on Information, Process, and Knowledge Management The Digital Diamond Framework: An Enterprise Architecture Framework for the Digital Age Roy Oberhauser Computer Science Dept. Aalen University Aalen, Germany email: [email protected] Abstract—Enterprise architecture (EA) frameworks of the past micro functionality deployments. Software/data functionality have attempted to support the cohesive and comprehensive becomes easily reusable and accessible via standard protocols modeling and documentation of the enterprise, often with a and formats independent of programming language or focus on business and information technology (IT). However, platform. Its scale can be seen in various “death star”-like the digitalization of enterprises and the complexity of IT have microservice network landscape visualizations (see Figure 1) outgrown these matrix box-like frameworks. This paper proposes a digital, holistic, and sustainable EA framework, called the Digital Diamond Framework, to support digitized enterprises in aligning the real EA state with the desired state. Keywords- enterprise architecture frameworks; enterprise architecture; enterprise modeling; business architecture; digitalization. I. INTRODUCTION Enterprise Architecture (EA) is concerned with comprehensively modeling and documenting the structure and Figure 1. Visualization of microservices at Amazon [4]. behavior of the business and IT infrastructure of an enterprise In lieu of these major trends, the reality that EA is in a cohesive way as a set of artifacts in order to communicate, attempting to comprehensively model, document, and change implement change, and develop insights in support of strategic has become much more complex than in previous decades. business planning and management science. Historically, EA The era of siloed functional teams and applications is fading, emerged from a necessity to document information systems and a highly networked and integrated digitized era has begun.
    [Show full text]
  • ILNAS-EN ISO 19439:2006 a ILN a I V Y P O C Y L N O Enterprise Integration - Framework for W Ie V Enterprise Modelling (ISO 19439:2006) E R P
    p o h S - e S A ILN a i v y p o C y l n o Enterprise integration-Frameworkfor Unternehmensintegration -Rahmenwerk enterprise modelling(ISO19439:2006) w ie für dieUnternehmensmodellierung- v e r P modélisation d'entreprise(ISO ILNAS-EN ISO19439:2006 - Entreprise intégrée-Cadrede Festlegung (ISO19439:2006) 2006 : 19439 19439:2006) 04/2006 ISO EN - S A ILN ILNAS-EN ISO 19439:2006 p o h S - e S A https://portail-qualite.public.lu/fr/normes-normalisation/participer-normalisation.html - - - CENELEC) andInternational(ISO,IEC)standards: participate forFREEinthedevelopmentofLuxembourgish(ILNAS),European(CEN, Every interestedparty,whichismemberofanorganizationbasedinLuxembourg,can ILNAS-EN ISO19439:2006. This EuropeanStandardENISO19439:2006wasadoptedasLuxembourgish National Foreword ILN a i v y p Participate intechnicalcommitteemeetings Foresee futuredevelopments Participate inthedesignofstandards o C or anyotherdatacarrieswithoutpriorpermission! any formorbymean-electronic,mechanical, photocopying Nothing fromthispublicationmaybereproduced orutilizedin THIS PUBLICATIONISCOPYRIGHTPROTECTED y l n o w ie v e r P - 2006 : 19439 ISO EN - S A ILN EUROPEAN STANDARDILNAS-EN ISO 19439:2006EN ISO 19439 NORME EUROPÉENNE EUROPÄISCHE NORM April 2006 ICS 25.040.40 Supersedes ENV 40003:1990 English Version Enterprise integration - Framework for enterprise modelling (ISO 19439:2006) Entreprise intégrée - Cadre de modélisation d'entreprise Unternehmensintegration - Rahmenwerk für die (ISO 19439:2006) Unternehmensmodellierung - Festlegung (ISO 19439:2006) p o h S - e This European Standard was approved by CEN on 3 February 2006. S A CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national ILN standards may be obtained on application to the Central Secretariat or to any CEN member.
    [Show full text]
  • Praxeme Et… Les Règles Métier Pour Prendre Des Décisions
    Atelier public du Praxeme Institute Mardi 25 novembre 2014 Praxeme et… les règles métier pour prendre des décisions Thierry BIARD Ambesas 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Thierry BIARD • Consultant indépendant – Ambesas EIRL Chef de Projets IT Spécialiste EDI & EAI Domaine Transport & Logistique • Projet de recherche doctoral Laboratoire Génie Industriel École Centrale Paris & Lille http://www.lgi.ecp.fr/pmwiki.php/PagesPerso/TBiard Ambesas 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Sommaire • Projet de recherche doctoral sur l’Architecture d’Entreprise. • Présentation du nouveau standard de l’OMG DMN (Decision Model and Notation) pour la formalisation des prises de décision selon les règles métier. • Complémentarité de DMN avec d’autres standards de l’OMG : BMM, SBVR, CMMN et surtout BPMN. • Eléments graphiques et langage de DMN. Interfaçage avec BPMN 2.0. • Travail sur le métamodèle de DMN pour un projet d’outillage. • Débat, échange sur ces sujets et sur leur capacité d'apport méthodologique. Ambesas 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Projet de recherche doctoral sur l’Architecture d’Entreprise 1/2 • Comment rendre la méthode publique d’Architecture d’Entreprise Praxeme encore plus rigoureuse* et plus efficace** ? * avec une approche scientifique pour la preuve de concept ** avec une démarche d’ingénierie pour la mise en application Ambesas 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
    [Show full text]
  • National Intelligent Manufacturing Standard System Construction
    2015) (Version National Intelligent ManufacturingGuidelines Standard System Construction GuidelinesConstruction System (Version 2015) Standard Manufacturing December 2015 Intelligent National Table of Contents I. General Requirements ........................................................................... 2 (i) Guiding ideology .................................................................................. 2 2015) (ii) Basic principle ................................................................................... 3 (iii) Construction target ............................................................................. 4 (Version II. Construction Idea .................................................................................. 6 (i) Fig. 1 Intelligent manufacturing system framework ............................ 7 Guidelines (ii) Structural diagram of intelligent manufacturing standard system ... 17 (iii) Framework of intelligent manufacturing standard system .............. 20 III. Construction Contents ...................................................................... 22 Construction (i) Basic generality standards .................................................................. 22 (ii) Key technique standards ................................System .................................. 27 (iii) Key industries standards .................................................................. 43 Standard IV. Implementation Organization .......................................................... 46 Appendix 1: Terms and Abbreviations
    [Show full text]
  • Enterprise Architecture Jeanne W
    Journal of E nterprise Architecture February 2012, Volume 8, Number 1 FEATURES Editor’s Corner: John Gøtze Architect in the Spotlight: Mark Perry ARTICLES SEA Change: How Sustainable EA Enables Business Success in Times of Disruptive Change Leo Laverdure and Alex Conn PhD Maturity Matters: Generate Value from Enterprise Architecture Jeanne W. Ross and Cynthia M. Beath Improving Government Enterprise Architecture Practice – Maturity Factor Analysis Adegboyega Ojo, Tomasz Janowski, and Elsa Estevez Architecture Styles Indranil Bhattacharya, Enterprise Architect, Deutsche Telekom The Impact of Enterprise Architecture Principles on the Management of IT Investments Mats-Åke Hugoson, Thanos Magoulas, and Kalevi Pessi Can a Re-Discovery of Open Socio-Technical Systems Strengthen EA? James Lapalme and Donald W. de Guerre CASE STUDY The Enterprise Architecture Approach to Support Concept Development in a Military Context: A Case Study Evaluation of EA’s Benefits Jukka Anteroinen and Juha-Matti Lehtonen BOOK REVIEW Thinking in Systems: A Primer Review by Leonard Fehskens https://www.globalaea.org/journal Journal of Enterprise Architecture Chief Editor: John Gøtze, PhD, IT University of Copenhagen Associate Editors Andy Blumenthal James Lapalme, PhD Division Chief, US Department of State Enterprise Architecture Consultant and Researcher Tyson Brooks, PMP Haiping Luo, PhD School of Information Studies, Syracuse University International Trade Administration, US Dept. of Commerce Dick Burk Stephen Marley, PhD Enterprise Architect Harris Corporation
    [Show full text]
  • Progress File (Standards Publications)
    IRISH STANDARDS PUBLISHED BASED ON CEN/CENELEC STANDARDS 1. I.S. EN 2336:1988/AC1:1988 Date published 1 JANUARY 2006 Aerospace Series - Bearings, Spherical Plain in Steel with Assembly Slots - Dimensions and Loads 2. I.S. EN 28378-1:1989/AC1:1989 Date published 1 JANUARY 2006 Information Processing - Data Interchange on 130 mm (5.25") Flexible Disk Cartridges Using Modified Frequency Modulation Recording at 7958 ftprad, 3.8 tpmm (96 tpi), on Both Sides - Part 1: Dimensional, Physical and Magnetic Characteristics. (ISO 8378-1, 1st Edition, 3. I.S. HD 1215-2:1988/AC1:1989 Date published 1 JANUARY 2006 Thermostatic Radiator Valves - Part 2 : Dimensions and Details on Connection 4. I.S. EN 50203:1996/A1:1999 Date published 2 FEBRUARY 2006 Automatic channel installation (ACI) 5. I.S. EN 54-2:1999 Date published 1 JANUARY 2006 Fire detection and fire alarm systems - Part 2: Control and indicating equipment 6. I.S. EN 12737:2004 Date published 28 JULY 2006 Precast concrete products - Floor slats for livestock 7. I.S. EN 61009-1:1994/A13:2004 Date published 2 FEBRUARY 2006 Electrical accessories - Residual current operated circuit-breakers with integral overcurrent protection for household and similar uses (RCBO's) -- Part 1: General rules 8. I.S. EN 50091-1-1:2004 Date published 2 FEBRUARY 2006 Uninterruptible power systems (UPS) -- Part 1-1: General and safety requirements for UPS used in operator access areas 9. I.S. EN 60432-1:2004 Date published 2 FEBRUARY 2006 Incandescent lamps - Safety specifications -- Part 1: Tungsten filament lamps for domestic and similar general lighting purposes (IEC 60432-1:1999 (MOD)) 10.
    [Show full text]