© 2005-2006 The ATHENA Consortium. EM1 - Enterprise Modelling as a way to achieve Interoperability Module 1 - What is Enterprise Modelling?

Slides:



Advertisements
Similar presentations
© The ATHENA Consortium From PIM4SOA to Web Services,
Advertisements

Information Systems Analysis and Design
© The ATHENA Consortium. CI2: The ATHENA Interoperability Framework Module 2: e-Procurement Scenario Furniture Sector 2.
Training of master Trainers Workshop 10 – 15 November 2012 e-Services Design and Delivery Module IIX Emilio Bugli Innocenti.
Reference Architecture for Enterprise Integration CIMOSA GRAI/GIM PERA Dima Nazzal.
1Business Models – REA Ontology Resources Events Agents The REA Ontology.
COPYRIGHT © 2008 Thomson South-Western, a part of The Thomson Corporation. Thomson, the Star logo, and South-Western are trademarks used herein under license.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
Information Systems within the Organization
Certified Business Process Professional (CBPP®)
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Innovation in operations and processes Lesson 6 Chapter 8 + slides.
Quality Management in Web-based Learning - A Finnish perspective Kristiina Karjalainen Lappeenranta University of Technology FVU Seminar 20 June 2005.
© The ATHENA Consortium. CI2: The ATHENA Interoperability Framework Module 3: Collaborative Product Development Scenario Aeronautics and Aerospace.
A c c e l e r a t i n g Y o u r S u c c e s s ™ Electronics Marketing: Electronic Components EMEA Core Distribution Services Financial Strength & Inventory.
TRAINING SOLUTIONS ISO 14001: DEVELOPMENT & IMPLEMENTATION For more information contact Victoria: (Tel) (Fax) ( )
© The ATHENA Consortium. EM1 - Enterprise Modelling as a way to achieve Interoperability Module 4 - How does Enterprise Modelling address these.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
14-1 Chapter 14 Managing Knowledge Applying Innovation By David O’Sullivan and Lawrence Dooley © Sage Publications 2008.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
© The ATHENA Consortium From PIM4SOA to Peer-2-Peer (P2P),
© The ATHENA Consortium. EM1 - Enterprise Modelling as a way to achieve Interoperability Module 2 - What are the current methods and tools for.
1 Chapter Client-Server Interaction. 2 Functionality  Transport layer and layers below  Basic communication  Reliability  Application layer.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
© The ATHENA Consortium. CI2: The ATHENA Interoperability Framework Module 1: The ATHENA Interoperability Framework.
Rational Unified Process Fundamentals Module 4: Disciplines II.
Instructore: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Requirement engineering.
Quality Management.  Quality management is becoming increasingly important to the leadership and management of all organisations. I  t is necessary.
© The ATHENA Consortium. CI3 - Practices of Interoperability in SMEs Carrier-Shipper Scenario.
© The ATHENA Consortium. 6-3b. Atlas Transformation Language (ATL) Tutorial / Exercise,
DELMIA DPM Assembly This is the Master “Presentation title” page. Type the title of your presentation in the "Presentation title” field. Cette page est.
© The ATHENA Consortium. AP6 – Model-Driven Development of Interoperable Web Services, Agents and P2P Solutions Learn about model transformations.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 6 System Engineering Overview of System Engineering.
1 CIM OSA CIMOSA Computer Integrated Manufacturing Open System Architecture 1 David CHEN IMS-LAPS, University Bordeaux 1.
Illustrations and Answers for TDT4252 exam, June
© The ATHENA Consortium. CI2: The ATHENA Interoperability Framework Module 5: Supply Chain Management (SCM) Automotive sector.
© The ATHENA Consortium. EM1 - Enterprise Modelling as a way to achieve Interoperability Module 5 - Enterprise modelling establishment methodology.
© Copyright Simon Wallace, February 2002 Process Product There are Many Aspects to Business Change - it’s not just the Technology Culture People Strategy.
Understanding Networked Applications: A First Course Ideas and examples (Chapter 6) by David G. Messerschmitt.
Systems Analysis and Design in a Changing World, Fourth Edition
Capturing the requirements  Requirement: a feature of the system or a description of something the system is capable of doing in order to fulfill the.
Pleasing in appearance.
Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.
PRJ566 Project Planning & Management Software Architecture.
Funded by: © AHDS Preservation in Institutional Repositories Preliminary conclusions of the SHERPA DP project Gareth Knight Digital Preservation Officer.
McGraw-Hill/Irwin © 2005 The McGraw-Hill Companies, Inc., All Rights Reserved. Module 20W Managing Technology.
© The ATHENA Consortium. EM1 - Enterprise Modelling as a way to achieve Interoperability Module 3 - What interoperability problems does Enterprise.
CSE 303 – Software Design and Architecture
1 Margaret Christison Head of Product Data Standards Product Information Standards Defence Logistics 2004.
Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts Rational Unified Process Fundamentals Module 4: Core Workflows II - Concepts.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
Based on material developed in ATHENA (IST ), INTEROP (IST ) and MODELWARE (IST ) 6-1b. Atlas Transformation Language (ATL) with RSM.
4+1 View Model of Software Architecture
Outlines Overview Defining the Vision Through Business Requirements
© The ATHENA Consortium. CI3 - Practices of Interoperability in SMEs Proposed Solutions.
Software Engineering Lecture 10: System Engineering.
1 4th of October, 2006 © ATHENA Consortium 2006 B5 EADS CCR piloting Nicolas Figay, EADS Flora Robin, EADS ATHENA Intermediate Review October 2006.
CommUNITY Barnet. Social Enterprise Toolkit Social Enterprise People define it differently but … it is widely understood as: An organisation that trades.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
© The ATHENA Consortium. 5-2b. Eclipse Modeling Framework (EMF) Tutorial / Exercise,
5-4b. Eclipse Process Framework (EPF) Tutorial / Exercise
SALES COORDINATOR Sydney
The Development Process of Web Applications
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Overview of System Engineering
The Knowledge Sharing Center is an independent and non-profit knowledge platform.
CS 8532: Advanced Software Engineering
Presentation transcript:

