Proposals

A main directive of YASTE is its continuous extension. Most ideas are discussed in the mailinglists first, but at some point a more consistent way of specification is required. For the YASTE project this should be done via written proposals. This article explains in more details what this means and how it should be handled.

General Guidelines

First of all some general information about proposals; Please write them, as everything else on this page in English! Further write all proposals in APT and add them to the /engsb-docs/src/site/apt/proposals folder. The structure itself could be chosen by the type of the document.

Domain Description

This section describes what should be contained in the proposal for an interface description. The structure of the documents themselves should be done in the following form:

  1. Which tools exist for the domain
  2. The purpose of these Tools i.e. common sense interactions between these tools. Preferably illustrated via behavioural UML diagramms (Activity, Sequence, Objectflow, ...).
  3. What YASTE plugins are required? TODO: osgi
  4. Define which events could be thrown by the domain. Define java classes and describe in detail when this event should be thrown.