1 / 68

Topcased

Overview of TOPCASED Project : Why, What, Who and How ? Open Source Strategy : why, organisation, licensing, tools, and quality Requirement and Design in Models Validate/Verify Requirements and Design Go through the life cycle : transformation techniques Inter-operability and Management activit

kerri
Download Presentation

Topcased

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    2. Overview of TOPCASED Project : Why, What, Who and How ? Open Source Strategy : why, organisation, licensing, tools, and quality Requirement and Design in Models Validate/Verify Requirements and Design Go through the life cycle : transformation techniques Inter-operability and Management activities : configuration, change and Requirement, tools communication Deployment and Architecture Where we are, Expected soon

    3. To reduce development costs for embedded systems (Aeronautical, space and automative domains) by promote optimised process and tools : maturity, competitivity and time to market end product. Supports Model Based Engineering. To insure durability of the toolkit through an Open source approach : limited market, very, very long life, editors durability, editors strategy, deployment facilities. To integrate current academic research results in industrial development process. To enforce Academics / Industries relationship To provide student engineers with knowledge of industrial process and related tools To enforce SMEs / Industries relationship

    4. For System Development : but what kind of system ? First targets are : specification and architecture at equipment, software and hardware level Detailed system specification for software intensive systems Establish seamless process and tools from system design to final product

    15. Collaboration with other projects

    16. Overview of TOPCASED Project : Why, What, Who and How ? Open Source Strategy : Why, organisation, licensing, tools, and quality Requirement and Design in Models Validate/Verify Requirements and Design Go through the life cycle : transformation techniques Inter-operability and Management activities : configuration, change and Requirement, tools communication Deployment and Architecture Where we are, Expected soon

    18. test tool AUTAN => ATTOL testware, specification and automated code generation SAO => SCADE,…. When there is a potential market, they go to a software editor If the market is too narrow, the commercial distribution fails : CAVEAT (formal proof tool developed by CEA) Then they go from one tool vendor to another one, depending on the market hazard ATTOL : MARBEN => RATIONAL => IBM SCADE : VERILOG => CS => Telelogic => Esterel Sometimes they simply disappear Object Geode (SDL development platform) => No mastering, no continuity, no long term availability

    24. Open Source Licenses

    25. Open Source organizations Stand-alone projects (Linux kernel, OpenOffice.org, ...) Multi-projects organizations : Free Software Foundation Apache Objectweb Eclipse Foundation Due to the distributed and multi-partners nature of these organizations, clear roles & decision process are required.

    26. Collaboration Tools Topcased uses (and contributes to) Gforge decomposed in several sub-projects This server is hosted by ENSEEIHT

    27. Collaboration Tools

    28. Development process Based on the Eclipse way Designed for distributed development teams Short integration cycles (1 week) Short development release cycles (2 months) Stable release in July each year Integrate often and early Get user reports early

    29. Quality Assurance and Control Constraints Qualification (when applicable) Long Term Maintenance Intellectual Property Context Multiple components : Make integration easier External components : insure quality level Distributed development :Quality process consistency Contributions : well defined integration process

    30. Overview of TOPCASED Project : Why, What, Who and How ? Open Source Strategy : why, organisation, licensing, tools, and quality Requirement and Design in Models Validate/Verify Requirements and Design Go through the life cycle : transformation techniques Inter-operability and Management activities : configuration, change and Requirement, tools communication Deployment and Architecture Where we are, Expected soon

    31. Requirement and Design in Models

    40. Overview of TOPCASED Project : Why, What, Who and How ? Open Source Strategy : why, organisation, licensing, tools, and quality Requirement and Design in Models Validate/Verify Requirements and Design Go through the life cycle : transformation techniques Inter-operability and Management activities : configuration, change and Requirement, tools communication Deployment and Architecture Where we are, Expected soon

    45. Already done State of the art of techniques and tools : PTOLEMY ... First draft of Needs To be done Choose technical solution : simulation through asynchronous pivot language or through generated code, based on existing solution or new one, define API between engine and animation, semantic definition using Kermeta ... Implement a Demonstrator around UML state machine, sequence and activity charts.

    46. Overview of TOPCASED Project : Why, What, Who and How ? Open Source Strategy : why, organisation, licensing, tools, and quality Requirement and Design in Models Validate/Verify Requirements and Design Go through the life cycle : transformation techniques Inter-operability and Management activities : configuration, change and Requirement, tools communication Deployment and Architecture Where we are, Expected soon

    47. Needs Model-to-Text Transformations For generating: code, xml, html, doc. Should be limited to syntactic level transcoding Model-to-Model Transformations Refining models : from specification (PIM) to design (PSM) Reverse engineering (code to models) Generating new views : generate dynamic view from a static ones, from model to verification and vice versa Applying design patterns Refactoring models : merge two branches of model Import model from tools to an other, from language through an other … any model engineering activity that can be automated…

    49. Classification of Model Transformation Techniques 1. General purpose programming languages – Ada, Python, Java ... 2. Generic transformation tools – Graph transformations, XSLT… 3. CASE tools scripting languages – Objecteering, Rose… 4. Dedicated model transformation tools – OMG QVT style, ATL, Prolog 5.Meta-modeling tools – Kermeta…

    50. Already done State of the art of techniques First draft of Needs : from process, verification ... First experimentation : using ATL, Kermeta First implementation to import Rose and Sildex model to TOPCASED/UML and TOPCASED/SAM To be done Continue state of the art and needs Continue techniques experimentation Methods aspects : Transformation guide Verification process of the transformation Develop transformation : model to code, model to test, model to document, model to model. Enhance import models : Rose, Stood, Rhapsody ...

    51. Overview of TOPCASED Project : Why, What, Who and How ? Open Source Strategy : why, organisation, licensing, tools, and quality Requirement and Design in Models Validate/Verify Requirements and Design Go through the life cycle : transformation techniques Inter-operability and Management activities : configuration, change and Requirement, tools communication Deployment and Architecture Where we are, Expected soon

    52. Inter-operability and Management activities

    61. Overview of TOPCASED Project : Why, What, Who and How ? Open Source Strategy : why, organisation, licensing, tools, and quality Requirement and Design in Models Validate/Verify Requirements and Design Go through the life cycle : transformation techniques Inter-operability and Management activities : configuration, change and Requirement, tools communication Deployment and Architecture Where we are, Expected soon

    64. Overview of TOPCASED Project : Why, What, Who and How ? Open Source Strategy : why, organisation, licensing, tools, and quality Requirement and Design in Models Validate/Verify Requirements and Design Go through the life cycle : transformation techniques Inter-operability and Management activities : configuration, change and Requirement, tools communication Deployment and Architecture Where we are, Expected soon

More Related