Author supplied: Teaching software architecture (SA) in a bachelor computer science curriculum can be challenging, as the concepts are on a high abstraction level and not easy to grasp for students. Good techniques and tools that help with addressing the challenging SA aspects in a didactically responsible way are needed. In this tool demo we show how we used the software architecture compliance checking tool HUSACCT for addressing various concepts of SA in our courses on software architecture. The students were introduced to architectural reconstruction and architecture compliance checking, which helped them to gain important insights in aspects such as the relation between architectural models and code and the specification of dependency relations between architecture elements as concrete rules.
DOCUMENT
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
Enterprise Architecture has been developed in order to optimize the alignment between business needs and the (rapidly changing) possibilities of information technology. But do organizations indeed benefit from the application of Enterprise Architecture according to those who are in any way involved in architecture? To answer this question, a model has been developed (the Enterprise Architecture Value Framework) to organize the benefits of Enterprise Architecture. Based on this model, a survey has been conducted among the various types of stakeholders of Enterprise Architecture, such as architects, project managers, developers and business or IT managers. In the survey the respondents were asked to what extent they perceive various benefits of Enterprise Architecture in their organization. The results of this survey (with 287 fully completed responses) are analyzed and presented in this paper. In all categories of the framework benefits are perceived, though to different extent. Very few benefits are perceived in relation to the external orientation of the organization. Few statistically significant correlations were found in relation to the background of the respondents: the overall view on benefits of Enterprise Architecture appeared independent of the role of the respondents, the economic sector and the number of years of experience with architecture.
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
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
The importance of sustainability is rapidly increasing and by now has an increasing impact on the operations of organizations. In modern organizations many of the business processes are supported by IT, which makes the relation between sustainability and IT an important subject. However, how to integrate business strategy with IT operations in relation to sustainability is unclear. In this paper we focus on the role of Enterprise Architecture in this process and try to answer “How Enterprise Architecture may contribute in the traceable transformation from sustainability principles towards requirements on Green IT in the field of higher education.” Based on a literature study and qualitative research at different organizations we adapted the Sustainable Information Systems Management (SISM) model of Erek et al (2012). The SISM Revisited model not only guides organizations in identifying areas of interest for aligning the sustainability strategy of an organization with its IS/IT activities, but we expect it will be useful to implement sustainability in organizations as well.
DOCUMENT
Abstract Healthcare organizations operate within a network of governments, insurers, inspection services and other healthcare organizations to provide clients with the best possible care. The parties involved must collaborate and are accountable to each other for the care provided. This has led to a diversity of administrative processes that are supported by a multi-system landscape, resulting in administrative burdens among healthcare professionals. Management methods, such as Enterprise Architecture (EA), should help to develop and manage such landscapes, but they are systematic, while the network of healthcare parties is dynamic. The aim of this research is therefore to develop an EA framework that fits the dynamics of network organizations (such as long-term healthcare). This research proposal outlines the practical and scientific relevance of this research and the proposed method. The current status and next steps are also described.
DOCUMENT
Twirre is a new architecture for mini-UAV platforms designed for autonomous flight in both GPS-enabled and GPS-deprived applications. The architecture consists of low-cost hardware and software components. High-level control software enables autonomous operation. Exchanging or upgrading hardware components is straightforward and the architecture is an excellent starting point for building low-cost autonomous mini-UAVs for a variety of applications. Experiments with an implementation of the architecture are in development, and preliminary results demonstrate accurate indoor navigation
MULTIFILE
Business Rule Management (BRM) is a means to make decision-making within organizations explicit and manageable. BRM functions within the context of an Enterprise Architecture (EA). The aim of EA is to enable the organization to achieve its strategic goals. Ideally, BRM and EA should be well aligned. This paper explores through study of case study documentation the BRM design choices that relate to EA and hence might influence the organizations ability to achieve a digital business strategy. We translate this exploration into five propositions relating BRM design choices to EA characteristics.
DOCUMENT
This report is the final report for the FPGA accelerated PID controller, part of the Distributed Control Systems project. This project runs within the Lectoraat Robotics and High Tech Mechatronics of Fontys Hogeschool Engineering Eindhoven. The Lectoraat has the goal to develop applicable knowledge to support education and industry. This knowledge is acquired with projects run in conjunction with the industry. The report will go into detail for the software designed for this project, not the hardware design. This report is intended for follow up students working on the Distributed Control Systems project. Within this report the assumption is made that the reader is at least familiar with the terms EtherCAT, FPGA, Linux and PID controllers. However for each part a small basic introduction is included. For readers looking for the accomplishments in this project, the results are in chapter six. Following are short descriptions of the chapters in this report. The first chapter will give a short introduction to the project. It talks about why the project was conceived, where the project was done and what the expected end result is. The second chapter, the problem definition, talks about how the project has been defined, what is included and what is not and how the customer expects the final product to function and look like. The third chapter details the methodology used during this project. All the research preformed for this project will be described in the forth chapter. This chapter goes into the research into the Xilinx Zynq 7000 chip, Beckhoff's EtherCAT system, how the Serial Peripheral Interface works and how a PID controller functions. Following in chapter five the design is expanded upon. First the toolchain for building for the Zynq chip is explained. This is followed by and explanation of the different software parts that have been designed. Finally chapters six and seven provide the results and the conclusions and recommendations for this project.
DOCUMENT
