Search results

Collaborative working using Information and Communication Technologies (ICT) systems in construction has become a reality as many activities are performed globally with actors located in various geographical locations. Computer Integrated Construction (CIC) is the type of ICT system that binds a fragmented and geographically distributed set of construction stakeholders collaborating together. Although the concept of CIC has been the subject of research for many years, its uptake has been very limited due to the development of the technology and its effective implementation. Research in this area is still premature and does not pay much attention to the development and implementation of the prototypes in the industry. As a result, the research developments have remained as prototypes although they have captured industrial interest. However, ongoing research within the field of construction IT is stressing that it is crucial to define research methodologies for human centred and adaptive CIC developments through industry‐wide knowledge sharing. The aim of this paper, through triangulated research strategy of interviews, surveys and case study is to justify the need for a requirements engineering process as a CIC development methodology for adaptive and user‐centred systems developments and as a guideline to bridge the gap between industry and the research community. The case study project is the DIVERCITY system development undertaken by researchers and practitioners across Europe to develop a shared virtual construction design and briefing environment that enables the construction industry to better undertake the client briefing and design review phases of a construction project.

The purpose of this paper is to describe and analyze the benefits of the application of a requirements engineering framework to assist Enterprise Resource Planning (ERP) development. This framework combines the technology-driven and the process-driven approaches for requirements analysis and implementation. Specific business process modeling methods enhance the framework and assist the formulation of the functional specifications of the ERP system and the management of requirements.

A case study strategy was chosen as the most appropriate method to answer the research question and test the theoretical propositions. The case study’s unit of analysis is a Greek manufacturing company and its ERP implementation project. A requirements engineering framework enhanced with business process modeling methods was applied and the results were evaluated using metrics for ERP implementation success. Data were collected using multiple sources of evidences, including interviews with various stakeholders, structured questionnaires, direct observations, vendors’ functionality papers and company’s documentation.

This study proves that the configuration of ERP’s reference models together with the adjustments of organization’s processes, provided through a structured requirements engineering framework can lead to reliable functional specifications, a smooth transition to an ERP system and, eventually, to successful ERP implementation, concerning its alignment with requirements.

A single case study is conducted in a typical manufacturing company, providing opportunities for further research in other industries, testing in parallel well-defined requirements and other success factors for ERP implementation.

The paper fulfils the identified needs for applied methodologies and frameworks for requirements engineering which can assist successful ERP implementations.

This paper aims to explore the requirements of organizational knowledge management initiatives using requirements engineering techniques, identifying the optimal techniques configuration and serving as a management tool for knowledge engineers.

The method is selection attributes. Knowledge management enablers are characterized and mapped with the coverage capabilities of requirements engineering techniques, using the attributes of the elicited object and a box-plot analysis. The information is gathered from 280 references, 32 companies and 16 experts in requirements engineering.

Requirements of organizational knowledge management initiatives are got optimally by combining interviews, use cases, scenarios, laddering and focus group techniques. The requirements of structure and processes are more complex to identify, while culture requirements are the best covered.

Knowledge management enablers are analyzed according to the current studies and comprehension of engineering techniques.

Knowledge engineers need to consider the coverage capabilities of engineering techniques to design an optimal requirement identification and meet the objectives of organizational knowledge acquisition initiatives. Requirement engineers can improve the requirements identification by a staged selection process.

The requirements of knowledge management initiatives that impact the community can be identified and traced to ensure the knowledge objectives. Requirements related to culture and people, like shared values, beliefs, and behaviors, are also considered.

To the best of the authors’ knowledge, this is the first study about formal requirement identification of knowledge management initiatives in the organizational context, providing the optimal configuration. A novel staged process is proposed for requirements engineering techniques selection, analyzing the enablers at component level and identifying the attributes associated with the elicited object.

The realization that concurrent engineering can be adopted in construction has led to various efforts to develop appropriate tools and techniques for its implementation in the industry. This paper discusses the role of client requirements processing in implementing concurrent engineering in construction. Client requirements processing refers to the definition, analysis, and translation of client requirements into solution‐neutral specifications for design. It is essential in maintaining focus on the client, and provides for the effective consideration, resolution and prioritization of the various perspectives within the client body. It also facilitates collaborative teamwork, compliance checking at every stage of the design and construction process, and the traceability of design decisions to explicit and implicit client requirements. The paper concludes with a description of a model for processing clients' requirements in construction, and an example of its practical application.

Requirements management (RM), as practised in the aerospace and defence sectors, attracts interest from construction researchers in response to longstanding problems of project definition. Doubts are expressed whether RM offers a new discipline for construction practitioners or whether it repeats previous exhortations to adopt a more disciplined way of working. Whilst systems engineering has an established track record of addressing complex technical problems, its extension to socially complex problems has been challenged. The dominant storyline of RM is one of procedural rationality and RM is commonly presented as a means of controlling dilettante behaviour. Interviews with RM practitioners suggest a considerable gulf between the dominant storyline in the literature and how practitioners operate in practice. The paper challenges construction researchers interested in RM to reflect more upon the theoretical debates that underpin current equivalent practices in construction and the disparity between espoused and enacted practice.

