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 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
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
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
Many quality aspects of software systems are addressed in the existing literature on software architecture patterns. But the aspect of system administration seems to be a bit overlooked, even though it is an important aspect too. In this work we present three software architecture patterns that, when applied by software architects, support the work of system administrators: PROVIDE AN ADMINISTRATION API, SINGLE FILE LOCATION, and CENTRALIZED SYSTEM LOGGING. PROVIDE AN ADMINISTRATION API should solve problems encountered when trying to automate administration tasks. The SINGLE FILE LOCATION pattern should help system administrators to find the files of an application in one (hierarchical) place. CENTRALIZED SYSTEM LOGGING is useful to prevent coming up with several logging formats and locations. Abstract provided by the authors. Published in PLoP '13: Proceedings of the 20th Conference on Pattern Languages of Programs ACM.
DOCUMENT
Urban areas provide a promising context for upcycling due to the concentration of consumers and existence of bulky waste resources. Hence, upcycling initiatives emerge across European cities, but little is known about their manifestations. Building on interviews with twenty-four stakeholders from the urban upcycling ecosystem and three focus groups sessions, a morphological model was created with internal and external business model characteristics to analyse a database of 172 collected Dutch urban upcycling initiatives in the furniture and interior sector. The morphological analysis led to eleven urban upcycling manifestations with distinct business model characteristics that make up five generic categories and a landscape of urban upcycling which facilitate future research into the topic. A research agenda to study quantitative implications, regional differences, collaborative experimentation and scaling strategies of urban upcycling is proposed. Practically, the typology may facilitate policy makers and practitioners to create, scale or accelerate urban upcycling initiatives.
MULTIFILE
There has probably never been such an intense debate about the layout of the countryside as the one that is currently raging. There are serious concerns about the landscape, which is being rapidly transformed by urbanization and everything associated with this process, and not only in the Netherlands but also far beyond its borders. Everyone has something to say in this society-wide debate, from local to national governments, from environmental factions to the road-user's lobby, and from those who are professionally involved to concerned private parties. In many cases it is a battle between idealized images and economic models, between agricultural reality and urban park landscapes, between ecological concerns and mobility. This issue of OASE explores the potential significance of architectonic design for transformation processes on the regional scale. Besides considering the instruments that are available to the designer to fulfil this task, the authors also consider how the design can exercise a 'positive' influence on such processes. The various contributions shed light on the potential significance of territory in contemporary design practice and offer critical reflection on the topical discourse that has evolved over recent years.
DOCUMENT
Early landscape designers were very aware of the fact that time is a key feature of landscape and of landscape architecture. Today, practising landscape architects will confirm the importance of time in landscape. However, both in the drawings and in the actual proposals of today's practitioners, aspects of time are often secondary - an ambiguous situation that is the focus of this essay. Given that landscape is so strongly time-based, we can ask what aspects of time are present in today's landscape architectural designs? We can also ask whether drawings reflect time and if not, why not?
DOCUMENT
