The term architecture denotes in this paper an abstract object that defines a set of requirements for a class of products, and that can be used to derive from it various more concrete objects, called (product) implementations. We assume that an architecture is expressed in a formal description language. The paper argues that in practice any architecture of more than elementary complexity, and thus its formal description, needs to be structured in order to keep it comprehensible and to efficiently express its functionality. This structuring may introduce implementation-oriented elements in the architecture, despite the fact that in principle the architecture should be implementation independent: i.e., it should be just a definition of the abstract object's external functionality.
|Number of pages||1|
|Publication status||Published - 1989|
|Event||Third International Joint Conference on Theory and Practice of Software Development, TAPSOFT 1989, Volume 2 - Barcelona, Spain|
Duration: 13 Mar 1989 → 17 Mar 1989
|Conference||Third International Joint Conference on Theory and Practice of Software Development, TAPSOFT 1989, Volume 2|
|Period||13/03/89 → 17/03/89|
|Other||13-17 Mar 1989|