Requirements engineering for computer integrated environments in construction

A Computer Integrated Environment (CIE) is the type of innovative integrated information system that helps to reduce fragmentation and enables the stakeholders to collaborate together in business. Researchers have observed that the concept of CIE has been the subject of research for many years but the uptake of this technology has been very limited because of the development of the technology and its effective implementation. Although CIE is very much valued by both industrialists and academics, the answers to the question of how to develop and how to implement it are still not clear. The industrialists and researchers conveyed that networking, collaboration, information sharing and communication will become popular and critical issues in the future, which can be managed through CIE systems. In order for successful development of the technology, successful delivery, and effective implementation of user and industry-oriented CIE systems, requirements engineering seems a key parameter. Therefore, through experiences and lessons learnt in various case studies of CIE systems developments, this book explains the development of a requirements engineering framework specific to the CIE system. The requirements engineering process that has been developed in the research is targeted at computer integrated environments with a particular interest in the construction industry as the implementation field. The key features of the requirements engineering framework are the following: (1) ready-to-use, (2) simple, (3) domain specific, (4) adaptable and (5) systematic, (6) integrated with the legacy systems. The method has three key constructs: i) techniques for requirements development, which includes the requirement elicitation, requirements analysis/modelling and requirements validation, ii) requirements documentation and iii) facilitating the requirements management. It focuses on system development methodologies for the human driven ICT solutions that provide communication, collaboration, information sharing and exchange through computer integrated environments for professionals situated in discrete locations but working in a multidisciplinary and interdisciplinary environment. The overview for each chapter of the book is as follows; Chapter 1 provides an overview by setting the scene and presents the issues involved in requirements engineering and CIE (Computer Integrated Environments). Furthermore, it makes an introduction to the necessity for requirements engineering for CIE system development, experiences and lessons learnt cumulatively from CIE systems developments that the authors have been involved in, and the process of the development of an ideal requirements engineering framework for CIE systems development, based on the experiences and lessons learnt from the multi-case studies. Chapter 2 aims at building up contextual knowledge to acquire a deeper understanding of the topic area. This includes a detailed definition of the requirements engineering discipline and the importance and principles of requirements engineering and its process. In addition, state of the art techniques and approaches, including contextual design approach, the use case modelling, and the agile requirements engineering processes, are explained to provide contextual knowledge and understanding about requirements engineering to the readers. After building contextual knowledge and understanding about requirements engineering in chapter 2, chapter 3 attempts to identify a scope and contextual knowledge and understanding about computer integrated environments and Building Information Modelling (BIM). In doing so, previous experiences of the authors about systems developments for computer integrated environments are explained in detail as the CIE/BIM case studies. In the light of contextual knowledge gained about requirements engineering in chapter 2, in order to realize the critical necessity of requirements engineering to combine technology, process and people issues in the right balance, chapter 4 will critically evaluate the requirements engineering activities of CIE systems developments that are explained in chapter 3. Furthermore, to support the necessity of requirements engineering for human centred CIE systems development, the findings from semi-structured interviews are shown in a concept map that is also explained in this chapter. In chapter 5, requirements engineering is investigated from different angles to pick up the key issues from discrete research studies and practice such as traceability through process and product modelling, goal-oriented requirements engineering, the essential and incidental complexities in requirements models, the measurability of quality requirements, the fundamentals of requirements engineering, identifying and involving the stakeholders, reconciling software requirements and system architectures and barriers to the industrial uptake of requirements engineering. In addition, a comprehensive research study measuring the success of requirements engineering processes through a set of evaluation criteria is introduced. Finally, the key issues and the criteria are comparatively analyzed and evaluated in order to match each other and confirm the validity of the criteria for the evaluation and assessment of the requirements engineering implementation in the CIE case study projects in chapter 7 and the key issues will be used in chapter 9 to support the CMM (Capability Maturity Model) for acceptance and wider implications of the requirements engineering framework to be proposed in chapter 8. Chapter 6 explains and particularly focuses on how the requirements engineering activities in the case study projects were handled by highlighting strengths and weaknesses. This will also include the experiences and lessons learnt from these system development practices. The findings from these developments will also be utilized to support the justification of the necessity of a requirements engineering framework for the CIE systems developments. In particular, the following are addressed. • common and shared understanding in requirements engineering efforts, • continuous improvement, • outputs of requirement engineering • reflections and the critical analysis of the requirements engineering approaches in these practices. The premise of chapter 7 is to evaluate and assess the requirements engineering approaches in the CIE case study developments from multiple viewpoints in order to find out the strengths and the weaknesses in these requirements engineering processes. This evaluation will be mainly based on the set of criteria developed by the researchers and developers in the requirements engineering community in order to measure the success rate of the requirements engineering techniques after their implementation in the various system development projects. This set of criteria has already been introduced in chapter 5. This critical assessment includes conducting a questionnaire based survey and descriptive statistical analysis. In chapter 8, the requirements engineering techniques tested in the CIE case study developments are composed and compiled into a requirements engineering process in the light of the strengths and the weaknesses identified in the previous chapter through benchmarking with a Capability Maturity Model (CMM) to ensure that it has the required level of maturity for implementation in the CIE systems developments. As a result of this chapter, a framework for a generic requirements engineering process for CIE systems development will be proposed. In chapter 9, the authors will discuss the acceptance and the wider implications of the proposed framework of requirements engineering process using the CMM from chapter 8 and the key issues from chapter 5. Chapter 10 is the concluding chapter and it summarizes the findings and brings the book to a close with recommendations for the implementation of the Proposed RE framework and also prescribes a guideline as a way forward for better implementation of requirements engineering for successful developments of the CIE systems in the future

