© 2025 SURF
Mixed Reality for THUAS campus Advantages of Mixed Reality for sustainable built environments 1. Incorporate BIM models in real time 2. Multi operator / for quick and easy consultation 3. Onsite ease of use / you can always put on your headset 4. Overlay capabilities of the Mixed Reality Headsets 5. Hand tracking 6. Layering information in real-time 7. 3D view of the location/situation / information 8. Switch from Mixed Reality to Virtual Reality 9. Teleport capabilities
DOCUMENT
In software architecture, the Layers pattern is commonly used. When this pattern is applied, the responsibilities of a software system are divided over a number of layers and the dependencies between the layers are limited. This may result in benefits like improved analyzability, reusability and portability of the system. However, many layered architectures are poorly designed and documented. This paper proposes a typology and a related approach to assign responsibilities to software layers. The Typology of Software Layer Responsibility (TSLR) gives an overview of responsibility types in the software of business information systems; it specifies and exemplifies these responsibilities and provides unambiguous naming. A complementary instrument, the Responsibility Trace Table (RTT), provides an overview of the TSLR-responsibilities assigned to the layers of a case-specific layered design. The instruments aid the design, documentation and review of layered software architectures. The application of the TSLR and RTT is demonstrated in three cases.
DOCUMENT
In this paper a new graphical password scheme is presented using a dynamic layered combination of graphical elements. It has unique capabilities in terms of low memory burden due to a story based approach, while at the same time being very resistant to shoulder surfing threats. The results of a security evaluation confirm shoulder surfing resistance.
DOCUMENT
In this paper a new graphical password scheme is presented using a dynamic layered combination of graphical elements. It has unique capabilities in terms of low memory burden due to a story based approach, while at the same time being very resistant to shoulder surfing threats. The results of a security evaluation confirm shoulder surfing resistance.
LINK
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
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
In this paper the Feltscaping-method is described, its characteristics and requirements, and some examples of how it was used and further developed. In doing so this paper aims at embedding feltscaping into the existing discourse of arts-based research. Furthermore, it will reflect on possibilities for further development of the Feltscaping method.The development of the method started seven years ago, as Cora Jongsma as a way of delving into the different layers of the landscape connected with the landscape. The product of this process is a feltscape, a representation of the landscape made up of several layers of wool that tells a story about a specific area. The layering in the feltscape, in the beginning, was purely the result of interaction between the creative process, conversations with land users, landscape research and visual experience, drawing a parallel to the formation process of the landscape. Starting as a personal search of the artist on how to connect the feltscapes to the landscape, after a few years, developed into an instrument to stimulate good conversation with people that in one way or another are connected to the landscape. In this way, feltscapes enable the researcher to test and exchange own sensory perceptions and to extent existing knowledge or questions about the landscape by eliciting social interactions.
DOCUMENT
