Towards a Model-Driven Engineering Software Development Framework

Slides:



Advertisements
Similar presentations
MDI 2010, Oslo, Norway Behavioural Interoperability to Support Model-Driven Systems Integration Alek Radjenovic, Richard Paige The University of York,
Advertisements

2009 – E. Félix Security DSL Toward model-based security engineering: developing a security analysis DSML Véronique Normand, Edith Félix, Thales Research.
Guaranteed Component Assembly with Round Trip Analysis for Energy Efficient High-integrity Multi-core Systems Artemis-AAL day 7 May, Budapest 1BME and.
Kellan Hilscher. Definition Different perspectives on the components, behavioral specifications, and interactions that make up a software system Importance.
WebRatio BPM: a Tool for Design and Deployment of Business Processes on the Web Stefano Butti, Marco Brambilla, Piero Fraternali Web Models Srl, Italy.
Presented by: Thabet Kacem Spring Outline Contributions Introduction Proposed Approach Related Work Reconception of ADLs XTEAM Tool Chain Discussion.
Rational Unified Process
Copyright © 2006 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
Model Driven Architecture (MDA) Partha Kuchana. Agenda What is MDA Modeling Approaches MDA in a NutShell MDA Models SDLC MDA Models (an Example) MDA -
WebRatio BPM: a Tool for Design and Deployment of Business Processes on the Web Stefano Butti, Marco Brambilla, Piero Fraternali Web Models Srl, Italy.
Copyright © 2007 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Applying MDA in the ATM: A practical approach Teodora Bozheva, Terry Bailey (ESI) Julia Reznik, Tom Ritter (Fraunhofer FOKUS)
Chapter 6– Artifacts of the process
Software Development Process
Standards John D. McGregor. But first… SECIE-Safety-in-Software-and-Human- Intensive-Systems-Leveson-brief.pdf.
UML - Development Process 1 Software Development Process Using UML (2)
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
CSCE 548 Secure Software Development Test 1 Review.
Software Models (Cont.) 9/22/2015ICS 413 – Software Engineering1 -Component-based software engineering -Formal Development Model.
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
John D. McGregor Session 2 Preparing for Requirements V & V
1 Workshop on Business-Driven Enterprise Application Design & Implementation Cristal City, Washington D.C., USA, July 21, 2008 How to Describe Workflow.
1 Introduction to Software Engineering Lecture 1.
Component & Deployment Diagram © copyright 2001 SNU OOPSLA Lab.
Refining middleware functions for verification purpose Jérôme Hugues Laurent Pautet Fabrice Kordon
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
1 An Aspect-Oriented Implementation Method Sérgio Soares CIn – UFPE Orientador: Paulo Borba.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Toulouse, September 2003 Page 1 JOURNEE ALTARICA Airbus ESACS  ISAAC.
Software Engineering Chapter: Computer Aided Software Engineering 1 Chapter : Computer Aided Software Engineering.
International Telecommunication Union © ITU-T Study Group 17 Integrated Application of SDL Amardeo Sarma NEC Europe Ltd.
Industrial Avionics Working Group 18/04/07 The Relationship Between the Design and Safety Domains in IAWG Modular Certification Part 2: Completeness of.
Formal Methods in Software Engineering1 Today’s Agenda  Mailing list  Syllabus  Introduction.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
SEESCOASEESCOA SEESCOA Meeting Activities of LUC 9 May 2003.
Software Systems Division (TEC-SW) ASSERT process & toolchain Maxime Perrotin, ESA.
CHESS Methodology and Tool Federico Ciccozzi MBEES Meeting Sälen, January 2011 January 2011.
The Software Lifecycle Stuart Faulk. Definition Software Life Cycle: evolution of a software development effort from concept to retirement Life Cycle.
Security analysis of COM with Alloy
Lecture 3 Prescriptive Process Models
SysML v2 Usability Working Session
Chapter 8 – Software Testing
IEEE Std 1074: Standard for Software Lifecycle
CSE 403 Software Engineering
Ron Williamson, PhD Systems Engineer, Raytheon 20 June 2011
Designing Software for Ease of Extension and Contraction
Model-Driven Analysis Frameworks for Embedded Systems
The Extensible Tool-chain for Evaluation of Architectural Models
Reverse Engineering: A Roadmap
Systems Engineering Tool for Intelligent Transportation
Introduction to Software Testing
QGen and TQL-1 Qualification
QGen and TQL Qualification
Software Development Process
Standards.
ABHISHEK SHARMA ARVIND SRINIVASA BABU HEMANT PRASAD 08-OCT-2018
Software engineering -1
Helping a friend out Guidelines for better software
Jochen Seemann Program Manager Enterprise Tools Microsoft Corporation
Chapter 7 –Implementation Issues
Automated Analysis and Code Generation for Domain-Specific Models
System Reengineering Restructuring or rewriting part or all of a system without changing its functionality Applicable when some (but not all) subsystems.
System to Software Integrity
Subject Name: SOFTWARE ENGINEERING Subject Code:10IS51
Executable Specifications
UML Design for an Automated Registration System
Software Architecture & Design
Presentation transcript:

