Urban densification continues unabated, even as the possible consequences for users’ eye-level experiences remain unknown. This study addresses these consequences. In a laboratory setting, images of the NDSM wharf were shown to university students primed for one of three user groups: residents, visitors and passers-by. Their visual experiences were recorded using eye-tracking and analyzed in combination with surveys on self-reported appreciation and restorativeness. On-site surveys were also administered among real users. The results reveal distinct eye-movement patterns that point to the influence of environmental roles and tasks and how architectural qualities steer people’s visual experience, valence and restoration.
DOCUMENT
There is an increasing call in society for the improvement of well-being for nursing home residents and the support of care professionals through a wide array of architectural and technological solutions that are available in modern nursing homes. This study investigated which of these solutions are considered essential by stakeholders from healthcare and technology. Data were gathered via 22 simultaneously held multidisciplinary mind map sessions with 97 stakeholders, resulting in 43 mind maps. These, in turn, were grouped into a single mind map of the nursing home in general, the private rooms for residents with somatic or psychogeriatric health problems, and the group living room. A prioritization of solutions was added. The contents of the mind maps reflect a Dutch consensus on the necessary architectural and technological features for the design of nursing homes.
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
Buildings with innovative technologies and architectural solutions are needed as a means of support for future nursing homes alongside adequate care services. This study investigated how various groups of stakeholders from healthcare and technology envision the nursing home of the future in the presumed perspective of residents, care professionals and technical staff. This qualitative study gathered data via ten simultaneous monodisciplinary focus group sessions with 95 professional stakeholders. The sessions yielded eight main themes: person and well-being; relatives and interaction; care technology; safety and security; interior design, architecture and the built environment; vision and knowledge; communication; and maintenance and operation. These themes can be used for programming future nursing homes, and for prioritising design and technological solutions. The views between the groups of stakeholders are to a large extent similar, and the personal needs of the residents are the most prominent factor for practice.
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." http://ieeexplore.ieee.org/document/7484100/ http://dx.doi.org/10.1109/QRASA.2016.7
DOCUMENT
Abstract-Architecture Compliance Checking (ACC) is an approach to verify the conformance of implemented program code to high-level models of architectural design. ACC is used to prevent architectural erosion during the development and evolution of a software system. Static ACC, based on static software analysis techniques, focuses on the modular architecture and especially on rules constraining the modular elements. A semantically rich modular architecture (SRMA) is expressive and may contain modules with different semantics, like layers and subsystems, constrained by rules of different types. To check the conformance to an SRMA, ACC-tools should support the module and rule types used by the architect. This paper presents requirements regarding SRMA support and an inventory of common module and rule types, on which basis eight commercial and non-commercial tools were tested. The test results show large differences between the tools, but all could improve their support of SRMA, what might contribute to the adoption of ACC in practice.
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
The challenges we collectively face, such as climate change, are characterized by more complexity, interdependence, and dynamism than is common for educational practice. This presents a challenge for (university) education. These transition challenges are often described as wicked or VUCA (Volatile, Uncertain, Complex, and Ambiguous) problems. In response, educational innovations that are inspired by ecology such as living labs are starting to emerge, but little is known about how learners engage within and with these more ecological forms of education. This work is an exploratory study into how learners navigate VUCA learning environments linked to tackling sustainability transition challenges, with a focus on the positive qualities of these experiences. This is done through interpretative phenomenological analysis (IPA) of seven students (using semi-structured interviews) of the MSC Metropolitan Analysis, Design and Engineering program, a joint degree from Wageningen University and Delft University of Technology in the Netherlands. The main findings, which are both psychological and educational, of this exploration include openness to new experiences (1), flexibility (2), a process appreciation of learning (3), a desire to create a positive impact on one’s direct biophysical environment (4) and society (5). In addition, we discuss the potential limitations of the malleability of these different qualities and propose future avenues for research into ecological learning for universities. This work closes by highlighting recommendations for educators to consider when designing or engaging in ecological forms of higher education that connect students to sustainability transitions.
DOCUMENT
Abstract-Architecture Compliance Checking (ACC) is useful to bridge the gap between architecture and implementation. ACC is an approach to verify conformance of implemented program code to high-level models of architectural design. Static ACC focuses on the modular software architecture and on the existence of rule violating dependencies between modules. Accurate tool support is essential for effective and efficient ACC. This paper presents a study on the accuracy of ACC tools regarding dependency analysis and violation reporting. Seven tools were tested and compared by means of a custom-made test application. In addition, the code of open source system Freemind was used to compare the tools on the number and precision of reported violation and dependency messages. On the average, 74 percent of 34 dependency types in our custom-made test software were reported, while 69 percent of 109 violating dependencies within a module of Freemind were reported. The test results show large differences between the tools, but all tools could improve the accuracy of the reported dependencies and violations.
DOCUMENT
From the article: Abstract. This exploratory and conceptual article sets out to research what arguments and possibilities for experimentation in construction exists and if experimentation can contribute towards more innovative construction as a whole. Traditional, -western- construction is very conservative and regional, often following a traditional and linear design process, which focuses on front-loaded cost savings and repetitive efficiency, rather than securing market position through innovation. Thus becoming a hindrance for the development of the sector as a whole. Exploring the effects of using the, in other design-sectors commonly and successfully practiced, “four-phased iterative method” in architectural construction could be the start of transforming the conservative construction industry towards a more innovative construction industry. The goal of this research is to find whether the proposed strategy would indeed result in a higher learning curve and more innovation during the - architectural- process. Preliminary research indicates that there is argumentation for a more experimental approach to construction.
DOCUMENT