Comparison of Traditional Versus CubeSat Remote Sensing: A Model-Based Systems Engineering Approach

This thesis compares the ability of both traditional and CubeSat remote sensing architectures to fulfill a set of mission requirements for a remote sensing scenario. Mission requirements originating from a hurricane disaster response scenario are developed to derive a set of system requirements. Using a Model-based Systems Engineering approach, these system requirements are used to develop notional traditional and CubeSat architecture models. The technical performance of these architectures is analyzed using Systems Toolkit (STK); the results are compared against Measures of Effectiveness (MOEs) derived from the disaster response scenario. Additionally, systems engineering cost estimates are obtained for each satellite architecture using the Constructive Systems Engineering Cost Model (COSYSMO). The technical and cost comparisons between the traditional and CubeSat architectures are intended to inform future discussions relating to the benefits and limitations of using CubeSats to conduct operational missions

Building product suggestions for a BIM model based on rule sets and a semantic reasoning engine

The architecture, engineering and construction (AEC) industry today relies on different information systems and computational tools built to support and assist in the building design and construction. However, these systems and tools typically provide this support in isolation from each other. A good combination of these systems and tools is beneficial for a better coordination and information management. Semantic web technologies and a Linked Data approach can be used to fulfil this aim. In this paper, we indicate how these technologies can be applied for one particular objective, namely to check a building information model (BIM) and make suggestions for that model regarding the building elements. These suggestions are based on information obtained from different data sources, including a BIM model, regulations and catalogues of locally available building components. In this paper, we briefly discuss the results obtained in the application of this approach in a case study based on structural safety requirements

Capturing variability in Model Based Systems Engineering

International audienceAutomotive model-based systems engineering needs to be dapted to the industry specific needs, in particular by implementing appropriate means of representing and operating with variability. We rely on existing modeling techniques as an opportunity to provide a description of variability adapted to a systems en- gineering model. However, we also need to take into account requirements related to backwards compatibility with current practices, given the industry experience in mass customization. We propose to adopt the product line paradigm in model-based systems engineering by extending the orthogonal variability model, and adapting it to our specific needs. This brings us to an expression closer to a description of constraints, related to both orthogonal variability, and to SysML system models. We introduce our approach through a discussion on the different aspects that need to be covered for expressing variability in systems engineering. We explore these aspects by observing an automotive case study, and relate them to a list of contextual requirements for variability management

Vision for Cross-Center MSBE Collaboration on the Gateway Program

Model-Based Systems Engineering (MBSE) can be a challenge when there is only one modeler and one model involved. For the Gateway Program, due to its unique acquisition approach, the modeling efforts involve multiple NASA centers with each developing their own models. Every additional model to be integrated compounds the difficulties, necessitating stronger ontologies and explicitly defined interfaces between models. To help facilitate this integration, a vision of collaboration between centers is in its beginning stages. This vision includes looking at models as systems themselves and developing their own use cases, requirements and interfaces between each of them. The goal of this presentation is to share the Gateway Program's cross-center vision for model collaboration, the lessons learned in developing and implementing that vision for the various system engineering products needed to satisfy life cycle review criteria and how treating models as systems helped in these efforts

