Model-driven software engineering for construction engineering: Quo vadis?

Models are an inherent part of the construction industry, which leverages from the steady advancements in information and communication technology. One of these advancements is Building Information Modeling (BIM), which denotes the move from 2D drawings to having semantically rich models of the objects subject to construction. Additionally, the way stakeholders collaborate in construction projects and their organization is revisited. This is commonly denoted as Integrated Project Delivery (IPD). Both BIM and IPD originate from the basic principles of Lean Construction, the vision to minimize waste, increase value, and continuous improvement. The application of Model-driven Software Engineering (MDSE) to BIM is a natural choice. Although several approaches utilizing MDSE for BIM have been proposed, so far no structured overview of the current state of the art has been conducted. Such an overview is vitally needed, because the existing literature is fragmented among multiple research areas. Consequently, in this paper, we present a systematic literature review on the application of MDSE to BIM, IPD and Lean Construction resulting in a systematically derived taxonomy, which we used to classify 97 papers published between 2008 and 2018. Based on the taxonomy, we provide an analysis of the classified research showing (a) where the discourse on model-driven construction engineering currently is, (b) the state of the art of model-driven techniques in construction engineering and (c) open research challenges

Iterative criteria-based approach to engineering the requirements of software development methodologies

Software engineering endeavours are typically based on and governed by the requirements of the target software; requirements identification is therefore an integral part of software development methodologies. Similarly, engineering a software development methodology (SDM) involves the identification of the requirements of the target methodology. Methodology engineering approaches pay special attention to this issue; however, they make little use of existing methodologies as sources of insight into methodology requirements. The authors propose an iterative method for eliciting and specifying the requirements of a SDM using existing methodologies as supplementary resources. The method is performed as the analysis phase of a methodology engineering process aimed at the ultimate design and implementation of a target methodology. An initial set of requirements is first identified through analysing the characteristics of the development situation at hand and/or via delineating the general features desirable in the target methodology. These initial requirements are used as evaluation criteria; refined through iterative application to a select set of relevant methodologies. The finalised criteria highlight the qualities that the target methodology is expected to possess, and are therefore used as a basis for de. ning the final set of requirements. In an example, the authors demonstrate how the proposed elicitation process can be used for identifying the requirements of a general object-oriented SDM. Owing to its basis in knowledge gained from existing methodologies and practices, the proposed method can help methodology engineers produce a set of requirements that is not only more complete in span, but also more concrete and rigorous

Knowledge society arguments revisited in the semantic technologies era

In the light of high profile governmental and international efforts to realise the knowledge society, I review the arguments made for and against it from a technology standpoint. I focus on advanced knowledge technologies with applications on a large scale and in open- ended environments like the World Wide Web and its ambitious extension, the Semantic Web. I argue for a greater role of social networks in a knowledge society and I explore the recent developments in mechanised trust, knowledge certification, and speculate on their blending with traditional societal institutions. These form the basis of a sketched roadmap for enabling technologies for a knowledge society

Knowledge Enhanced Notes (KEN)

To aid the creation and through-life support of large complex engineering products, organisations are placing a greater emphasis on constructing complete and accurate records of design activities. Current documentary approaches are not sufficient to capture activities and decisions in their entirety and can lead to organisations revisiting and in some cases reworking design decisions in order to understand previous design episodes. This paper presents an overview of the challenges in creating accurate, re-usable records of synchronous design activities, enhancing the through-life support of engineering products, followed by the development of an information capture software system to address these challenges. The main objectives for the development of the Knowledge Enhanced Notes system are described followed by the techniques chosen to address the objectives, and finally a description of a use-case for the system. Whilst the focus of the KEN System was to aid the creation and through-life support of large complex engineering products through constructing complete and accurate records of design activities, the system is entirely generic in its application to synchronous activities

CSP methods for identifying atomic actions in the design of fault tolerant concurrent systems

Limiting the extent of error propagation when faults occur and localizing the subsequent error recovery are common concerns in the design of fault tolerant parallel processing systems, Both activities are made easier if the designer associates fault tolerance mechanisms with the underlying atomic actions of the system, With this in mind, this paper has investigated two methods for the identification of atomic actions in parallel processing systems described using CSP, Explicit trace evaluation forms the basis of the first algorithm, which enables a designer to analyze interprocess communications and thereby locate atomic action boundaries in a hierarchical fashion, The second method takes CSP descriptions of the parallel processes and uses structural arguments to infer the atomic action boundaries. This method avoids the difficulties involved with producing full trace sets, but does incur the penalty of a more complex algorithm

The Need and Requirements to a Strategy Ontology

The importance of strategy and strategy construct is not a new phenomenon. However as strategy work becomes less tangible, concerns with understanding, describing, and managing strategies develops into an increasingly complex subject. Current strategy concepts are dispersed and lack integration. Moreover, the enablement of modelling practices around strategy concepts considering the entire strategy lifecycle are also missing. Consequently, this paper focuses on issues with strategy in theory and practice, why a strategy ontology is needed and how this can be developed

An active-architecture approach to COTS integration

Commercial off-the-shelf (COTS) software products are increasingly used as standard components within integrated information systems. This creates challenges since both their developers and source code are not usually available, and the ongoing development of COTS cannot be predicted. The ArchWare Framework approach recognises COTS products as part of the ambient environment of an information system and therefore an important part of development is incorporating COTS as effective system components. This integration of COTS components, and the composition of components, is captured by an active architecture model which changes as the system evolves. Indeed the architecture modelling language used enables it to express the monitoring and evolution of a system. This active architecture model is structured using control system principles. By modelling both integration and evolution it can guide the system’s response to both predicted and emergent changes that arise from the use of COTS products.Publisher PDFPeer reviewe

T-Visual Approach Slope Indicator System (T-VASIS) versus Precision Approach Path Indicator (PAPI) – the debate revisited

Two visual approach slope indicator lighting systems are in use in Australasia. These systems are designed to ameliorate and overcome the visual illusions associated with the approach and landing manoeuvre of aircraft. Using a flight simulator, 14 student pilot candidates, with little actual flying experience, ‘flew’ 10 approaches using PAPI and 10 approaches using T-VASIS. The approaches were ‘flown’ in various flight conditions including low visibility. The visual approach slope indicator lighting system was randomly assigned to each experimental condition. Results indicated that overall, there was less deviation from a correct glidepath when the approaches were ‘flown’ using T-VASIS. A post-flight survey indicated that participants found T-VASIS to be more intuitive. The results are discussed with reference to the prevailing preference of PAPI over T-VASIS by aviation authorities