© The ATHENA Consortium. EM1 - Enterprise Modelling as a way to achieve Interoperability Module 1 - What is Enterprise Modelling?

2 © The ATHENA Consortium. Module 1 - What is Enterprise Modelling? Module Structure: 1. Enterprise Modelling 2. Enterprise Model Example

3 © The ATHENA Consortium. Enterprise Modelling (EM) is a capability for externalising, making and sharing enterprise knowledge. EM tools can either be: used stand-alone to produce various kinds of model views, integrated as front-ends to other systems, part of an environment providing a contextual user-environment. What is Enterprise Modelling?

4 © The ATHENA Consortium. “Collaborative Enterprises will be supported seamlessly by EM during all life-cycles“. OEM V Target Setting Sourcing Partial Process Model (OEM View) ARIS Model Partial Process Model (Supplier View) IEM Model Changes (external/ internal) Concrete Product idea Customer Order accepted Change accepted Design order accepted Product Life Cycle pre- development Technology Market trends Innovation Acquisition and offer generation Different aspects of the same process from different perspectives Enterprise Modelling in the Context of Collaborative Enterprises

5 © The ATHENA Consortium. Enterprise Modelling Application Domains Enterprise engineering and reengineering Product life cycle management Choice and implementation of IT systems and solution General enterprise architecture and operations support

6 © The ATHENA Consortium. Enterprise engineering and reengineering Enterprise engineering and reengineering Enterprise Engineering and Reengineering

7 © The ATHENA Consortium. Enterprise engineering and reengineering Enterprise engineering and reengineering Product Life Cycle Management

8 © The ATHENA Consortium. Enterprise engineering and reengineering Enterprise engineering and reengineering Choice and implementation of IT systems and solution Choice and implementation of IT systems and solution Choice and implementation of IT systems and solutions

9 © The ATHENA Consortium. Enterprise engineering and reengineering Enterprise engineering and reengineering Choice and implementation of IT systems and solution Choice and implementation of IT systems and solution Wertschöpfende anwenden verteilen speichern Wissensziele Identifizieren Geschäftspro zesse erzeugen General Enterprise architecture and operations support General Enterprise architecture and operations support General Enterprise architecture and operations support

10 © The ATHENA Consortium. Process model Order (State n) Order (State n+1) Product (State n) Product (State n+1) Resource (State n) Resource (State n+1) Action Business process Inheritance Process Chain ProductsOrdersResources Information model Object Class Structure (green)(blue)(red) Enterprise Model Example (IEM / MO²GO)

11 © The ATHENA Consortium. Basic Elements Action Order Product Resource Description of object states Process description X = 1 X = 0 X = 1 Connection between actions and objects or between actions. Split: both processes run In parallel. Decision: the process sequence depends on the object states following the decision element Join: different sequences are joining to one sequence Loop: several iterations of process steps Connection Elements Basic Structure of the Process model control support transformation “Generic Activity Model“ IEM Modelling elements

12 © The ATHENA Consortium. Level 2 Check the incoming order Level 1 Zielverein- barungs- verfahren Strategische Planung Customer order processing Check the storage level of the ordered product Abstraction Detailing Steuerung Repression Informations- sammlung u. Problemanalyse Zielverein-barungs-verfahren Strategische Planung Controlling Prävention betreiben Level 0 Business process model Process Hierarchies

13 © The ATHENA Consortium. produce product Product produced Product designed Production order Leader assembly Procedure instructions Production Planning System Organisation unit Documentation IT-System change support control IEM Illustration of a Process

14 © The ATHENA Consortium. Supplier Process Model

15 © The ATHENA Consortium. Ports ControlOutputResourceInput Supplier Process Model

16 © The ATHENA Consortium. OEM Model (Original Equipment Manufacturer)

17 © The ATHENA Consortium. This course has been developed under the funding of the EC with the support of the EC ATHENA-IP Project. Disclaimer and Copyright Notice: Permission is granted without fee for personal or educational (non-profit) use, previous notification is needed. For notification purposes, please, address to the ATHENA Training Programme Chair at In other cases please, contact at the same e_mail address for use conditions. Some of the figures presented in this course are freely inspired by others reported in referenced works/sources. For such figures copyright and all rights therein are maintained by the original authors or by other copyright holders. It is understood that all persons copying these figures will adhere to the terms and constraints invoked by each copyright