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
Renewable energy sources have an intermittent character that does not necessarily match energy demand. Such imbalances tend to increase system cost as they require mitigation measures and this is undesirable when available resources should be focused on increasing renewable energy supply. Matching supply and demand should therefore be inherent to early stages of system design, to avoid mismatch costs to the greatest extent possible and we need guidelines for that. This paper delivers such guidelines by exploring design of hybrid wind and solar energy and unusual large solar installation angles. The hybrid wind and solar energy supply and energy demand is studied with an analytical analysis of average monthly energy yields in The Netherlands, Spain and Britain, capacity factor statistics and a dynamic energy supply simulation. The analytical focus in this paper differs from that found in literature, where analyses entirely rely on simulations. Additionally, the seasonal energy yield profile of solar energy at large installation angles is studied with the web application PVGIS and an hourly simulation of the energy yield, based on the Perez model. In Europe, the energy yield of solar PV peaks during the summer months and the energy yield of wind turbines is highest during the winter months. As a consequence, three basic hybrid supply profiles, based on three different mix ratios of wind to solar PV, can be differentiated: a heating profile with high monthly energy yield during the winter months, a flat or baseload profile and a cooling profile with high monthly energy yield during the summer months. It is shown that the baseload profile in The Netherlands is achieved at a ratio of wind to solar energy yield and power of respectively Ew/Es = 1.7 and Pw/Ps = 0.6. The baseload ratio for Spain and Britain is comparable because of similar seasonal weather patterns, so that this baseload ratio is likely comparable for other European countries too. In addition to the seasonal benefits, the hybrid mix is also ideal for the short-term as wind and solar PV adds up to a total that has fewer energy supply flaws and peaks than with each energy source individually and it is shown that they are seldom (3%) both at rated power. This allows them to share one cable, allowing “cable pooling”, with curtailment to -for example-manage cable capacity. A dynamic simulation with the baseload mix supply and a flat demand reveals that a 100% and 75% yearly energy match cause a curtailment loss of respectively 6% and 1%. Curtailment losses of the baseload mix are thereby shown to be small. Tuning of the energy supply of solar panels separately is also possible. Compared to standard 40◦ slope in The Netherlands, facade panels have smaller yield during the summer months, but almost equal yield during the rest of the year, so that the total yield adds up to 72% of standard 40◦ slope panels. Additionally, an hourly energy yield simulation reveals that: façade (90◦) and 60◦ slope panels with an inverter rated at respectively 50% and 65% Wp, produce 95% of the maximum energy yield at that slope. The flatter seasonal yield profile of “large slope panels” together with decreased peak power fits Dutch demand and grid capacity more effectively.
DOCUMENT
Business process modeling and system dynamics are different approaches that are used in the design and management of organizations. Both approaches are concerned with the processes in, and around, organizations with the aim to identify, design and understand their behavior as well as potential improvements. At the same time, these approaches differ considerably in their methodological focus. While business process modeling specifically takes the (control flow of) business processes as its primary focus, system dynamics takes the analysis of complex and multi-faceted systems as its core focus. More explicitly combining both approaches has the potential to better model and analyze (by way of simulation) complex business processes, while specifically also including more relevant facets from the environment of these business processes. Furthermore, the inherent ability for simulation of system dynamics models, can be used to simulate the behavior of processes over time, while also putting business processes in a broader multi-faceted context. In this paper, we report on initial results on making such a more explicit combination of business process modeling and system dynamics. In doing so, we also provide a step-by-step guide on how to use BPMN based models and system dynamics models together to model and analyze complex business processes, while illustrating this in terms of a case study on the maintenance of building facades.
LINK
Business process modeling and system dynamics are different approaches that are used in the design and management of organizations. Both approaches are concerned with the processes in, and around, organizations with the aim to identify, design and understand their behavior as well as potential improvements. At the same time, these approaches differ considerably in their methodological focus. While business process modeling specifically takes the (control flow of) business processes as its primary focus, system dynamics takes the analysis of complex and multi-faceted systems as its core focus. More explicitly combining both approaches has the potential to better model and analyze (by way of simulation) complex business processes, while specifically also including more relevant facets from the environment of these business processes. Furthermore, the inherent ability for simulation of system dynamics models, can be used to simulate the behavior of processes over time, while also putting business processes in a broader multi-faceted context. In this paper, we report on initial results on making such a more explicit combination of business process modeling and system dynamics. In doing so, we also provide a step-by-step guide on how to use BPMN based models and system dynamics models together to model and analyze complex business processes, while illustrating this in terms of a case study on the maintenance of building facades.
LINK
Een verticaal opgesteld zonnepaneel, gericht op het zuiden, produceert per jaar in Nederland ongeveer 70% van de elektriciteit die een scheef (hoek 35 graden) opgesteld paneel produceert. De productie van het verticaal opgestelde paneel is evenwel gelijkmatiger over het jaar verdeeld, past daardoor beter bij het consumptiepatroon van elektriciteit en vormt daardoor een geringere belasting voor het netwerk. Daarom zou overwogen moeten worden dergelijke opstellingen te promoten, door aangepaste subsidievoorwaarden.
DOCUMENT
From ACM: "In cases where architectural documentation is outdated or missing, software architecture reconstruction (SAR) techniques may be used to create architectural views of a system. This paper describes a case study in which SAR techniques are applied to reconstruct module views of a case system; a debt settlements suite for local governments, developed in C#. A manual approach and its results are described and compared to the outcome of a layers reconstruction algorithm. Furthermore, this paper explains how software architecture compliance checking (SACC) techniques may help to test the results of reconstruction activities. In this study, SAR and SACC were supported by HUSACCT, a tool that provides rich sets of module and rule types in support of layers, facade, and gateway patterns." https://doi.org/10.1145/3129790.3129809
DOCUMENT
Dealing with and maintaining high-quality standards in the design and construction phases is challenging, especially for on-site construction. Issues like improper implementation of building components and poor communication can widen the gap between design specifications and actual conditions. To prevent this, particularly for energy-efficient buildings, it is vital to develop resilient, sustainable strategies. These should optimize resource use, minimize environmental impact, and enhance livability, contributing to carbon neutrality by 2050 and climate change mitigation. Traditional post-occupancy evaluations, which identify defects after construction, are impractical for addressing energy performance gaps. A new, real-time inspection approach is necessary throughout the construction process. This paper suggests an innovative guideline for prefabricated buildings, emphasizing digital ‘self-instruction’ and ‘self-inspection’. These procedures ensure activities impacting quality adhere to specific instructions, drawings, and 3D models, incorporating the relevant acceptance criteria to verify completion. This methodology, promoting alignment with planned energy-efficient features, is supported by BIM-based software and Augmented Reality (AR) tools, embodying Industry 4.0 principles. BIM (Building Information Modeling) and AR bridge the gap between virtual design and actual construction, improving stakeholder communication and enabling real-time monitoring and adjustments. This integration fosters accuracy and efficiency, which are key for energy-efficient and nearly zero-energy buildings, marking a shift towards a more precise, collaborative, and environmentally sensible construction industry.
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
