OPENPROD ITEA2 Final Review Meeting 18.12.2012 EDF - Site de Chatou EADS Innovation Works Wladimir Schamai.

Slides:



Advertisements
Similar presentations
International Telecommunication Union © ITU-T Study Group 17 Integrated Application of URN Daniel Amyot University of Ottawa, Canada
Advertisements

Testing Workflow Purpose
Component-Based Software Engineering Main issues: assemble systems out of (reusable) components compatibility of components.
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
LIFE CYCLE MODELS FORMAL TRANSFORMATION
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
UML Diagrams Jung Woo. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems, business.
Alternate Software Development Methodologies
Presented by: Thabet Kacem Spring Outline Contributions Introduction Proposed Approach Related Work Reconception of ADLs XTEAM Tool Chain Discussion.
CH02: Modeling the process and life cycle Process of developing software (organization and discipline in the activities) contribute to the quality of the.
Formal Methods in Software Engineering Credit Hours: 3+0 By: Qaisar Javaid Assistant Professor Formal Methods in Software Engineering1.
Filling the Gap Between System Design & Performance Verification Rafik HENIA, Laurent RIOUX, Nicolas SORDON Thales Research & Technology.
Model-Based Programming: Executable UML with Sequence Diagrams By Ruben Campos Cal State L.A. Computer Science Thesis Work Spring 2007.
1 UML – an overview What is UML? UML stands for Unified Modelling Language. ”The Unified Modelling Language is a visual language for specifying, constructing.
Π-Method: A Model-Driven Formal Method for Architecture- Centric Software Engineering By Flavio Oquendo Presented by: Sajith Wickramaratne.
CS 290C: Formal Models for Web Software Lecture 6: Model Driven Development for Web Software with WebML Instructor: Tevfik Bultan.
1 Scenario-based Analysis of UML Design Class Models Lijun Yu October 4th, 2010 Oslo, Norway.
By Ryan Mowry.  Graphical models of system  Entire system or just parts  Complex systems easier to understand  “Capture key requirements and demonstrate.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Chapter 6– Artifacts of the process
February Semantion Privately owned, founded in 2000 First commercial implementation of OASIS ebXML Registry and Repository.
CLEANROOM SOFTWARE ENGINEERING.
By Manuel C. Salas Advisor: Dr. Bernard P. Zeigler University of Arizona 2008.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
What is a life cycle model? Framework under which a software product is going to be developed. – Defines the phases that the product under development.
Testing Workflow In the Unified Process and Agile/Scrum processes.
WSMX Execution Semantics Executable Software Specification Eyal Oren DERI
1 Recent work in the area: Requirement-Driven Development of Distributed Applications Gregor v. Bochmann School of Information Technology and Engineering.
Lecture 3 Uses Cases Topics UML Use Cases pop quiz Readings: Chapter 3 January 24, 2008 CSCE 492 Software Engineering.
1 Introduction to Software Engineering Lecture 1.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
Performance evaluation of component-based software systems Seminar of Component Engineering course Rofideh hadighi 7 Jan 2010.
Fall 2010 CS4310 Requirements Engineering A Brief Review of UML & OO Dr. Guoqiang Hu Department of Computer Science UTEP 1.
OPENPROD ITEA2 Final Review Meeting EDF - Site de Chatou University of Applied Science Bernhard Bachmann.
Model Checking and Model-Based Design Bruce H. Krogh Carnegie Mellon University.
Verification of behavioural elements of UML models using B Truong, Ninh-Thuan and Souquieres, Jeanine In Proceedings of the 2005 ACM Symposium on.
Automata Based Method for Domain Specific Languages Definition Ulyana Tikhonova PhD student at St. Petersburg State Politechnical University, supervised.
3.2 Semantics. 2 Semantics Attribute Grammars The Meanings of Programs: Semantics Sebesta Chapter 3.
Architecture Analysis Techniques
Requirements Engineering-Based Conceptual Modelling From: Requirements Engineering E. Insfran, O. Pastor and R. Wieringa Presented by Chin-Yi Tsai.
Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher(2009) with material from Amyot User Requirements Notation (URN)
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Author Software Engineering Institute
Course: COMS-E6125 Professor: Gail E. Kaiser Student: Shanghao Li (sl2967)
Prof. Hany H. Ammar, CSEE, WVU, and
Modeling Test Cases to Multi-Agent Systems Andrew Diniz da Costa
Formal Verification. Background Information Formal verification methods based on theorem proving techniques and model­checking –To prove the absence of.
Rigorous Testing by Merging Structural and Behavioral UML Representations Presented by Chin-Yi Tsai.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Software Engineering I. Introduction to Software Engineering Software models Formal Specification using ASML (Abstract State Machines Language) Software.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
SEESCOASEESCOA SEESCOA Meeting Activities of LUC 9 May 2003.
Lectures 2 & 3: Software Process Models Neelam Gupta.
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
Course: Software Engineering – Design I IntroductionSlide Number 1 What is a specification Description of a (computer) system, which:  is precise;  defines.
Doc.: IEEE /223r0 Submission July 2000 Taylor Salman, Opnet TechnologiesSlide 1 Project: IEEE P Working Group for Wireless Personal Area.
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
SysML-Modelica Transformation Specification (SE DSIG Meeting, Jacksonville, 3/22/2010) Chris Paredis Georgia Tech On behalf of the SysML-Modelica Working.
SysML Modelica Integration Working Group Report (SE DSIG Meeting, San Antonio, TX, 9/15/2009) Chris Paredis Georgia Tech 1.
CHESS Methodology and Tool Federico Ciccozzi MBEES Meeting Sälen, January 2011 January 2011.
Rhapsody 2003년 3월 12일 배대호.
Multi-Device UI Development for Task-Continuous Cross-Channel Web Applications Enes Yigitbas, Thomas Kern, Patrick Urban, Stefan Sauer
UML Diagrams By Daniel Damaris Novarianto S..
Evolution of UML.
Object-Oriented Analysis and Design
UML Diagrams Jung Woo.
Software Design Methodology
Component-Based Software Engineering
UML profiles.
On behalf of the SysML-Modelica Working Group
Presentation transcript:

