From service-oriented architecture to service-oriented enterprise

Service-Oriented Architecture (SOA) was originally motivated by enterprise demands for better business-technology alignment and higher flexibility and reuse. SOA evolved from an initial set of ideas and principles to Web services (WS) standards now widely accepted by industry. The next phase of SOA development is concerned with a scalable, reliable and secure infrastructure based on these standards, and guidelines, methods and techniques for developing and maintaining service delivery in dynamic enterprise settings. In this paper we discuss the principles and main elements of SOA. We then present an overview of WS standards. And finally we come back to the original motivation for SOA, and how these can be realized

Business models and information systems for sustainable development

Businesses are expected to explore market opportunities in the area of sustainable development, thus contributing to finding solutions aiming at sustainable quality of life. This will require adaptation and innovation of business models and information systems, with challenges of particular interest to the business modeling and software design community. This paper briefly discusses two relevant topics in this respect, namely (i) goal and value modeling, and (ii) model-driven development. We mention existing work that can be taken as a starting point for addressing sustainability issues, and we make some observations that may be taken into account when extending existing work

A critical analysis of the X.400 model of message handling systems

The CCITT X.400 model of store and forward Message Handling Systems (MHS) serves as a common basis for the definition of electronic mail services and protocols both within CCITT and ISO. This paper presents an analysis of this model and its related recommendations from two perspectives. First the concepts of service, protocol and interface are discussed together with their application to this model; second the positioning within ISO's reference model for Open Systems Interconnection (OSI) is commented on

Service-oriented coordination platform for technology-enhanced learning

It is currently difficult to coordinate learning processes, not only because multiple stakeholders are involved (such as students, teachers, administrative staff, technical staff), but also because these processes are driven by sophisticated rules (such as rules on how to provide learning material, rules on how to assess students’ progress, rules on how to share educational responsibilities). This is one of the reasons for the slow progress in technology-enhanced learning. Consequently, there is a clear demand for technological facilitation of the coordination of learning processes. In this work, we suggest some solution directions that are based on SOA (Service-Oriented Architecture). In particular, we propose a coordination service pattern consistent with SOA and based on requirements that follow from an analysis of both learning processes and potentially useful support technologies. We present the service pattern considering both functional and non-functional issues, and we address policy enforcement as well. Finally, we complement our proposed architecture-level solution directions with an example. The example illustrates our ideas and is also used to identify: (i) a short list of educational IT services; (ii) related non-functional concerns; they will be considered in future work

Model-driven design of context-aware applications

In many cases, in order to be effective, software applications need to allow sensitivity to context changes. This implies however additional complexity associated with the need for applications’ adaptability (being capable of capturing context, interpreting it and reacting on it). Hence, we envision 3 ‘musts’ that, in combination, are especially relevant to the design of context-aware applications. Firstly, at the business modeling level, it is considered crucial that the different possible context states can be properly captured and modeled, states that correspond to certain desirable behaviors. Secondly, it must be known what are the dependencies between the two, namely between states and behaviors. And finally, what is valid for application design in general, business needs are to be aligned to application solutions. In this work, we address the mentioned challenges, by approaching the notion of context and extending from this perspective a previously proposed business-software alignment approach. We illustrate our achieved results by means of a small example. It is expected that this research contribution will be useful as an additional result concerning the alignment between business modeling and software design

On interoperability and conformance assessment in service composition

The process of composing a service from other services typically involves multiple models. These models may represent the service from distinct perspectives, e.g., to model the different roles of systems involved in the service, and at distinct abstraction levels, e.g., to model the service’s capability, interface or the orchestration that implements the service. The consistency among these models needs to be maintained in order to guarantee the correctness of the composition process. Two types of consistency relations are distinguished: interoperability, which concerns the ability of different roles to interoperate, and conformance, which concerns the correct implementation of an abstract model by a more concrete model. This paper discusses the need for and use of techniques to assess interoperability and conformance in a service composition process. The paper shows how these consistency relations can be described and analysed using concepts from the COSMO framework. Examples are presented to illustrate how interoperability and conformance can be assessed

EDOC: meeting the challenges of enterprise computing

An increasing demand for interoperable applications exists, sparking the real-time exchange of data across borders, applications, and IT platforms. To perform these tasks, enterprise computing now encompasses a new class of groundbreaking technologies such as Web services and service-oriented architecture (SOA); business process integration and management; and middleware support, like that for utility, grid, peer-to-peer, and autonomic computing. Enterprise computing also influences the processes for business modeling, consulting, and service delivery; it affects the design, development, and deployment of software architecture, as well as the monitoring and management of such architecture. As enterprises demand increasing levels of networked information and services to carry out business processes, IT professionals need conferences like EDOC to discuss emerging technologies and issues in enterprise computing. For these reasons, what started out as the Enterprise Distributed Object Computing (EDOC) conference has come to encompass much more than just distributed objects. So this event now used the name International EDOC Enterprise Computing Conference, to recognize this broader scope yet also retain the initial conference's name recognition

Exploiting rules and processes for increasing flexibility in service composition

Recent trends in the use of service oriented architecture for designing, developing, managing, and using distributed applications have resulted in an increasing number of independently developed and physically distributed services. These services can be discovered, selected and composed to develop new applications and to meet emerging user requirements. Service composition is generally defined on the basis of business processes in which the underlying composition logic is guided by specifying control and data flows through Web service interfaces. User demands as well as the services themselves may change over time, which leads to replacing or adjusting the composition logic of previously defined processes. Coping with change is still one of the fundamental problems in current process based composition approaches. In this paper, we exploit declarative and imperative design styles to achieve better flexibility in service composition

Flexible home care automation adapting to the personal and evolving needs and situations of the patient

Health monitoring and healthcare provisioning at home (i.e., outside the hospital) have received increasingly attention as a possible and partial solution for addressing the problems of an aging population. There are still many technological issues that need to be solved before home healthcare systems can be really cost-effective and efficient. However, in this paper we will highlight another category of issues which we call architectural challenges. Each patient is unique, and each patient has a unique lifestyle, living environment and course of life. Therefore it should be possible to personalize the services provided by home healthcare systems according to the needs and preferences of each individual patient, and it should be possible to make incremental adaptations at later points in time if this is necessary due to, for example, a changing health condition. The architectural challenges and solution directions related to this has been discussed in this paper

The role of the RM-ODP computational viewpoint concepts in the MDA approach

An MDA design approach should be able to accommodate designs at different levels of platform-independence. We have proposed a design approach previously (in [2]), which allows these levels to be identified. An important feature of this approach is the notion of abstract platform. An abstract platform is determined by the platform characteristics that are relevant for applications at a certain level of platform-independence, and must be established by considering various design goals. In this paper, we define a framework that makes it possible to use RM-ODP concepts in our MDA design approach. This framework allows a recursive application of the computational viewpoint at different levels of platform-independence. This is obtained by equating the RM-ODP notion of infrastructure to our notion of abstract platform