Very few high technology acquisition projects are successful. Problems occur far too often, regardless of whether one is acquiring clinical or business information systems, patient monitoring systems, or therapeutic and diagnostic systems. The odds are good that the project will be delivered late, cost far more than predicted, and not provide all of the features promised. Only 9 percent of projects are on time and under budget, and only about 16 percent deliver what was promised. The principal reason for project failure is improper management of the requirements of the system. Requirements engineering and management (REAM) is a skill from the systems engineering profession that can be learned by nearly any professional who is managing a technology acquisition project. This paper will tell you what REAM is and how it is done.

Quality Function Deployment (QFD) proposes to take into account the “voice of the customer,” through a list of customer needs, which are (qualitatively) mapped to technical requirements in House One. But customers do not perceive products in this space, nor do they not make purchase decisions in this space. Marketing specialists use statistical models to map between a simpler space of customer perceptions and the long and detailed list of needs. For automobiles, for example, the main axes in perceptual space might be categories such as luxury, performance, sport, and utility. A product’s position on these few axes determines the detailed customer requirements consistent with the automobiles’ position such as interior volume, gauges and accessories, seating type, fuel economy, door height, horsepower, interior noise level, seating capacity, paint colors, trim, and so forth. Statistical models such as factor analysis and principal components analysis are used to describe the mapping between these spaces, which we call House Zero.

This paper focus on House One. Two important steps of the product development process using House One are: (1) setting technical targets; (2) identifying the inherent tradeoffs in a design including a position of merit. Utility functions are used to determine feature preferences for a product. Conjoint analysis is used to capture the product preference and potential market share. Linear interpolation and the slope point formula are used to determine other points of customer needs. This research draws from the formal mapping concepts developed by Nam Suh and the qualitative maps of quality function deployment, to present unified information and mapping paradigm for concurrent product/process design. This approach is the virtual integrated design method that is tested upon data from a business design problem.

Machine design and manufacture is the key to the advancement of manufacturing industry. Before any machine can be designed, it is important to establish requirements of the machine. Identifies quality function deployment (QFD) as one of the tools that can be used to identify customer needs and link the needs to product design. By bringing forward customers’ requirements into the design process, design rework and unnecessary iteration between design and manufacture can be reduced. In this project, QFD for a pultrusion machine design has been chosen as a case study. QFD was applied at the front end of the design process. The QFD process started with identifying the customers and determining their needs. These needs were translated into engineering requirements which were then used to formulate general specifications of the machine. A step by step approach was introduced to make the QFD process more manageable. Reports on the first phase of a research project in which QFD was used to capture all vital information from the customers and translated that into engineering requirements.

The purpose of this study is the analysis of a security and privacy requirements engineering methodology. Such methodologies are considered an important part of systems’ development process when they contain and process a large amount of critical information, and thus need to remain secure and ensure privacy.

These methodologies provide techniques, methods and norms for tackling security and privacy issues in information systems. In this process, the utilisation of effective, clear and understandable modelling languages with sufficient notation is of utmost importance, as the produced models are used not only among IT experts or among security specialists but also for communication among various stakeholders, in business environments or among novices in an academic environment.

The qualitative analysis revealed a partial satisfaction of these principles.

This paper evaluates the effectiveness of a security and privacy requirements engineering methodology, namely, Secure Tropos, on the nine principles of the theory of notation.

General data protection regulation (GDPR) entered into force in May 2018 for enhancing personal data protection. Even though GDPR leads toward many advantages for the data subjects it turned out to be a significant challenge. Organizations need to implement long and complex changes to become GDPR compliant. Data subjects are empowered with new rights, which, however, they need to become aware of. GDPR compliance is a challenging matter for the relevant stakeholders calls for a software platform that can support their needs. The aim of data governance for supporting GDPR (DEFeND) EU project is to deliver such a platform. The purpose of this paper is to describe the process, within the DEFeND EU project, for eliciting and analyzing requirements for such a complex platform.

The platform needs to satisfy legal and privacy requirements and provide functionalities that data controllers request for supporting GDPR compliance. Further, it needs to satisfy acceptance requirements, for assuring that its users will embrace and use the platform. In this paper, the authors describe the methodology for eliciting and analyzing requirements for such a complex platform, by analyzing data attained by stakeholders from different sectors.

The findings provide the process for the DEFeND platform requirements’ elicitation and an indicative sample of those. The authors also describe the implementation of a secondary process for consolidating the elicited requirements into a consistent set of platform requirements.

The proposed software engineering methodology and data collection tools (i.e. questionnaires) are expected to have a significant impact for software engineers in academia and industry.

It is reported repeatedly that data controllers face difficulties in complying with the GDPR. The study aims to offer mechanisms and tools that can assist organizations to comply with the GDPR, thus, offering a significant boost toward the European personal data protection objectives.

This is the first paper, according to the best of the authors’ knowledge, to provide software requirements for a GDPR compliance platform, including multiple perspectives.