Tekst oratie in verkorte vorm uitgesproken bij de openbare aanvaarding van het ambt van bijzonder hoogleraar E-business, vanwege Hogeschool Utrecht, aan de Open Universiteit. In dit stuk worden de verbanden tussen businessmodellen , procesmodellen en Informatiearchitectuur behandeld.
MULTIFILE
From the article: Though organizations are increasingly aware that the huge amounts of digital data that are being generated, both inside and outside the organization, offer many opportunities for service innovation, realizing the promise of big data is often not straightforward. Organizations are faced with many challenges, such as regulatory requirements, data collection issues, data analysis issues, and even ideation. In practice, many approaches can be used to develop new datadriven services. In this paper we present a first step in defining a process for assembling data-driven service development methods and techniques that are tuned to the context in which the service is developed. Our approach is based on the situational method engineering approach, tuning it to the context of datadriven service development. Published in: Reinhartz-Berger I., Zdravkovic J., Gulden J., Schmidt R. (eds) Enterprise, Business-Process and Information Systems Modeling. BPMDS 2019, EMMSAD 2019. Lecture Notes in Business Information Processing, vol 352. Springer. The final authenticated version of this paper is available online at https://doi.org/10.1007/978-3-030-20618-5_11.
MULTIFILE
Author Supplied: In the last decades, architecture has emerged as a discipline in the domain of Information Technology (IT). A well-accepted definition of architecture is from ISO/IEC 42010: "The fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution." Currently, many levels and types of architecture in the domain of IT have been defined. We have scoped our work to two types of architecture: enterprise architecture and software architecture. IT architecture work is demanding and challenging and includes, inter alia, identifying architectural significant requirements (functional and non-functional), designing and selecting solutions for these requirements, and ensuring that the solutions are implemented according to the architectural design. To reflect on the quality of architecture work, we have taken ISO/IEC 8402 as a starting point. It defines quality as "the totality of characteristics of an entity that bear on its ability to satisfy stated requirements". We consider architecture work to be of high quality, when it is effective; when it answers stated requirements. Although IT Architecture has been introduced in many organizations, the elaboration does not always proceed without problems. In the domain of enterprise architecture, most practices are still in the early stages of maturity with, for example, low scores on the focus areas ‘Development of architecture’ and ‘Monitoring’ (of the implementation activities). In the domain of software architecture, problems of the same kind are observed. For instance, architecture designs are frequently poor and incomplete, while architecture compliance checking is performed in practice on a limited scale only. With our work, we intend to contribute to the advancement of architecture in the domain of IT and the effectiveness of architecture work by means of the development and improvement of supporting instruments and tools. In line with this intention, the main research question of this thesis is: How can the effectiveness of IT architecture work be evaluated and improved?
DOCUMENT
Abstract To add value to the organization, an Enterprise Architecture Management (EAM) function should be able to realize its goals in line with the corporate strategy. In this paper *, we propose the Enterprise Architecture Realization Scorecard (EARS) and an accompanying method to discover the strengths and weaknesses in the realization process of an EAM function. During an assessment, representative EA goals are selected, and for each goal, the results, delivered during the different stages of the realization process, are identified, examined and scored. The outcome of an assessment is a numerical EARScorecard, supplemented with a description of the strengths and weaknesses of the EA realization process, and recommendations. To evaluate and improve the assessment instrument, the EARScorecard was used in various organizations. An assessment case is discussed in depth to illustrate the use of the instrument.
DOCUMENT
With the development of Enterprise Architecture (EA) as a discipline, measuring and understanding its value for business and IT has become relevant. In this paper a framework for categorizing the benefits of EA, the Enterprise Architecture Value Framework (EAVF), is presented and based on this framework, a measurability maturity scale is introduced. In the EAVF the value aspects of EA are expressed using the four perspectives of the Balanced Scorecard with regard to the development of these aspects over time, defining sixteen key areas in which EA may provide value. In its current form the framework can support architects and researchers in describing and categorizing the benefits of EA. As part of our ongoing research on the value of EA, two pilots using the framework have been carried out at large financial institutions. These pilots illustrate how to use the EAVF as a tool in measuring the benefits of EA
DOCUMENT
Live programming is a style of development characterized by incremental change and immediate feedback. Instead of long edit-compile cycles, developers modify a running program by changing its source code, receiving immediate feedback as it instantly adapts in response. In this paper, we propose an approach to bridge the gap between running programs and textual domain-specific languages (DSLs). The first step of our approach consists of applying a novel model differencing algorithm, tmdiff, to the textual DSL code. By leveraging ordinary text differencing and origin tracking, tmdiff produces deltas defined in terms of the metamodel of a language. In the second step of our approach, the model deltas are applied at run time to update a running system, without having to restart it. Since the model deltas are derived from the static source code of the program, they are unaware of any run-time state maintained during model execution. We therefore propose a generic, dynamic patch architecture, rmpatch, which can be customized to cater for domain-specific state migration. We illustrate rmpatch in a case study of a live programming environment for a simple DSL implemented in Rascal for simultaneously defining and executing state machines.
DOCUMENT
Author supplied: "Abstract—Software architecture compliance checking (SACC) is an approach to monitor the consistency between the intended and the implemented architecture. In case of static SACC, the focus is mainly on the detection of dependencies that violate architectural relation rules. Interpretation of reported violations may be cumbersome, since the violations need to be connected to architectural resolutions and targeted qualities such as maintainability and portability. This paper describes an SACC case study which shows that inclusion of different types of rules in the SACC process enhances reasoning on architecture violations, especially if a rule type is related to specific architectural pattern. The SACC is performed with HUSACCT, an SACC-tool that provides rich sets of module and rule types in support of patterns such as layers, facade, and gateway. The case system is a governmental system developed in C#, which follows the .NET common application architecture. Even though the system appeared to be well-structured, the SACC revealed that 10 of the 17 architectural rules were violated."
DOCUMENT
Presentatie voor de 20e Nederlandse Testdag, m.m.v. Raymond Slot, Wiebe Wiersema, (HU), Christian Köppe (HAN, Arnhem), Sjaak Brinkkemper, Jan Martijn van der Werf (UU Utrecht). The Software Architecture of the Schiphol Group is taken as an example. Compliance checking of software rulescan be done with the Hogeschool Utrecht Software Architecture Compliance Checking Tool which is available at http://husacct.github.io/HUSACCT/
DOCUMENT
Het Meta-Model of Interprofessional Development wordt beschreven. Deze bestaat uit diverse factoren die prioriteit zouden moeten krijgen om verschillende beroepsgroepen complementair te laten samenwerken om zo tot optimale en gezamenlijke uitkomsten te kunnen komen. Deze factoren vormen tezamen een systemische samenhang omdat zij een wisselwerking op elkaar hebben. Diverse wetenschappelijk toetsbare assumpties worden beschreven voor elk van deze factoren (fasen) in relatie tot interprofessionele ontwikkeling en in relatie tot hun onderlinge samenhang.
DOCUMENT
Decisions and business rules are essential Components of an organization. Combined, these components form a basis for securing the implementation of new laws, regulations and internal policies into processes, work instructions and information systems. To ensure proper implementation, business rule types must be taken into account, as the functions per type may be different. The current body of knowledge on decision and business rule management offers some insights into different types of business rules, however, these types are often presented as a secondary focus of a contribution or set in stone without proper evidence supporting these claims. This study therefore aims to explore the different business rule types utilized in the body of knowledge as well as practice. This will form a basis to determine possible overlap and inconsistencies and aid in establishing the functional differences between the defined business rule types. By applying a literature review, semi-structured interviews and secondary data analysis, we observed that the current body of knowledge shows serious diffusion with regards to business rule types, the same holds for practice. Therefore, future research should focus to research these differences in detail with the aim to harmonize the proliferation of business rule types.
DOCUMENT
