A Semantic Agile Approach for Reconfigurable Distributed Applications in Pervasive Environments

Nowadays, future mobile applications must have the ability to use distributed smart connected objects on various smart cities domains. Most existing mobile applications have mostly neglected to consider the user's current needs and their preferences that continuously quickly evolve. The authors have developed a novel framework to generate dynamically distributed application as service chains of components and optimize connected objects life cycle. The framework combines a generic context-aware ontology situation model, middleware and IoT for managing user's composite situations at the design and the run-time levels. The first level consists of modeling applications, profiles and usage contexts through a model-driven methodology considering the specified user's constraints. The second level consists of context monitoring mechanisms, situation reasoning and deploying adapted services using Kai-smart platform for meeting user's needs and its current contexts. The proposed framework is validated through several use cases in different smart domains.

Download Full-text

MODEL DRIVEN DEVELOPMENT OF CONTEXT-AWARE MOBILE APPLICATIONS - An Architecture and a Metamodel

Proceedings of the 4th International Conference on Software and Data Technologies ◽

10.5220/0002254200430052 ◽

2009 ◽

Keyword(s):

Mobile Applications ◽

Context Aware ◽

Model Driven Development ◽

Model Driven

Download Full-text

A Middleware Architecture for Developing Mobile Applications

Software Design and Development ◽

10.4018/978-1-4666-4301-7.ch015 ◽

2014 ◽

pp. 270-284

Author(s):

Hana Rubinsztejn ◽

José Viterbo ◽

Vagner Sacramento ◽

Ricardo Rocha ◽

Gustavo Baptista ◽

...

Keyword(s):

Software Engineering ◽

Mobile Devices ◽

Mobile Applications ◽

Distributed Applications ◽

Context Aware ◽

Design And Implementation ◽

Service Oriented

In this chapter, the authors present MoCA, a service-oriented middleware architecture that supports the development and deployment of distributed applications for mobile devices, which are inherently context-aware and adaptive. Besides explaining its main services and APIs, they discuss in which ways the MoCA architecture supports some well-known software engineering principles that apply to the design and implementation of context- aware applications. Furthermore, the authors give an overview of its usage and present prototype applications that have been developed on the top of MoCA.

Download Full-text

Use of Business Models within Model Driven Architecture

Scientific Journal of Riga Technical University Computer Sciences ◽

10.2478/v10143-009-0010-1 ◽

2009 ◽

Vol 38 (38) ◽

pp. 119-130

Author(s):

Erika Asnina

Keyword(s):

Business Models ◽

Business Processes ◽

Use Cases ◽

Separation Of Concerns ◽

Model Driven Architecture ◽

Model Driven ◽

Development Processes ◽

Business Requirements ◽

Complex Computer ◽

Independent Model

Use of Business Models within Model Driven Architecture Model Driven Architecture is a framework dedicated for development of large and complex computer systems. It states and implements the principle of architectural separation of concerns. This means that a system can be modeled from three different but related to each other viewpoints. The viewpoint discussed in this paper is a Computation Independent one. MDA specification states that a model that shows a system from this viewpoint is a business model. Taking into account transformations foreseen by MDA, it should be useful for automation of software development processes. This paper discusses an essence of the Computation Independent Model (CIM) and the place of business models in the computation independent modeling. This paper considers four types of business models, namely, SBVR, BPMN, use cases and Topological Functioning Model (TFM). Business persons use SBVR to define business vocabularies and business rules of the existing and planned domains, BPMN to define business processes of both existing and planned domains, and use cases to define business requirements to the planned domain. The TFM is used to define functionality of both existing and planned domains. This paper discusses their capabilities to be used as complete CIMs with formally defined conformity between planned and existing domains.

Download Full-text