Current Assumptions
===================
+ each component can play each role only once per ensemble
+ only roles can interact
+ role behaviors do not have mixed states
+ Promela: only one component type can play a role (needed when calling a component's operation)

HelenaText
==========
- goals
- process names should only have to be unique in a role behavior, but at the moment in complete specification 
- proposal for component operations
		 
- Formatting: solve indentation problem for declaring role behavior
- Relations and data values via XBase
- Refactor xtext grammar -> prevent multiple inheritance

- automatic tests
- try to force no whitespace inbetween self.attr and owner.attr and owner.assoc
- instantiation level
- translation process terms to labeled transition systems

? mixed states and priorities
? component interfaces
? internal operations of roles
? calls of internal operations of roles in role behaviors


AdaptiveHelenaText
==================
- resolve history transitions

Promela Generator
=================
- Generate data values and relations
- goals
- instantiation in init process (after we have instantiation in HelenaText)

jHelena Generator
=================
- instantiation

jHelena:
========
- Update UML architecture diagram (check visibilities of all methods)
- check that attr, assocs, ops, msgs are not declared multiple times for the same role/comp type
- extract createType/getType from all ...Type classes if possible
- check assumption: one component plays one role just once in one ensemble