A requirements engineering framework for integrated systems development for the construction industry

Computer Integrated Construction (CIC) systems are computer environments through which collaborative working can be undertaken. Although many CIC systems have been developed to demonstrate the communication and collaboration within the construction projects, the uptake of CICs by the industry is still inadequate. This is mainly due to the fact that research methodologies of the CIC development projects are incomplete to bridge the technology transfer gap. Therefore, defining comprehensive methodologies for the development of these systems and their effective implementation on real construction projects is vital. Requirements Engineering (RE) can contribute to the effective uptake of these systems because it drives the systems development for the targeted audience. This paper proposes a requirements engineering approach for industry driven CIC systems development. While some CIC systems are investigated to build a broad and deep contextual knowledge in the area, the EU funded research project, DIVERCITY (Distributed Virtual Workspace for Enhancing Communication within the Construction Industry), is analysed as the main case study project because its requirements engineering approach has the potential to determine a framework for the adaptation of requirements engineering in order to contribute towards the uptake of CIC systems

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

WESTT (Workload, Error, Situational Awareness, Time and Teamwork): An analytical prototyping system for command and control

Modern developments in the use of information technology within command and control allow unprecedented scope for flexibility in the way teams deal with tasks. These developments, together with the increased recognition of the importance of knowledge management within teams present difficulties for the analyst in terms of evaluating the impacts of changes to task composition or team membership. In this paper an approach to this problem is presented that represents team behaviour in terms of three linked networks (representing task, social network structure and knowledge) within the integrative WESTT software tool. In addition, by automating analyses of workload and error based on the same data that generate the networks, WESTT allows the user to engage in the process of rapid and iterative “analytical prototyping”. For purposes of illustration an example of the use of this technique with regard to a simple tactical vignette is presented

An Evaluation of Inter-Organizational Workflow Modelling Formalisms

This paper evaluates the dynamic aspects of the UML in the context of inter-organizational workflows. Two evaluation methodologies are used. The first one is ontological and is based on the BWW (Bunge-Wand-Weber) models. The second validation is based on prototyping and consists in the development of a workflow management system in the aerospace industry. Both convergent and divergent results are found from the two validations. Possible enhancements to the UML formalism are suggested from the convergent results. On the other hand, the divergent results suggest the need for a contextual specification in the BWW models. Ce travail consiste en une évaluation des aspects dynamiques du language UML dans un contexte de workflow inter-organisationnel. Le choix du language par rapport à d'autres est motivé par sa richesse grammaticale lui offrant une très bonne adaptation à ce contexte. L'évaluation se fait par une validation ontologique basée sur les modèles BWW (Bunge-Wand-Weber) et par la réalisation d'un prototype de système de gestion de workflows inter-organisationnels. À partir des résultats convergents obtenus des deux différentes analyses, des améliorations au formalisme UML sont suggérées. D'un autre coté, les analyses divergentes suggèrent une possibilité de spécifier les modèles BWW à des contextes plus particuliers tels que ceux des workflows et permettent également de suggérer d'autres améliorations possibles au langage.Ontology, Conceptual study, Prototype Validation, UML, IS development methods and tools., Ontologie, étude conceptuelle, validation du prototype, UML, méthodes et outils de développement IS

An Exploratory Study of Forces and Frictions affecting Large-Scale Model-Driven Development

In this paper, we investigate model-driven engineering, reporting on an exploratory case-study conducted at a large automotive company. The study consisted of interviews with 20 engineers and managers working in different roles. We found that, in the context of a large organization, contextual forces dominate the cognitive issues of using model-driven technology. The four forces we identified that are likely independent of the particular abstractions chosen as the basis of software development are the need for diffing in software product lines, the needs for problem-specific languages and types, the need for live modeling in exploratory activities, and the need for point-to-point traceability between artifacts. We also identified triggers of accidental complexity, which we refer to as points of friction introduced by languages and tools. Examples of the friction points identified are insufficient support for model diffing, point-to-point traceability, and model changes at runtime.Comment: To appear in proceedings of MODELS 2012, LNCS Springe

Perspective on Information Requirement Determination Practices in Kuwait: Familiarity, Usage and Perceived Value

Few studies have examined how Information Requirement Determination (IRD) is practiced in the Arab world. To lessen the gap, this empirical study reports on the perception of 19 IRD methods in Kuwait, an Arab country. Based on a sample of 87 software stakeholders, this study reports on the most known, widely used and highly valued IRD methods. Results show that Arab culture influences perception of IRD techniques in that: (i) the most used is the traditional technique (interview), followed by the formal analysis technique (DFD), and group elicitation technique (brainstorming); (ii) the most valued techniques from past projecst are external representation techniques (Decision trees), followed by unstructured elicitation techniques (goal oriented elicitation), and observation technique (prototyping); and (iii) the least known, used and valued techniques are UML, Ishikawa and cognitive technique (KJ- methods). In addition, the study reveals some additional factors that affect IRD practices such as the existence of a correlation between past IS project problems and the usage of three techniques (QFD, DFD and role playing), the existence of a correlation between two techniques (prototyping and decision trees) and the statement obtaining the right requirements is essential to successful system development . Other correlations were also found between some IRD techniques and specific used information system development methodologies. This paper discusses findings which are relevant to theory and practice

Business process simulation: An alternative modelling technique for the information system development process

This paper discusses the idea that even though information systems development (ISD) approaches have long advocated the use of integrated organisational views, the modelling techniques used have not been adapted accordingly and remain focused on the automated information system (IS) solution. Existing research provides evidence that business process simulation (BPS) can be used at different points in the ISD process to provide better integrated organisational views that aid the design of appropriate IS solutions. Despite this fact, research in this area is not extensive; suggesting that the potential of using BPS for the ISD process is not yet well understood. The paper uses the findings from three different case studies to illustrate the ways BPS has been used at different points in the ISD process. It compares the results against IS modelling techniques, highlighting the advantages and disadvantages that BPS has over the latter. The research necessary to develop appropriate BPS tools and give guidance on their use in the ISD process is discussed