Architecture description language
Warning: Under construction
To describe a Java EE 6
architecture, Jolorun uses an
architecture description language. It is a
domain specific language suited for describing Java EE 6 architectures (and not any kind of architecture, it is Java EE 6 specific). WIth this
mini language you can define the skeleton of your architecture and ask Jolorun to generate the code. The goal is to be able to describe and understand a system at a high level of abstraction.
This is what a simple example could look like :
Warning: Just ideas for the moment
Ideas
The following things are usually defined :
- Nature of the component
- Component properties
- Semantics of connections
- Behavior of a system as a whole
A system consists of a set of
actors (‘active entities’). Of these actors, three aspects may be considered:
- they have structure (describing, e.g., the decomposition of actors in subactors and how actors are related);
- they show behaviour (e.g., they perform processes, interact with each other, and offer services to their environment)
- they are likely to use and exchange information (in other words, they communicate)
Layers in the sense that the lower layers provide functionality to support the higher layers. The layers that are usually recognised in this context are the business layer, the application layer and the technology layer.
Number of other important
aspects, some of which may cross several (or all) conceptual domains, e.g.:
• Goals
• Security
• Governance
• Costs, value
• Performance
The
relationships are classified as :
- structuring relationships, which model the structural coherence of
concepts of the same or different types
- dynamic relationships, which are used to model (temporal) dependencies between behavioural concepts
- other relationships, which do not fall in one of the two above categories.
References
Comments: 0