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
This papers presents some ideas to use so-called software agents as a software representation of a product not only during manufacturing but also during the whole life cycle of the product. Software agents are autonomous entities capable of collecting useful information about products. By their design and capabilities software agents fit well in the concept of ubiquitous computing. We use these agents in our newly developed manufacturing process. This paper discusses further use of agent technology.
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
Dit essay geeft een systeemvisie op het ontwikkelen van embedded software voor slimme systemen: (mobiele) robots en sensornetwerken.
DOCUMENT
This paper describes an agent-based software infrastructure for agile industrial production. This production is done on special devices called equiplets. A grid of these equiplets connected by a fast network is capable of producing a variety of different products in parallel. The multi-agent-based underlying systems uses two kinds of agents: an agent representing the product and an agent representing the equiplet.
MULTIFILE
Over the past decade, journalists have created in-depth interactive narratives to provide an alternative to the relentless 24-hour news cycle. Combining different media forms, such as text, audio, video, and data visualisation with the interactive possibilities of digital media, these narratives involve users in the narrative in new ways. In journalism studies, the convergence of different media forms in this manner has gained significant attention. However, interactivity as part of this form has been left underappreciated. In this study, we scrutinise how navigational structure, expressed as navigational cues, shapes user agency in their individual explorations of the narrative. By approaching interactive narratives as story spaces with unique interactive architectures, in this article, we reconstruct the architecture of five Dutch interactive narratives using the walkthrough method. We find that the extensiveness of the interactive architectures can be described on a continuum between closed and open navigational structures that predetermine and thus shape users’ trajectories in diverse ways.
DOCUMENT
The current set of research methods on ictresearchmethods.nl contains only one research method that refers to machine learning: the “Data analytics” method in the “Lab” strategy. This does not reflect the way of working in ML projects, where Data Analytics is not a method to answer one question but the main goal of the project. For ML projects, the Data Analytics method should be divided in several smaller steps, each becoming a method of its own. In other words, we should treat the Data Analytics (or more appropriate ML engineering) process in the same way the software engineering process is treated in the framework. In the remainder of this post I will briefly discuss each of the existing research methods and how they apply to ML projects. The methods are organized by strategy. In the discussion I will give pointers to relevant tools or literature for ML projects.
LINK
Author-supplied abstract: Developing large-scale complex systems in student projects is not common, due to various constraints like available time, student team sizes, or maximal complexity. However, we succeeded to design a project that was of high complexity and comparable to real world projects. The execution of the project and the results were both successful in terms of quality, scope, and student/teacher satisfaction. In this experience report we describe how we combined a variety of principles and properties in the project design and how these have contributed to the success of the project. This might help other educators with setting up student projects of comparable complexity which are similar to real world projects.
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
A software system is described that uses the agent concept in the Cell Control layer. Important design goals are: the system continues as good as possible after a process crash, crashed processes are recreated whenever possible, and equivalent workstations are allocated dynamically. This project is carried out mainly to investigate whether the agent concept is applicable in such a situation. The system is not operational yet, but will be built in the period ahead. In addition, a graphic simulator for a small manufacturing system will be built for testing the agent structure.
DOCUMENT
