Architecturing and Configuring Distributed Application with Olan

Abstract. Service oriented architectures provide a simple yet flexible model of a computing system as a graph of services making requests and providing results to each other. In this paper we define a formal model of a service oriented architecture and using it, we define metrics for performance, for availability, and for various security properties. These metrics serve as the basis for expressing the business requirements. To make trade-offs possible we also define a set of cost metrics, denominated in a uniform currency, to measure the cost of not meeting a requirement. The model, the property metrics, and the cost metrics are then used to generate a Constraint Satisfaction Problem where the objective function is set to minimize the aggregate system cost. We have written these constraints and defined realistic requirements in OPL and we have used them to generate system configurations that minimize the overall cost by optimally trading off the business requirements.Computing systems are designed to meet the security, performance availability, and economic requirements of the procurer. Sometimes not all of these requirements are simultaneously attainable to the maximum degree. In order to get as close as possible to meeting the requirements, trade-offs must sometimes be made between the individual requirements. In order to make these trade-offs in a sensible way and to find a system configuration that best meets our overall goals, we need a model of a system which can be evaluated quickly to determine how well the system is meeting its requirements and a uniform cost model that we can use to manage the trade-offs on the different requirements.In this paper we use formal techniques to define a precise model of a service oriented architecture, a flexible yet simple computing model that underlies the Web Service standards so popular in data processing and integration applications. We argue that this model is close enough to the reality of such systems to be interesting. We then formally define various properties of the model that correspond to important properties in real systems. The properties that we define and optimize for are different aspects of data security, server throughput, service availability and network bandwidth. We do not claim that these are the

show abstract

“…In this work the model is more based on dynamic load rather than the static load model used in this work. Examples include [11,12].…”

Section: Related Workmentioning

confidence: 99%

Trading Off Security in a Service Oriented Architecture

Swart

Aziz

Foley

et al. 2005

Data and Applications Security XIX

View full text Add to dashboard Cite

show abstract

“…The software architecture research community has also addressed configuration and deployment issues for component-based applications ([4], [35], [36], [37], [38]). A software architecture represents high-level abstractions for structure, behavior, and key properties of a software system.…”

Section: Architecture-driven Deploymentmentioning

confidence: 99%

“…For this purpose, Architecture Description Languages or ADLs have been developed to describe software systems in terms of their architectural elements. Prism-DE [4] and Olan [35] are examples of deployment techniques that employ the concepts of software architecture during the process of software deployment. In these techniques, ADLs are used to specify valid deployment configurations.…”

Section: Architecture-driven Deploymentmentioning

confidence: 99%

Deploying Component–Based Applications: Tools and Techniques

Heydarnoori

Software Engineering Research, Management and Applications

View full text Add to dashboard Cite

Summary. Software deployment comprises activities for placing an already developed application into its operational environment and making it ready for use. For complex componentbased applications that constitute many heterogeneous components with various hardware and software requirements, this deployment process can become one of the most burning challenges. In this situation, it is difficult to manually identify a valid deployment configuration that satisfies all constraints. Thus, automated tools and techniques are required to do the complex process of software deployment. To address this requirement, a variety of tools and techniques that support different activities of the deployment process have been introduced in both industry and academia. This paper aims to provide an overview of these tools and techniques.

show abstract

“…To describe (inter)relations between components in a distributed system, we can use Architecture Definition Languages (ADLs). Among many ADLs, Olan [2] is a model that encapsules legacy software in components, abstracts the middleware communication into connectors, and allows to specify the geographical placement of components.…”

Section: Dynamic Architecturesmentioning

confidence: 99%

“…Our updatable, distributed system is inspired by MARMOL [6] and Olan [2]. Olan encapsules legacy software and communication in classes.…”

Section: The Updatable Distributed Systemmentioning

confidence: 99%