OPENPROD ITEA2 Final Review Meeting EDF - Site de Chatou EADS Innovation Works Wladimir Schamai

OPENPROD ITEA2 Final Review Meeting OPENPROD WP2 Results ModelicaML (Integration of UML and Modelica) –Supports model-based development of whole products, both software parts (UML) and hardware parts (Modelica). –UML to Modelica code generation, Modelica code import and synchronization Method for Model-Based Design Verification –vVDR (virtual Verification of Designs against Requirements) implemented in the ModelicaML prototype –Shows what is necessary to enable design verification using models –Shows how to formalize requirements, design alternative and verification scenarios –Enables the automation of model composition, simulation and results evaluation

OPENPROD ITEA2 Final Review Meeting ModelicaML ModelicaML integrates a subset of the UML and the Modelica language in order to leverage standardized graphical notations of UML for system modeling and the simulation power of Modelica In ModelicaML engineers can describe System requirements System design (structure and behavior) Usage-, test scenarios vVDR (virtual Verification of Designs against Requirements) is a method that enables a model-based design verification against requirements vVDR is supported in ModelicaML

OPENPROD ITEA2 Final Review Meeting vVDR – Method for Model-Based Deign Verification Formalize Requirements Formalize Designs Formalize Scenarios Create Verification Models Execute and Create Report Analyze Results RMM Requirement Monitor Models Scenario Models SM Design Alternative Models DAM VM Verification Models AUTOMATED TaskCreated Artifact Goal: Enable on-demand verification of designs against requirements using automated model composition at any time during development. AUTOMATED Actor Reports

OPENPROD ITEA2 Final Review Meeting Automated Model Composition We want to verify different design alternatives against sets of requirements using different scenarios 1) How to find valid combinations of design alternatives, scenarios and requirements in order to enable an automated composition of verification models? 2) Having found a valid combination: How to bind all components correctly? … Create Verification Models … RMM 1. Verification Model VM DAM SM 2. Verification Model VM … … Requirement ModelsScenario ModelsDesigns Alternative Models DAM SM DAM SM RMM 1 SM RMM …… n. Verification Model

OPENPROD ITEA2 Final Review Meeting Verification Results Analysis HTML verification summary report Plots

OPENPROD ITEA2 Final Review Meeting Conclusion The integration of UML and Modelica (ModelicaML) –Enables the creation of executable system models in UML/SysML by using Modelica as action language –This work has identified and reported issues in the UML/SysML OMG specifications and contributed to the OMG SysML/Modelica transformation standard –ModelicaML State Machines implementation contributed to the Modelica state machines to be standardized by the Modelica Association vVDR (virtual Verification of Designs against Requirements) –Enables an automated model-based verification of designs against requirements –Is integrated in the ModelicaML prototype