Towards a Model-Driven Engineering Software Development Framework Julien Delange Maxime Perrotin Samir Bennani Julien Delange Maxime Perrotin Samir Bennani 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012

Consequences of Software Development issues Increasing cost Development + certification Late release and impact on other projects Re-engineering efforts due to testing efforts Remaining bugs leading to potential failures 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012

Software Development Traps & Pitfalls – tech concerns Heterogeneous notations Models using different representation Collocation of languages with potential incompatibilities Lack of formalization Assumptions made by development teams Heterogeneous execution environment Impact on system execution and software behavior 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012

Software Development Traps & Pitfalls – org. concerns Lack of coordination among teams Different understanding of system requirements Assumptions based on team experience Human-factor Introduction of bugs Heterogeneous background 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012

Software Development Traps & Pitfalls – org. concerns Lack of coordination among teams Different understanding of system requirements Assumptions based on team experience Human-factor Introduction of bugs Heterogeneous background 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012

Proposed Approach Formalize system specifications using models System functions, interfaces & execution environment Avoid unspecified aspects Automate development aspects Focus on specialized engineering domain Avoid integration efforts 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012

The ASSERT Set of Tools for Engineering System description using three views Data View: interfaces, data types Interface View: system functions and connections Deployment View: functions allocation on execution system Automatic production of implementation Transform models into executable code Integration with established tools and standards 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012

TASTE Development Process Data View (ASN.1) Interface View (AADL) Functions code (C, Ada, Simulink, etc.) Deployment View (AADL) User-defined Interfaces generation Code skeletons (C, Ada, etc.) Code integration System implementation (binary) 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012 Automatically Generated

TASTE ecosystem Languages Tools ASN.1 Interfaces & data types AADL Functional specification Deployment definition Functional modeling languages ASN1Scc (Semantix) Ocarina (ISAE) TASTE GUI (Ellidiss) RTDS (Pragmadev) 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012

The VEGA case-study Implementation Interface View Functional code (Guidance and Navigation Control) Deployment View Simulink models Heterogeneous languages Deployment on systems with different architectures Implementation 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012

Existing projects & feedback Initial use in the European Space Agency Supporting projects development Abstraction ease system development Extension to other domain Use in both academic and industrial contexts Demonstrate toolset maturity 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012

Conclusion Pragmatic approach addressing current traps & pitfalls Strict & formalized system description Automate system production, avoid manual efforts Support for more validation & other domains Support for validation/certification efforts Extension for other safety-critical systems (e.g. avionics) 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012

Questions ? 12/04/2012 Towards a Model-Driven Engineering Software Development Framework - AVICPS2012