SEICMU Program
Overview
Software Engineering Institute at Carnegie Mellon University in Pittsburgh, Pennsylvania .
Customer's Product: Evaluation
Hardware: [ QEMU simulation environment only]
Expected cert: TBD
SOW: TBD.
Baseline: FourPeaks
Technical Contact: Julien Delange
Management Contact: Janis McKinney
Deos Management Contact: Bill Cronk
Deos Technical Contact: Gary Gilliland
Charge Code: 2140-000-746 - Deos Pre-sales and Marketing
Current Release Based on Chino release
- \\nx3000\ship\dds\windows\approved\DDS-seicmu-deos-fourpeaks-20141115
Milestones
| Program | Milestones | Type | Stable Date | Ship Date | Cur. Date | Status |
|---|---|---|---|---|---|---|
| SEICMU | Deos Phone Training | Training | 2014-11-26 | 2014-11-26 | 2014-11-26 | DONE |
| SEICMU | SEICMU Eval Release | Release | 2014-11-14 | 2014-11-14 | 2014-11-14 | DONE |
| SEICMU | Deos SEICMU Evaluation | Evaluation | 2014-11-14 | 2014-11-14 | 2015-05-31 | In Progress |
Evaluation Results
- The goal of the evaluation was to integrate Deos code and system development with CMU's AADL tools.
- Julien was able to get this working and provide a demo at the Joint RTES/SAE AADL Forum in San Diego in February.
- Julien set up a webpage for this work here: http://www.aadl.info/aadl/arinc653-mils-demo/
- His next demonstration is in June to a DoD group to demonstrate integrating SCADE auto generating tools with Deos and migrating to VxWorks and back to Deos using modeling tools.
- He will demo to us as well.
Projects
Code Name
SEICMU The Software Engineering Institute at Carnegie Mellow University.
The Original Oyster House The oldest bar and resturant in Pittsburg PA. If we need a code name at some late date. Maybe OOH.
Install and Training November 26
Recap
- Customer installed product himself. No training provided.
Key concerns for Evaluation
- 1) Development integration: exercise the integration of DeOS in a model-based code generation framework for
producing ARINC653 applications from architecture models designed with the Architecture Analysis and Design Language (MDI)
- 2) Usability: exercise the integration of the tool in an Eclipse-based framework and provide appropriate user feedback
when executing the system
- 3) Core feature of the developer suite: evaluation of the editor, builder, use of different development platforms
(including Windows).
- 4) Runtime features of the tool suite arid RTOS to evaluate application performance and/or certification
- 5) Evaluating the specific scheduling approaches of the RTOS.
