OSATE overview & community updates

Transcription

1 OSATE overview & community updates Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Julien Delange 04/22/2013

2 Overview of OSATE2 Eclipse-based AADL editor Support for AADLv2.1, up to date with latest standard revisions Support for behavior and error annexes Support for quantitative analysis SEI-based plug-ins (latency, performance, etc.) Third-party plug-ins (code generation, scheduling analysis) OSS development model Public SCM and bugtrack, open to external contribution Licensed under EPL license 2

3 Statistics update Code base More than 1M lines of code Mostly generated Community More than 1700 commits in one year Around 10 regular contributors Software Quality Test on 200+ models More than 50 reported bugs fixed since last meeting 15 bugs still opened Commit activity in 2012/2013 3

4 OSATE development plan for 2013, update Increase community involvement Integrate new third-projects: autobuild with RAMSES Provide help and support using OSS tools: connection with PRISM Follow-up with AADL committee Implement latest language revision, up-to-date with standard Follow-up with mailing-list New release process Stable releases after each committee meeting Testing release everyday, check Keep track of quality issues: less than 15 bugs are opened 4

5 OSATE Property Edition 5

6 OSATE integrated help User documentation Plug-ins documentation Reference Standard OSATE dev reference Error-Model documentation Also available online at 6

7 Error-Model support in IMV Graphical support for fault assessment Components impacted Gross evaluation Probability values not used Error source 7

8 Error-Model, Fault Hazard Assessment (FHA) Enumerate faults on each components Identification of missing faults Improve fault/error management Support for SAE ARP4761 safety/reliability process Implementation by generating an Excel document 8

9 Error-Model, Reliability Block Diagram (RDB) Evaluation of safety using components hierarchy Use of composite error behavior Using gross estimation of components reliability To be refined using error propagation 9

10 Error-Model, Fault Tree Analysis (FTA) Dependencies of Faults and Errors Identify root cause of failures Implementation using XML files Export to tool-specific notation using scripts (CAFTA) 10

11 Error-Model, export to Markov-Chain (PRISM) Export error model into Markov-Chain Simulation and evaluation of system reliability Check error specifications (faults occurrence, etc.) Experimentation with PRISM Industry-level tool, used by NASA Validation on a representative example To be extended for full support of EMV2 11

12 Community update SEI blog posts Check out New ongoing post on tools and specific domains User-specific mailing-list sae-aadl* lists for announcements aadl-modeling for user discussions Remote AADL meetings Encourage user exchange Discuss modeling patterns and tools usage Just started, please read announcements 12

13 Getting Support View code revision Bugtrack Github Public bugreport Source code changes tracking Wiki Maintain research doc. Populate with documentation Ease community involvement Mailing-List Branch to track 13

14 Conclusion Improvement on OSATE 2 support Regular support and bug fixes Development of new internal features Error-Model related toolset Experiment and investigate user needs Connection with other annexes (e,g, behavior) AADL community needs you Open Development Model (OSS tools & license) New discussions support (mailing-list, blog, remote meetings) 14

15 Links and other useful information OSATE-related tools Wiki: Github: Ohloh: General AADL discussions Main AADL website: SEI blog: AADL mailing-lists 15

16 Contact Presenter / Point of Contact Dr. Julien Delange Telephone: jdelange@sei.cmu.edu U.S. Mail Software Engineering Institute Customer Relations 4500 Fifth Avenue Pittsburgh, PA USA Web Customer Relations info@sei.cmu.edu Telephone: SEI Phone: SEI Fax:

17 Copyright 2013 Carnegie Mellon University This material is based upon work funded and supported by the Department of Defense under Contract No. FA C-0003 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. NO WARRANTY. THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN AS-IS BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. This material has been approved for public release and unlimited distribution. This material may be reproduced in its entirety, without modification, and freely distributed in written or electronic form without requesting formal permission. Permission is required for any other use. Requests for permission should be directed to the Software Engineering Institute at permission@sei.cmu.edu. DM