Model Based Requirements Engineering for the Development of Modular Kits

The introduction of modular design increases complexity within product development and especially within Requirements Engineering. To handle this complexity, the approach of Model Based Systems Engineering is applied in this contribution. First, the origins of complexity in modular product development are introduced. Key challenges within Requirements Engineering are drawn up and then verified. A modeling method for requirements of modular kits is introduced and validated in the series development of hybrid drivetrain systems at a German automotive manufacturer. Increases in quality and a requirements reusability of over 80% were achieved. Thus, the capability of the modeling method is verified

Reclaiming human machine nature

Extending and modifying his domain of life by artifact production is one of the main characteristics of humankind. From the first hominid, who used a wood stick or a stone for extending his upper limbs and augmenting his gesture strength, to current systems engineers who used technologies for augmenting human cognition, perception and action, extending human body capabilities remains a big issue. From more than fifty years cybernetics, computer and cognitive sciences have imposed only one reductionist model of human machine systems: cognitive systems. Inspired by philosophy, behaviorist psychology and the information treatment metaphor, the cognitive system paradigm requires a function view and a functional analysis in human systems design process. According that design approach, human have been reduced to his metaphysical and functional properties in a new dualism. Human body requirements have been left to physical ergonomics or "physiology". With multidisciplinary convergence, the issues of "human-machine" systems and "human artifacts" evolve. The loss of biological and social boundaries between human organisms and interactive and informational physical artifact questions the current engineering methods and ergonomic design of cognitive systems. New developpment of human machine systems for intensive care, human space activities or bio-engineering sytems requires grounding human systems design on a renewed epistemological framework for future human systems model and evidence based "bio-engineering". In that context, reclaiming human factors, augmented human and human machine nature is a necessityComment: Published in HCI International 2014, Heraklion : Greece (2014

Improved Traceability of a Small Satellite Mission Concept to Requirements Using Model Based System Engineering

Model Based Systems Engineering (MBSE) has recently been gaining significant support as a means to improve the "traditional" document-based systems engineering (DBSE) approach to engineering complex systems. In the spacecraft design domain, there are many perceived and propose benefits of an MBSE approach, but little analysis has been presented to determine the tangible benefits of such an approach (e.g. time and cost saved, increased product quality). This paper presents direct examples of how developing a small satellite system model can improve traceability of the mission concept to its requirements. A comparison of the processes and approaches for MBSE and DBSE is made using the NASA Ames Research Center SporeSat CubeSat mission as a case study. A model of the SporeSat mission is built using the Systems Modeling Language standard and No Magic's MagicDraw modeling tool. The model incorporates mission concept and requirement information from the mission's original DBSE design efforts. Active dependency relationships are modeled to demonstrate the completeness and consistency of the requirements to the mission concept. Anecdotal information and process-duration metrics are presented for both the MBSE and original DBSE design efforts of SporeSat

A Model-Based Systems Engineering Approach to e-VTOL Aircraft and Airspace Infrastructure Design for Urban Air Mobility

This paper serves to contribute to Model-Based Systems Engineering (MBSE) by following the NASA Systems Engineering Handbook framework for a Systems Engineering (SE) design approach to an Electric Vertical Takeoff and Landing (e-VTOL) aircraft and the incorporating airspace infrastructure. The focus of this study is, by using the MBSE model created, to capture the technical requirements definition and design intent of the vehicle and airspace inclusive of community specific knowledge derived from the Federal Aviation Administration (FAA) NextGen Urban Air Mobility (UAM) Concept of Operations (ConOps) version 1.0. The stakeholder requirements derived from the FAA UAM NextGen ConOps will form the bedrock for the aircraft infrastructure requirements from which the flight mission requirements are derived. From these requirements, the profile of a notional flight mission is provided. Additionally, from the flight mission requirements, a design solution can be proposed and examined to ensure it meets the original stakeholder needs. The vehicle and associated airspace environment are modeled using an MBSE dedicated platform, Cameo Systems Modeler, in a language called SysML. The resulting MBSE model created can demonstrate the traceability between top-level system requirements down to the subcomponent-level design. In the conclusive study of the sub-system behavioral relationships, the analysis and validation of the proposed design solution can support model reliability