Search results

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.

To present a methodology for requirements specification for assembly system reconfiguration.

Industrial needs were analysed through a series of interviews with personnel involved in the design and sales process. This was then compared to reported research in literature and a new method has been derived and demonstrated.

An improved methodology for requirements specification leading to more efficient design and deployment of reconfigurable assembly systems.

Provides a structured mechanism for performing requirements specification tasks that are currently done on an ad hoc basis.

This study proposes targeted modernization of the Department of Defense (DoD's) Joint Forces Ammunition Logistics information system by implementing the optimized innovative information technology open architecture design and integrating Radio Frequency Identification Device data technologies and real-time optimization and control mechanisms as the critical technology components of the solution. The innovative information technology, which pursues the focused logistics, will be deployed in 36 months at the estimated cost of $568 million in constant dollars. We estimate that the Systems, Applications, Products (SAP)-based enterprise integration solution that the Army currently pursues will cost another $1.5 billion through the year 2014; however, it is unlikely to deliver the intended technical capabilities.

Reflects on experiences when traditional IT approaches were used to design large IT systems and ended in failure.

The requirements‐gathering process is usually a very complex affair and can represent a major obstacle to successful system development. It is argued here that one reason for systems development projects' poor performance, or even failure, is the mismatch between the customer and the developer technical knowledge/understanding instigated by the differences in the cultural background of both sides. The main argument focuses on the reasons for system failure and how they relate to the diversity of knowledge and the understanding gaps that may exist between the business customers and the system developers.

The study reveals that the understanding gaps mainly result from lack of business operations knowledge on the developer side, matched by lack of technical appreciation and knowledge on the user side.

A practical approach using diagramming and Set mapping techniques is described, with an explanation of how it can be used to enhance human interaction in requirement identification and consequently help address the knowledge‐gap problem.

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 examine the information gathering methods used during enterprise system (ES) selection among Polish organizations and to have IT consulting experts evaluate these methods, which will result in identification of the preferred approach for the information‐gathering task during system selection.

The research has a qualitative exploratory design with grounded theory being the main research method. A mixed quantitative‐qualitative approach to data collection was used: an e‐mail‐based survey was used as an introductory stage to gather data on information‐gathering methods. The results of the survey were evaluated by ES experts during unstructured interviews. The interviews were then transcribed and coded according to the grounded theory coding techniques.

The evaluation of selection approaches revealed that the approach to information gathering should depend on the level of configurability of the systems subject to selection. Two generic approaches were identified: requirements driven – for highly configurable systems, and system functionality driven – for the systems offering limited configurability. Interaction between the customer and the bidder was also identified as the main condition for preparing the unbiased offer by the bidders.

Regarding the survey study, as the survey sample was small and the sample selection process was not random, the results should not be generalised to the whole population of Polish enterprises. It would be also beneficial to test the validity of the findings from the grounded theory study on the big population of ES bidders with the use of statistical methods.

For highly configurable systems, a model that includes a business process analysis, detailed requirements' specification and dedicated system functionality presentation is the preferred approach. A workshop is preferred to obtaining a ready requirements list. For systems offering limited configurability, an approach centred on system presentation is more suitable. In this case the requirements should be gathered during the presentation on a “gap‐fit” basis.

There is a significant lack of research that explores the selection process, with the stress on organizational needs and system functionality information gathering and makes indications for improvement of this process from the consulting enterprise (bidder) point of view. The paper fills this gap by presenting the results of a survey among Polish enterprises regarding selection routines and the evaluation of these routines by expert ES professionals, resulting in the development of the preferred set of information‐gathering methods.

The purpose of this paper is to investigate the perceptions of 19 requirement engineering (RE) techniques in Kuwait in term of three criteria “awareness,” “use,” and “perceived value generated over past system development projects.” Also, this paper aims to examine possible relationships between these RE techniques and two information system development success factors.

This paper develops a questionnaire and tests with a sample of respondents from 175 organizations in Kuwait.

Results show that: Arab culture influence perception of RE techniques; most companies have good knowledge of different techniques; several different techniques for identifying and analyzing customer requirements are used; the most highly valued RE techniques are decision trees, goal oriented, prototyping, data flow diagram (DFD), and interviews; six techniques (tree analysis, role playing, unified modeling language, Kawakita Jiro method, flow charts, and Ishikawa) are found to have the least perceived value; and only two techniques (prototyping and decision tree) are highly correlated with the statement “Obtaining the right requirements is a critical success factor for system development,” while other three techniques (quality function deployment, DFD and role playing) are correlated with “We experienced problems during past system developments projects because of wrong requirements collection.”

The study sheds light on perceptions on RE techniques perception in Kuwait where less is known about the subject from Western researchers.

This paper suggests re‐examining university curriculums in order to prepare students for familiarity with techniques that have proven their effectiveness elsewhere and call for more collaboration between academia and practitioners in order to appropriate research outcomes. In addition, this paper is of benefit to foreign consulting companies willing to penetrate the Gulf Cooperative Council.

This is the first Arab study that sheds light on system development practices in the Arab world.

Performance measurement is a subject that has been high on the agenda for over two decades. This article proposes making a contribution to this field by discussing how to deal systematically with all the requirements a performance measurement system (PMS) should fulfil.

Different requirements suggested in the performance measurement literature from the past 20 years have been analysed in order to structure the different tasks to conduct when designing a PMS.

The article explains how to separate requirements that can be linked to a PMS and to an individual performance measure. It also suggests three system classes depending on what requirements a PMS fulfils. Finally a three‐step procedure is proposed that describes how to evaluate and improve an existing PMS in a company.

In practice, it is difficult to deal with numerous requirements simultaneously when designing a PMS. The article supplies measurement practitioners with tools to identify any priority important requirements.

Several new ideas to the field of performance measurement are introduced and explained: the concept of system classes, classification of requirements and a simple three‐step procedure to evaluate and improve PMS.

This paper presents a recommendation on how one requirement elicitation technique supports the other techniques in defining system requirement for a case-based system. A case-based lesson planning system aims to assist teachers in constructing quality lesson plans through its cycle which begins with case retrieval. To retrieve relevant lesson plans, appropriate inputs should be used and the intended output needs to be identified via suitable requirement elicitation techniques. The use of a single technique might result in inadequate requirement specification, thus affecting the quality of the output requirements as well as quality of the final information system.

Requirement elicitation was carried out in three phases: phase I involved document review, phase II was an interview and phase III used a survey. Respondents of the study comprised experienced teachers as well as new teachers. This research used both qualitative and quantitative approaches to answer the research questions, which involved semi-structured interviews, document review and survey to collect the relevant data. Documents were reviewed by analysing lesson plans from three different countries. In addition, a review of lesson plans prepared by teachers and the standard syllabus were carried out. Findings from the document review were used in structured interviews using a teach-back technique, sorting and matrix of attribute-values. A questionnaire was then constructed based on the interviews and document review.

The findings of this initial study, as part of a larger research investigation, would help in knowledge modelling and representation. This will contribute to effective case retrieval via good design of the system input and output. The study identifies important elements of a lesson plan according to their ranking. Keywords that were used by teachers as input for retrieval were identified together with the expected output.

The main goal of requirement elicitation is to specify complete and detailed requirements of the proposed system. There are two main types of requirement: functional and non-functional requirements. This paper only focuses on functional requirements – specifically case retrieval with appropriate input and output.

Various requirement engineering (RE) techniques can be applied in different phases of requirement elicitation. Suitable technique should be chosen at different phases of RE, as it is important for triangulation purposes. Incomplete RE will affect the modelling part of system development, and, thus, affect the design and implementation of an information system.

Software engineer or anybody involved in system development should plan accordingly for the RE process. They should be creative and reasonable in selecting suitable RE techniques to be applied.

This study aims to gain understanding of the various aspects of lesson planning. Crucial knowledge in lesson planning that was gathered from the elicitation phase is modelled to have a good understanding of the problems and constraints among teachers. The findings of this initial study, as part of a larger research investigation, would help in knowledge modelling and representation. This will contribute to effective case retrieval via a good design of the system input and output.

This paper aims to identify a generic set of information requirements for facilities management (FM) systems, which should be included in BIM as-built models for efficient information exchange between BIM and FM systems, and to propose a process to identify, verify and collect the required information for use in FM systems during the project’s lifecycle.

Both qualitative and quantitative approaches were applied at different stages of the study’s sequential design. The collection and analysis of qualitative data was based on an extensive literature review of similar studies, standards, best practices and case study documentation. This was followed by a questionnaire survey of 191 FM practitioners in the UK. This formed the background of the third stage, which was the development of the information management process to streamline information exchange between building information models and FM systems.

The study identifies a generic list of information requirements of building information models to support FM systems. In addition, the study presents an information management process that generates a specific database for FM systems using an open data format.

The existing literature focuses on specific building types (educational buildings) or specific information requirements related to particular systems (mechanical systems). The existing standards, guidelines and best practices focus on the information requirements to support the operations and maintenance (O&M) phase in general. This study is different from previous studies because it develops a set of specific information requirements for building information models to support FM systems. FM organisations and owners can use the proposed list of information requirements as a base to generate specific data output for their FM systems’ input, to decrease the redundant activity of manual data entry and focus their efforts on key activities.