2010
DOI: 10.1016/j.jss.2010.04.075
|View full text |Cite
|
Sign up to set email alerts
|

A comprehensive engineering framework for guaranteeing component compatibility

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2011
2011
2023
2023

Publication Types

Select...
3
2
1

Relationship

1
5

Authors

Journals

citations
Cited by 11 publications
(6 citation statements)
references
References 27 publications
0
5
0
Order By: Relevance
“…Our approach is therefore close to the process of SOMA in starting from business models and aligning services to business goals. Another methodology that have influenced our work was developed in the FP6 EU project SIMS 5 [8] which defined a top-down approach for specifying mobile services, starting from a high level specification of the system and modelling composite collaboration representing the services and refining these to fine grained specification of components, interfaces and data.…”
Section: Service Engineering Methodologiesmentioning
confidence: 99%
“…Our approach is therefore close to the process of SOMA in starting from business models and aligning services to business goals. Another methodology that have influenced our work was developed in the FP6 EU project SIMS 5 [8] which defined a top-down approach for specifying mobile services, starting from a high level specification of the system and modelling composite collaboration representing the services and refining these to fine grained specification of components, interfaces and data.…”
Section: Service Engineering Methodologiesmentioning
confidence: 99%
“…The variability and domain models are transformed into code executable by the middleware to plan the adaptation. Nevertheless, MUSIC does not support developing application components (managed elements) as in the framework, they do not play an active role in the adaptation: component development is considered an orthogonal, well‐understood issue 37,38 and as such, outside of the framework's scope. Accordingly, the framework does not allow the integral design of adaptation logic and component reconfiguration.…”
Section: Motivation and Backgroundmentioning
confidence: 99%
“…Deliberately, the MUSIC project did not spend any effort on research into software engineering techniques for the development of the application components themselves, because the application components do not play an active role in the adaptation. Component development is considered an orthogonal, well‐understood issue and simply outside of the project scope. Thus, the main research innovations and contributions of MUSIC in the development process are: (i) a comprehensive application adaptation modelling methodology that enables various forms of application variability and seamlessly integrates into the adaptation models information on context dependencies, adaptations objectives (based on utility functions) and external heterogeneous service offers; (ii) model transformation support for transforming the adaptation models, including domain knowledge contained in ontologies, into code that is used by the MUSIC middleware at runtime to perform the adaptation reasoning.…”
Section: Music Framework At a Glancementioning
confidence: 99%