2020, Article in monograph or in proceedings (7th International Conference on Research and Practical Issues of Enterprise Information Systems, pp. 206-214)
2020, Article in monograph or in proceedings (Project: Hospital’s IT infrastructure capability and digital capabilities, pp. 233-244)In the Netherlands demands on IT support in healthcare organizations are increasing. New visions on healthcare focus on patient-centered healthcare, where mutual consultation among healthcare professionals in the network becomes a standard process. Recent governmental regulations prescribe that patients must be able to access personal health records. IT flexibility is needed to allow organizations to meet new demands. In this study, we focus on Conceptual Independence (CI) be-cause CI, as a design principle, can improve the adaptability of Information Systems (IS). Software with CI operates on flexible data models that are independent of the CI based application. Therefore, it is claimed that a standalone IS becomes more flexible with CI. We extend the claim by demonstrating that CI affects the flexibility of the entire IT infrastructure. We investigate which dimensions of IT flexibility are responsible for the improvement. Multi-case study research has been performed following a mixed-methods approach in 10 mental healthcare organizations. Five have implemented openEHR, a proxy for CI, and five have not. Data has been collected with a questionnaire of IT infrastructure flexibility and semi-structured interviews. The data synthesis shows a positive effect of CI on IT flexibility, as CI increases the adaptability of IS, transparency and standardization of the IT infrastructure.
Mean scores of openEHR organizations and other organizations on the questionnaire of IT infrastructure flexibility
Mean scores of openEHR organizations and other organizations on the questionnaire of IT infrastructure flexibility
…
Reuse and modularity P2: Reuse of functionality increases Modularity of IT infrastructure
Reuse and modularity P2: Reuse of functionality increases Modularity of IT infrastructure
…
Accessibility of data
Accessibility of data
…
Mean Scores for Organizations on IT Infrastructure Flexibility Questionnaire
Mean Scores for Organizations on IT Infrastructure Flexibility Questionnaire
…
Hypothesis Test Summary -Means
Hypothesis Test Summary -Means
…
Figures - uploaded by Rogier van de WeteringAuthor content
Content may be subject to copyright.
2018, Article in monograph or in proceedings (FEDERATED CONFERENCE ON COMPUTER SCIENCE AND INFORMATION SYSTEMS / In FedCSIS (ed.), Project: Hospital’s IT infrastructure capability and digital capabilities, pp. 87-94)This study links business requirements and adaptability of existing software systems. Organizations expect flexibility of IT with regard to business requirements. We hypothesize that the flexibility of business requirements is difficult in IT systems, because of software dependencies in the way domain knowledge is implemented. In this paper, we, therefore, explore how Business requirements have been implemented in the source code of three open source healthcare systems. Outcomes suggest that a tight interdependency of business terminology and functionality in source code hides business requirements from view and thereby hinders IT flexibility on higher levels.
Diagram of Modeling levels of OMG
Diagram of Modeling levels of OMG
…
Figures - uploaded by Rogier van de WeteringAuthor content
All figure content in this area was uploaded by Rogier van de Wetering
Content may be subject to copyright.
2018, Article in monograph or in proceedings (a Case Study, pp. 383-393)In this practice paper, we report the outcomes of a case study in a new Dutch hospital, where enterprise architects are working toward a 'lean' and 'simplified' EA model to align existing IT systems to new requirements. The objective of the case study was to examine if the developed EA model could support architects in selecting components of an existing IT infrastructure for re-use, with regard to radically new requirements. We have developed an EA model in close collaboration with enterprise architects. This study reflects on the use of this model in the hospital. The approach combines analysis of the content in the model, a study of documents in the organization, and communication with the architects. We signal that the existence of an integrated suite for an Electronic Health Record system largely determined how the model was used. Reflection disclosed that a lack of information on requirements and applications, as well as low adaptability of existing systems, negatively affected the flexibility of IT in the organization.
2018, Article in monograph or in proceedings (Buchmann, R.; Karagiannis, D.; Kirikova, M. (ed.), PoEM 2018. Lecture Notes in Business Information Processing)
2017, Article in monograph or in proceedings (In MATEC Web of Conferences 127, 01006 (2017))In this paper we explain why Axiomatic design has not been applied in large system of systems information technology architectures in health care organizations in the Netherlands. We have found in extensive case studies of IT systems that the Independence axiom could not be found in the existing Information systems. This causes great concern for the adaptability of systems. Although best practices in system engineering advice decoupling of system functionality, findings show that the Independence Axiom has not been applied to functional requirements. A number of difficulties was exposed to the researcher and IT architects, when they tried to identify and to demarcate functional requirements in existing systems. In IT systems a distinction is made between business and system functions and software engineers emphasize decoupling of system functions. That has resulted in a strong coupling of business information and technical application logic. This means Conceptual dependencies are often at the heart of the difficulties. Decoupling these dependencies in applications seems a candidate for ordering requirements in a way that keeps the functional requirements independent from each other. Conceptual independence signifies a complete decoupling of the concepts and relations of the Business domain from the technical functionality. The paper describes the difficulties when applying the Independence Axiom in the Information systems domain and argues that a combination of Conceptual independence and Axiomatic design is achievable. The authors adapt the Design matrix with Conceptual independence. We conclude that applying Conceptual independence is crucial when constructing IT systems based on Axiomatic design.
Components in Home care institute.
Components in Home care institute.
…
. Descriptions of DPs.
. Descriptions of DPs.
…
Figures - available via license: Creative Commons Attribution 4.0 International
Content may be subject to copyright.
2016, Article in monograph or in proceedings (Proceedings of the 10th Travelling Conference on Pattern Languages of Programs, pp. 1-10)Conceptual independence is a novel approach for adaptable information systems. It extends the ideas of Model Driven Development. Conceptual independence eases adaptability by a separation of the Business domain terms from the functions that use the terms in the application. Although in practice many examples can be found in which parts of this approach are applied, a consistent application of this idea is not often encountered. The principle of Conceptual independence is sketched in this paper in a pattern. Since developing information systems often depends on the content of the Business domain, and the conceptual model of the domain needs frequent adaptation, systems need to be adaptable. In this paper we describe a complete decoupling of the software system from its conceptual model of the domain. We illustrate the relevance of this approach for the professional practice of software development and architecture. Furthermore, we describe related approaches for adaptable systems.
2015, Article in monograph or in proceedings (Procedia CIRP, pp. 262-268)This paper applies and discusses the principles of Axiomatic Design for changing IT architecture in health care. It presents three case studies positioned in the field of Enterprise architecture that explore how IT architects, as professionals, manage change and re-design the structure of the IT systems in line with strategic goals. The research approach was to use a light modelling tool, Ampersand, for modelling the Enterprise architecture. Two types of models stand out: Type 1 Strategic IT models in which higher strategic goals are related to requirements for applications and Type 2 Technical management of systems models in which technical risks and risk of system failure in the current IT infrastructure were modelled. To bridge the views of different IT experts in the organization this work uses the customer domain, the functional domain and the physical domain from Axiomatic Design in an extended example in the paper. The V Model is used to bridge the models, and then it is extended with Axiomatic Design principles.
2015, Article / Letter to editor (Elsevier, vol. 34, (2015), pp. 263-268)Abstract This paper applies and discusses the principles of Axiomatic Design for changing IT architecture in health care. It presents three case studies positioned in the field of Enterprise architecture that explore how IT architects, as professionals, manage change and re-design the structure of the IT systems in line with strategic goals. The research approach was to use a light modelling tool, Ampersand, for modelling the Enterprise architecture. Two types of models stand out: Type 1 Strategic IT models in which higher strategic goals are related to requirements for applications and Type 2 Technical management of systems models in which technical risks and risk of system failure in the current IT infrastructure were modelled. To bridge the views of different IT experts in the organization this work uses the customer domain, the functional domain and the physical domain from Axiomatic Design in an extended example in the paper. The V Model is used to bridge the models, and then it is extended with Axiomatic Design principles.
Example of model of type 1 Strategic IT
Example of model of type 1 Strategic IT
…
. Context in different case studies.
. Context in different case studies.
…
V Model for overview of IT Architecture.
V Model for overview of IT Architecture.
…
Figures - uploaded by René Ronald BakkerAuthor content
Content may be subject to copyright.
2013, Article in monograph or in proceedings (Paper presented at the 7th International Conference on Research and Practical Issues of Enterprise Information Systems CONFENIS)IT architects in practice have a difficult task in extending and adapting enterprise information systems. Mastering complexity is a priority. This is still more art than craftsmanship in spite of many years of academic research in IT architecture. We will explore by a series of case studies how to support IT architects in practice, with their work of improving the consistency and completeness of emerging architectures. In this process, IT architects should be capable of discussing conflicting, incomplete, highly abstract, or overly detailed requirements with stakeholders and developers, while keeping an overview of all priorities and constraints. In this research paper, we first discuss the research strategy, Design research combined with case study research, to address this question. Next, we discuss Ampersand and its tool, a rule-based modeling language, and an engine developed in high-level IT consultancy. Ampersand seems promising for flexible modeling of IT architecture, and its rule engine can help IT architects manage consistency between requirements and IT solutions. An empirical exploration in developing the IT architecture for a new specialized child oncology hospital is used to check the premises of our research and the usefulness of Ampersand in this context. The conclusions of this exploration have led to hypotheses for testing in further research. The hypotheses concern applying the Ampersand approach to effectively support IT architects’ work.