OSATE Tool Developer

From AadlWiki

Jump to: navigation, search

Welcome to the root page for information about writing plug-ins, analyses, and otherwise interfacing with OSATE. Here you can find links to

  • Notes from the OSATE development about changes to the OSATE API
  • Tutorials for creating OSATE plug-ins
  • Code examples for manipulating the AADL meta model as implemented in OSATE
  • Information on how to build OSATE itself

It will also contain proposals for changes to OSATE to better support annex extensions, integration with the TOPCASED graphical editor, and automated invocation of analysis tools.

Contents

News: OSATE API Changes

Plug-in Tutorials

Tutorials on specific Plug-in topics. Generally these give a more holistic coverage to the topic than the notes in the sections below.

Meta Model Information and Examples

General Issues

Features

Connections

Modes and System Operation Modes

Properties

Building OSATE

OSATE Repository

Branching

To enable the evolution of new features, in particular for AADL version 2.0, we will follow a more formal branching scheme in the CVS repository. For each OSATE release we will create branch that contains the source code of this version. Our branching strategy mimics what many open source projects do: Before a new release we will create a branch to freeze the feature set for the release. Release testing and fixes will be done on this branch.

Development of OSATE 2.0 has been moved to GitHub with releases made available on GForge. See Osate 2 for details.

This branching strategy starts with release 1.4.6. The corresponding branch is named OSATE_1_4_6. Whoever wants to check out the sources of the latest stable OSATE version should switch to this branch and no longer use the HEAD. The Eclipse Help system describes how to work with CVS branches in

Workbench User Guide -> Tasks -> Working in the team environment with CVS -> Working with a CVS repository -> Discovering branch and version tags

and Workbench User Guide -> Tasks -> Working in the team environment with CVS -> Replacing resources in the workspace

Personal tools