Primitive component architecture description language
B. Magableh, und S. Barrett. 2010 The 7th International Conference on Informatics and Systems (INFOS), Seite 1--7. IEEE, (März 2010)
Zusammenfassung
This document gives formatting instructions for authors preparing papers for publication in the Proceedings of an IEEE conference. The authors must follow the instructions given in the document for the papers to be published. You can use this document as both an instruction set and as a template into which you can type your own text. In this paper, we introduce an architecture description language (ADL) for PCOMs (a context oriented component model). The language is described at three levels: (1) Building blocks (PCOMs context oriented components types) (2) Connectors, which connect components externally and internally, and (3) Architectural Configuration, which includes a full description of composition and decomposition mechanisms. The contribution is designing ADL. That supports context-orinted component by providing new architecture elements, which fulfil the requirements of designing context oriented component based applications. Context oriented component is a behavioural unit composed of static parts and dynamic parts. A PCOMs component model design was introduced in our previous work. PCOMs proposes a component model design to compose context-aware system by capturing context condition at runtime. The model is a component-based one that modifies the application architecture by subdividing components into subsystems of static and dynamic elements. We map each context condition to a composable template architectural configuration. Each context condition acts to select behavioural patterns, which combine to form application architectures. Different types of architecture elements are proposed in this work. We focus in defining the following new elements: Components' dynamic and static parts, components' layers, decision policies, and composition plan. Finally we introduce an ADL that fully supports context aware applications, by supporting the definition of a component as a unit of behaviour. Our ADL clearly defines the composition mechanisms, and provides pro per definition for the composition's design Patterns and composition plan. The composition plan is recursively describes the composite components, and the connection between them by describing several design Patterns. A design Pattern typically, shows the relationships and the interactions between components' dynamic behaviour parts.
2010 The 7th International Conference on Informatics and Systems (INFOS)
Jahr
2010
Monat
mar
Seiten
1--7
Verlag
IEEE
isbn
978-1-4244-5828-8
review
SUMMARY (Fritz) Not a great paper. Define an ADL for a context oriented component model which has a static part and a dynamic/adaptive part which changes on environmental changes (e.g. bandwidth availability, demand, ...). They propose what I see to be more a technical soluion to a partially adaptive architecture than a true ADL (no patterns, strategies, NFR traceability, ...). Also, architecture definition is largely at functional level. They also provide a compact overview of other ADLs. More detail: ------------------ Define architecture description language for PCOMs which they call a context oriented component model. PCOMs are components with static behaviour, dynamic behaviour, ports and may be annotated with abstract context conditions(???). - Ports are points of interaction btw component & environment - Static behaviour - does not change with changes of environment (static part of architecture) - Dynamic behaviour - the adaptive part of architecture which can change with environmental changes (e.g. bandwiddth availability) They also provide a compact overview of the
%0 Conference Paper
%1 magableh_primitive_2010
%A Magableh, B.
%A Barrett, S.
%B 2010 The 7th International Conference on Informatics and Systems (INFOS)
%D 2010
%I IEEE
%K Application Architecture Component Computer Connectors; Context Object Statistics; application architectural architecture architecture; architectures; aware; awareness; behavioural component composition computing configuration; context context-aware decomposition description design design; framework; language; languages; mechanisms; model modeling; oriented pattern; patterns; primitive programming programming; science; software; system; template ubiquitous {ADL}; {PCOM}
%P 1--7
%T Primitive component architecture description language
%X This document gives formatting instructions for authors preparing papers for publication in the Proceedings of an IEEE conference. The authors must follow the instructions given in the document for the papers to be published. You can use this document as both an instruction set and as a template into which you can type your own text. In this paper, we introduce an architecture description language (ADL) for PCOMs (a context oriented component model). The language is described at three levels: (1) Building blocks (PCOMs context oriented components types) (2) Connectors, which connect components externally and internally, and (3) Architectural Configuration, which includes a full description of composition and decomposition mechanisms. The contribution is designing ADL. That supports context-orinted component by providing new architecture elements, which fulfil the requirements of designing context oriented component based applications. Context oriented component is a behavioural unit composed of static parts and dynamic parts. A PCOMs component model design was introduced in our previous work. PCOMs proposes a component model design to compose context-aware system by capturing context condition at runtime. The model is a component-based one that modifies the application architecture by subdividing components into subsystems of static and dynamic elements. We map each context condition to a composable template architectural configuration. Each context condition acts to select behavioural patterns, which combine to form application architectures. Different types of architecture elements are proposed in this work. We focus in defining the following new elements: Components' dynamic and static parts, components' layers, decision policies, and composition plan. Finally we introduce an ADL that fully supports context aware applications, by supporting the definition of a component as a unit of behaviour. Our ADL clearly defines the composition mechanisms, and provides pro per definition for the composition's design Patterns and composition plan. The composition plan is recursively describes the composite components, and the connection between them by describing several design Patterns. A design Pattern typically, shows the relationships and the interactions between components' dynamic behaviour parts.
%@ 978-1-4244-5828-8
@inproceedings{magableh_primitive_2010,
abstract = {This document gives formatting instructions for authors preparing papers for publication in the Proceedings of an {IEEE} conference. The authors must follow the instructions given in the document for the papers to be published. You can use this document as both an instruction set and as a template into which you can type your own text. In this paper, we introduce an architecture description language {(ADL)} for {PCOMs} (a context oriented component model). The language is described at three levels: (1) Building blocks {(PCOMs} context oriented components types) (2) Connectors, which connect components externally and internally, and (3) Architectural Configuration, which includes a full description of composition and decomposition mechanisms. The contribution is designing {ADL.} That supports context-orinted component by providing new architecture elements, which fulfil the requirements of designing context oriented component based applications. Context oriented component is a behavioural unit composed of static parts and dynamic parts. A {PCOMs} component model design was introduced in our previous work. {PCOMs} proposes a component model design to compose context-aware system by capturing context condition at runtime. The model is a component-based one that modifies the application architecture by subdividing components into subsystems of static and dynamic elements. We map each context condition to a composable template architectural configuration. Each context condition acts to select behavioural patterns, which combine to form application architectures. Different types of architecture elements are proposed in this work. We focus in defining the following new elements: Components' dynamic and static parts, components' layers, decision policies, and composition plan. Finally we introduce an {ADL} that fully supports context aware applications, by supporting the definition of a component as a unit of behaviour. Our {ADL} clearly defines the composition mechanisms, and provides pro per definition for the composition's design Patterns and composition plan. The composition plan is recursively describes the composite components, and the connection between them by describing several design Patterns. A design Pattern typically, shows the relationships and the interactions between components' dynamic behaviour parts.},
added-at = {2013-02-28T11:13:35.000+0100},
author = {Magableh, B. and Barrett, S.},
biburl = {https://www.bibsonomy.org/bibtex/2084dd040d5fa80b69be381cd54d4c193/fritzsolms},
booktitle = {{2010 The 7th International Conference on Informatics and Systems {(INFOS)}}},
interhash = {436b9124a040511b73086c4a43a53f02},
intrahash = {084dd040d5fa80b69be381cd54d4c193},
isbn = {978-1-4244-5828-8},
keywords = {Application Architecture Component Computer Connectors; Context Object Statistics; application architectural architecture architecture; architectures; aware; awareness; behavioural component composition computing configuration; context context-aware decomposition description design design; framework; language; languages; mechanisms; model modeling; oriented pattern; patterns; primitive programming programming; science; software; system; template ubiquitous {ADL}; {PCOM}},
lccn = {0002},
month = mar,
pages = {1--7},
publisher = {{IEEE}},
review = {{SUMMARY} {(Fritz)} Not a great paper. Define an {ADL} for a context oriented component model which has a static part and a dynamic/adaptive part which changes on environmental changes (e.g. bandwidth availability, demand, ...). They propose what I see to be more a technical soluion to a partially adaptive architecture than a true {ADL} (no patterns, strategies, {NFR} traceability, ...). Also, architecture definition is largely at functional level. They also provide a compact overview of other {ADLs.} More detail: ------------------ Define architecture description language for {PCOMs} which they call a context oriented component model. {PCOMs} are components with static behaviour, dynamic behaviour, ports and may be annotated with abstract context conditions(???). - Ports are points of interaction btw component \& environment - Static behaviour - does not change with changes of environment (static part of architecture) - Dynamic behaviour - the adaptive part of architecture which can change with environmental changes (e.g. bandwiddth availability) They also provide a compact overview of the},
timestamp = {2013-02-28T11:13:56.000+0100},
title = {{Primitive component architecture description language}},
year = 2010
}