| Popis: |
An important issue concerning system architectures is how to guarantee that the executable behaviour of a particular model is exactly the same as intended by the system architect. Graphical notations seem intuitive enough to be well understood almost at first sight. However, they typically lack the precise mathematical basis that is required to render them really unambiguous. On the contrary, attempts at formalisation can easily become quite complex. For this reason, we apply the notion of ASMs to formalise the \({eP^2}\) components, their interfaces and behaviour, and to specify the collaboration of the components in a rigorous way. Moreover, by using a formal notation, we avoid ambiguities in the system from the very start. Furthermore, we fulfil the main goals of a software architecture description comprising, amongst others, (i) efficient support of the system development, (ii) the presentation of different aspects of the architecture, and (iii) descriptions of components at different levels of abstraction. |
