Search

Contains fulltext : 76132.pdf (Publisher’s version ) (Closed access) The Open Group werkt al jaren aan standaarden. Eerst waren dat standaarden op het gebied van protocollen en operating systems. Sinds het einde van de jaren negentig richt men zich ook op standaarden voor het werk van architecten.

Onbekend.Economies around the globe have evolved into being largely service-oriented economies. Consumers no longer just want a printer or a car, they rather ask for a printing service or a mobility service. In addition, service-oriented organizations increasingly exploit new devices, technologies and infrastructures. Agility is the ability to deal with such changing requirements and environments. Agile ways of working embrace change as a positive force and harness it to the organizations competitive advantage. The approach described in this book focuses on the notion of a service as a piece of functionality that offers value to its customers. Instead of solely looking at agility in the context of system or software development, agility is approached in a broader context. The authors illustrate three kinds of agility that can be found in an agile enterprise: business, process and system agility. These three types of agility reinforce each other and establish the foundation for the agile enterprise. Architecture, patterns, models, and all of the best practices in system development contribute to agile service development and building agile applications. This book addresses two audiences. On the one hand, it aims at agile and architecture practitioners who are looking for more agile ways of working in designing and building business services or who are interested in extending and improving their agile methods by using models and model-based architectures. On the other hand, it addresses students of (enterprise) architecture and software development or service science courses, both in computer science and in business administration.

A coherent description of architectures provides insight, enables communication among different stakeholders and guides complicated (business and ICT) change processes. Unfortunately, so far no architecture description language exists that fully enables integrated enterprise modeling. In this paper we focus on the requirements and design of such a language. This language defines generic, organization-independent concepts that can be specialized or composed to obtain more specific concepts to be used within a particular organisation. It is not our intention to re-invent the wheel for each architectural domain: wherever possible we conform to existing languages or standards such as UML. We complement them with missing concepts, focusing on concepts to model the relationships among architectural domains. The concepts should also make it possible to define links between models in other languages. The relationship between architecture descriptions at the business layer and at the application layer (business-IT alignment) plays a central role.

The process of connecting enterprise systems and applications to digital platforms and ecosystems requires interoperability on different levels and eventually leads to the task of creating a schema mapping. At present, this task is carried out manually and prior research has proven this task difficult to automate. In this paper, we discuss the suitability of machine learning approaches to create an auto-mapping functionality, so different schemas and standards can (partially) be mapped automatically, and incorporate a symbiotic approach to improve the matching result. To the best of our knowledge, this is a new approach with potential to reduce the time needed for schema matching tasks. The main contribution of this paper is a reference architecture and prototype for smarter interoperability using a combination of automatic schema matching, based on machine learning, and intelligence amplification.