Open AADL

Blog

2017

Updates ! August 12, 2017.

After several months of silence, several posts recap the latest development around AADL and Ocarina, see below for the list:

Along with various rewrite in the other pages. More to come!

New book `AADL in Practice` June 5, 2017.

Julien Delange, one of the (past) core member of the OSATE dev team published his book on AADL: AADL in Practice

This concise book provides a full coverage of AADL. From the foreword (that I authored):

Turning a significant portion of these past experiences into a book that is pleasant to read is a challenge of its own and one that is well executed in this manuscript. It aims at providing to the engineer and student communities one concise book that introduces some core aspects of AADL. Through one case study, readers will learn how to model a system and then analyze it. More importantly, they will be able to apply AADL directly thanks to the companion project that can be downloaded separately.

With this book, readers will be well-equipped to apply model-based architectural techniques to their own projects.

The book is available directly on Amazon.

Note This book will be part of a future teaching project I’ll report shortly.

AADL Inspector 1.6 has been released April 13, 2017.

Ellidiss released AADL Inspector, now with Ocarina bundled.

See AADL Inspector product page for more details. Among the relevant features, one can cite the capability to simulate AADL models, gateway to Cheddar. Starting with the 1.6 release, AADL Inspector proposes to use Ocarina to check model legality rules.

Use CalVer versioning scheme January 1, 2017.

Ocarina now uses Calendar Versioning. This provides a more consistent tracking of versions.

As a consequence, Ocarina 2017.1 has been released. GitHub changelog highlights most recent updates.

2016

Travis continuous build December 25, 2016.

Thanks to travis, Ocarina and related projects PolyORB-HI/Ada, PolyORB-HI/C and AADLib now have automated continuous integration testing capabilities here; including code coverage information thanks to codecov.io there.

These are reported directly on Ocarina README file on GitHub