Application Design Model Research Articles

A Model-Based Method to Design an Application Common Platform for Enterprise Information Systems

This paper presents a model-based method to design a software platform, called an application common platform for developments of enterprise information systems. This application common platform(ACP) wraps existing reusable software assets to hide their details from application developers and provide domain level application programming interfaces, so that reusability of software assets and productivity of application improve. In this paper, we present a software architecture which organizes applications, ACP, and software assets and illustrate a development process of ACP. Especially, we show design rules to derive ACP design models from application design models and software assets design models. We also define metrics of reusability and productivity and evaluate the proposed method through real developments of enterprise information systems. As a result, the proposed method reduced 20% of development cost compared to estimation cost.

An architecture for rapid, on-demand service composition

Legacy application design models, which are still widely used for developing context-aware applications, incur important limitations. Firstly, embedding contextual dependencies in the form of if–then rules specifying how applications should react to context changes is impractical to accommodate the large variety of possibly even unanticipated context types and their values. Additionally, application development is complicated and challenging, as programmers have to manually determine and encode the associations of all possible combinations of context parameters with application behaviour. In this paper we propose a framework for building context aware applications on-demand, as dynamically composed sequences of calls to services. We present the design and implementation of our system, which employs goal-oriented inferencing for assembling composite services, dynamically monitors their execution, and adapts applications to deal with contex- tual changes. We describe the failure recovery mechanisms we have implemented, allowing the deployment of the system in a non-perfect environment, and avoiding the delays inherent in re-discovering a suitable service instance. By means of experimental evaluation in a realistic infotainment application, we demonstrate the potential of the proposed solution an effective, efficient, and scalable approach.

WREN---an environment for component-based development

Prior research in software environments focused on three important problems---tool integration, artifact management, and process guidance. The context for that research, and hence the orientation of the resulting environments, was a traditional model of development in which an application is developed completely from scratch by a single organization. A notable characteristic of component-based development is its emphasis on integrating independently developed components produced by multiple organizations. Thus, while component-based development can benefit from the capabilities of previous generations of environments, its special nature induces requirements for new capabilities not found in previous environments. This paper is concerned with the design of component-based development environments , or CBDEs. We identify seven important requirements for CBDEs and discuss their rationale, and we describe a prototype environment called WREN that we are building to implement these requirements and to further evaluate and study the role of environment technology in component-based development. Important capabilities of the environment include the ability to locate potential components of interest from component distribution sites, to evaluate the identified components for suitability to an application, to incorporate selected components into application design models, and to physically integrate selected components into the application.