Model-Based Data Processing with Transient Model Extensions

2009 16th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems

Schmid

2009

Self Cite

To foster the reuse of software artifacts various approaches like Component Based Software Engineering or Model-Driven Software Development have been proposed. These approaches support a developer in generating and implementing platform specific software artifacts, which can be executed on the chosen runtime architecture. To facilitate portability of these artifacts to other runtime architectures it is important to model various aspects of the artifact (i.e. user interface, behavior, data) in a platform independent way. While this abstraction helps to reduce complexity of the problem, choosing the right granularity of methods provided by this artifact is another important issue for enhancing software quality.Considering these aspects a model-based development approach is presented, which is based on the interpretation of several model views -like state machine and class diagrams being provided by a model-based software component. Additionally the integration of components build with this approach in the design of an information system is discussed. The proposed architecture is evaluated by an implementation in the software application domain of logistics.

Section: Runtime Metamodelmentioning

confidence: 99%

“…Also the concept of Transient Model Extensions (TME) has been introduced in [18], allowing the temporary extension of the metamodel used as the basis for the EC. This extension can be combined with platform specific code snippets, which are called as handlers or observer callbacks if a TME defined element is manipulated in the EC.…”

Section: Entity Containermentioning

confidence: 99%

Interpreting Model-Based Components for Information Systems

2009 16th Annual IEEE International Conference and Workshop on the Engineering of Computer Based Systems

Schmid

2009

Self Cite

“…Elements defined in the data model are treated as entities being accessible by a dynamic or static interface and having their own identity and lifecycle. The EC has been used as basis for several concepts like Transient Model Extension (TME) [8]. The EC approach has also been extended to become a Model Based Component Container (MCC) supporting state machines model views etc.…”

Section: Related Workmentioning

confidence: 99%

“…Such an extended meta model enables a full validation of loaded M1 models with embedded ECQL statements also. Extension of the meta model is done with a Transient Model Extension (TME) [8], allowing the insertion of new model elements and the connection of existing model elements based on the rules provided in the next upper layer (in this case the M3 layer). A second extension in the M2 layer is performed during the instantiation of a MCC, allowing the support of assigned resources to a VON (e.g.…”

Section: Statement Signaturesmentioning

confidence: 99%

ECQL: A Query and Action Language for Model-Based Applications

Krenn

2010 17th IEEE International Conference and Workshops on Engineering of Computer Based Systems

2010

Self Cite

Modern distributed computer systems with mobile and embedded devices as first class citizens are formed from heterogeneous platforms. To support this heterogeneity along with adaptation of the system an approach for interpretation of domain specific models at runtime has been proposed with the concept of Model-Based Software Components (MBSC), separating the domain specific functionality from the current technical platform. This is achieved by the usage of different sets of high-level models. These sets are interpreted by a portable, plugin-extensible runtime environment, utilizing several instances of model-based containers (MCC) for models and their corresponding data.In this paper the design of a domain specific language is presented, enabling the specification of accessing and manipulating data entities provided by various MCCs used in the runtime architecture of a MBSC. For demonstration purposes the application of the various language elements is presented using a case study of an exemplary distributed pervasive system running in the business domain of logistics.

“…Some requirements on layer specific data structures are not known in the design phase of a layer, because they follow from implementational considerations. In order to support these requirements by a data model a dynamical model extension mechanism has been proposed in [9]. This mechanism is called Transient Model Extension (TME) to point out, that extensions made to the model are available only in the scope (e.g.…”

Section: Introductionmentioning

confidence: 99%

Implementing Model-Based Data Structures using Transient Model Extensions

Schmoelzer²,

2007

JSW

Self Cite

Software is often constructed using a layered approach to encapsulate various functionality in corresponding layers. Individual requirements of each layer demand layer specific data structures. These data structures typically provide redundant information with respect to the data source. Providing a Model Driven Software Development approach for creating these data structures leads to overlapping data models, each containing data structures defined by the data source. Because putting all various requirements of the software layers in a single data model can lead to difficulties, each software layer should only extend the basic data source model with its specifically needed model elements. The approach presented in this paper applies a mechanism for a dynamic extension of a data model. This extension mechanism is used in the implementational activity of a software process, and allows the changing of a model within a local scope. Using this mechanism, a basic data model can be used by every layer, being extended by additional attributes and classes for satisfying layer specific requirements.