Model-Driven Development Maturity Model Tatiana Ribeiro Hipólito.

Slides:



Advertisements
Similar presentations
© Telelogic AB Modeling DoDAF Compliant Architectures Operational Systems Technical.
Advertisements

INCOSE Presentation San Francisco Chapter 13 October 2009 Mapping CMMI to Systems Engineering Adrienne Friedman.
Presentation by Prabhjot Singh
SAFe Automotive aRchItecture SAFARI. SAFARI_Presentation_Short_v1.ppt 2 / /P. Cuenot/ © Continental AG ARTEMIS/Call2 R&D Project Proposal Project.
Which role might model-based engineering play in software certification? Selo Sulistyo.
Formal Techniques in Software Engineering Universiteit AntwerpenIntroduction 1.1 Formal Techniques in Software Engineering 3de BAC Informatica Chapter.
4.1 Blended approaches: Information Engineering IMS Information Systems Development Practices.
The Experience Factory May 2004 Leonardo Vaccaro.
Soft. Eng. I, Spring 07Dr Driss Kettani, from I. Sommerville1 CSC-3324: Chapter 5 Requirements Engineering Reading: Chap. 6, 7 + annex.
Secure Middleware (?) Patrick Morrison 3/1/2006 Secure Systems Group.
Planning a measurement program What is a metrics plan? A metrics plan must describe the who, what, where, when, how, and why of metrics. It begins with.
1 Introduction to Software Engineering Lecture 42 – Communication Skills.
Chapter 10: Analyzing Systems Using Data Dictionaries Instructor: Paul K Chen.
Ontologies Reasoning Components Agents Simulations An Overview of Model-Driven Engineering and Architecture Jacques Robin.
CASE Tools CIS 376 Bruce R. Maxim UM-Dearborn. Prerequisites to Software Tool Use Collection of useful tools that help in every step of building a product.
Software Configuration Management (SCM)
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
CS 290C: Formal Models for Web Software Lecture 6: Model Driven Development for Web Software with WebML Instructor: Tevfik Bultan.
Arquitectura Tecnológica dos Sistemas de Informação Enterprise Architecture Validation Pedro da Silva - Nº João Jesus – Nº Nuno Dias – Nº
On the Correctness of Model Transformations Gabor Karsai ISIS/Vanderbilt University.
Page 1 R Risk-Driven and Iterative Development. Page 2 R Copyright © 1997 by Rational Software Corporation What the Iterative Life Cycle Is Not It is.
Software Quality Assurance (SQA) Monitor the methods and standards used during the software development and verify their correct usage. What is Quality?
Mobile Application for SAT Preparation Preliminary Project Plan By Project Team: Hi5 Anant Kambli Amit Shukla Ajaykumar Aswathappa Prabin Gautam Rama K.
Software Engineering CS B Prof. George Heineman.
Slide title In CAPITALS 50 pt Slide subtitle 32 pt Site DB creation and updates 05/08/2006 by Performance Team.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
TC Methodology Massimo Cossentino (Italian National Research Council) Radovan Cervenka (Whitestein Technologies)
Software System Engineering: A tutorial
1 Software Quality CIS 375 Bruce R. Maxim UM-Dearborn.
OASIS WSQM TC Meeting Dugki Min. 컴퓨터공학부 건국대학교 Agenda 1. Roll Call 2. Review and approval of the agenda 3. Review and approval of the previous.
RUP Design RUP Artifacts and Deliverables
Alignment of ATL and QVT © 2006 ATLAS Nantes Alignment of ATL and QVT Ivan Kurtev ATLAS group, INRIA & University of Nantes, France
EMI INFSO-RI SA2 - Quality Assurance Alberto Aimar (CERN) SA2 Leader EMI First EC Review 22 June 2011, Brussels.
Relationships July 9, Producers and Consumers SERI - Relationships Session 1.
MOTOROLA and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective.
Model-Driven Analysis Frameworks for Embedded Systems George Edwards USC Center for Systems and Software Engineering
WSMX Execution Semantics Executable Software Specification Eyal Oren DERI
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
Verification and Validation in the Context of Domain-Specific Modelling Janne Merilinna.
1 A Model-Driven Approach For Information System Migration Raymonde Le Delliou 1, Nicolas Ploquin 2, Mariano Belaunde 3, Reda Bendraou 4, Louis Féraud.
© Siemens AG, CT SE 2, Iris Groher, Markus Voelter C O R P O R A T E T E C H N O L O G Y XWeave – Models and Aspects in Concert 1 XWeave Models.
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
ANKITHA CHOWDARY GARAPATI
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Formalizing Material Flow Diagrams Robert-Jan Bijl.
PRJ566 Project Planning & Management Software Architecture.
Cluster “LIFETIME” Cluster “LIFETIME” projects: LIFECON (Coordinator VTT, Finland) EUROLIFEFORM (Coordinator Taylor Woodrow, United Kingdom) INVESTIMMO.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 15a: Product Metrics for Software Software Engineering: A Practitioner’s Approach, 6/e Chapter.
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 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
XXX, Inc. 1 Technical Capabilities  Requirements Engineering  Analysis and Design  Implementation  Quality Assurance  Project Life Cycle  Requirements.
CMMI1 Capability Maturity Model Integration Eyal Ben-Ari 8/2006.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
© 2010 IBM Corporation What’s New in RSA 8.0 Beta 1 – Visual Basic modeling March, 2010.
Instituto de Engenharia de Sistemas e Computadores Investigação e Desenvolvimento em Lisboa ProjectIT ProjectIT-Studio, an integrated environment for the.
Multi-disciplinary Approach for Industrial Phases in Space Projects Evolution of classic SE into MBSE Harald EisenmannAstrium Satellites Joachim Fuchs.
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Discussion of Course Syllabus Class will start momentarily. Please Stand By … CS 8532: Advanced.
CS 8532: Adv. Software Eng. – Spring 2009 Dr. Hisham Haddad , Monday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
CHESS Methodology and Tool Federico Ciccozzi MBEES Meeting Sälen, January 2011 January 2011.
CIS 375 Bruce R. Maxim UM-Dearborn
Seminar 1 Design of Informatics Systems
Rational Unified Process
OBJECT-ORIENTED APPROACH TO OFFICIAL STATISTICS
System Modeling Assessment & Roadmap Joint OMG/INCOSE Working Group
OO Design and Development
EA Framework TOGAF is a framework - a detailed method and a set of supporting tools - for developing an enterprise architecture.
Presentation transcript:

Model-Driven Development Maturity Model Tatiana Ribeiro Hipólito

Roteiro Projeto MODELWARE WP2 Model-Driven Development Maturity Model Outros Modelos –Kleppe and Warmer’s Modelling Maturity Levels –IBM MDD Maturity Matrix Conclusão Referência

Projeto MODELWARE WP2 Model-Driven Developmente Maturity Model – MDD MM - Versão Preliminar. MM é um meio para avaliar o nível de capacidade de uma organização com relação ao MDD. Conjunto de práticas MDD relacionadas à implantação dos processos MDD: –Engenharia –Gerência –Apoio

Modelo Conceitual WP2 MDD Maturity Model MDD TCM Guidelines helps in transition Practice MDD Element’s Aspect includes MDD Metrics MDD Engineering Metrics MDD Business Metrics measures level refers to Technology Change Management: guia para introduzir e melhorar MDD nas organizações. Em desenvolvimento e serão refinadas na versão final. Level consist of

Estrutura do MDD MM

Maturity Levels Level 1: Ad-hoc Modelling Level 2: Manual Modelling Level 3: Initial MDD Level 4: Integrated MDD Level 5: Ultimate MDD MDD Maturity Model Level Practice MDD Element’s Aspect consist of includes

Práticas Engineering (ENG) Project Management (PJM) Support (SUP) MDD Maturity Model Level Practice MDD Element’s Aspect consist of includes

Práticas Ad-hoc Modeling Manual Modeling Initial MDD Integrated MDD Ultimate MDD

Práticas Modelling practices are sporadically used or not used at all.

Práticas EngineeringProject ManagementSupport ENG 1 – Identify modelling techniques ENG 2 – Define implementation model ENG 3 – Code the implementation model PJM 1 – Decide upon modelling tools

Práticas EngineeringProject ManagementSupport ENG 4 – Define business model ENG 5 – Develop technical model ENG 6 – Define transformations from technical model to code ENG 7 – Gerenate code from the technical model ENG 8 – Separate generated from non-generated code ENG 9 – Verify models PJM 2 – Define MDD-project worflow PJM 3 – Decide upon coverage of modelling activities SUP 1 – Establish and maintain repositories for models and transformations SUP 2 – Define, collect and analyze measures with respect to the modelling activities

Práticas EngineeringProject ManagementSupport ENG 10 – Select and use standard modelling language ENG 11 – Define domain model ENG 12 – Develop business model ENG 13 - Transform business models to technical models ENG 14 – Test the models ENG 15 – Separate the technical models of the product and the platform PJM 4 – Plan iterative development of application and system family platform

Práticas EngineeringProject ManagementSupport ENG 16 – Design domain- specific modelling languages ENG 17 – Continuously improve and validate the domain metamodel ENG 18 – Simulate and execute models PJM 5 – Establish and maintain strategic software assets

Elementos MDD MDD Maturity Model Level Practice MDD Element’s Aspect consist of includes Models Documentation Model Transformation and Code Generation Mechanisms Tools

Aspectos

O que se espera de cada nível

MDD Elements and Related Apstects Implemented Model

MDD Elements and Related Apstects Code

MDD Elements and Related Apstects Model to text Transformation (Implementation model to documentation)

MDD Elements and Related Apstects Tools

MDD Elements and Related Apstects Business Model

MDD Elements and Related Apstects Technical Model

MDD Elements and Related Apstects Model to text Transformation (Technical model to documentation)

MDD Elements and Related Apstects Code generation mechanisms (Technical model to code)

MDD Elements and Related Apstects Tools: Modelling tools

MDD Elements and Related Apstects Domain Model

MDD Elements and Related Apstects Business Model

MDD Elements and Related Apstects Architecture-centric meta model

MDD Elements and Related Apstects Model to model transformation (Business to technical model)

MDD Elements and Related Apstects Tools: Modelling tools; Model repositories; Basic model Testing tools

MDD Elements and Related Apstects Domain meta model

MDD Elements and Related Apstects Domain model

MDD Elements and Related Apstects Model to model Transformation (Domain to business model)

MDD Elements and Related Apstects Tools: Model simulation And execution tools

Kleppe and Warmer’s Modelling Maturity Levels

Kleppe and Warmer’s Modelling Maturity Levels

IBM MDD Maturity Matrix

Conclusão Complemento do CMMI Versão preliminar

Referência MODELWARE – – D2.6 MDD Maturity Model – Preliminary – Revision date: 12/12/05. Maximize the Business Value of the Software – Model-Driven Architecture. Borland, 2006.

FIM !!!