An investigation of facilitator‐assisted and CONOPS‐based requirements elicitation methods using a 2 × 2 factorial experimental design

S. Gulu Gambhir

Systems Engineering, 2001, vol. 4, issue 4, 272-286

Abstract: System developments are frequently unsuccessful as measured in performance, cost, and schedule dimensions. Previous research has traced many development problems to poor system requirements. A method called Facilitator‐Assisted Requirements Elicitation (FARE), which employs a technical facilitator for discussion of requirements based on a Concept of Operations (CONOPS) Matrix, is developed and tested. A 2 × 2 factorial design was used to examine the effects of two independent variables on the FARE method: (1) facilitator presence or absence and (2) CONOPS Matrix or free‐form development. Twenty‐four subjects were randomly divided into four groups. Each group was given the task of developing a set of requirements and recording both a priority and rationale for the inclusion of each requirement. The three dependent variables are Communications, measured by responses to a post‐experiment survey; Requirements Scope, measured by subjective evaluation of requirements sets by an independent panel; and Requirements Quality, also measured by the independent panel. Results indicate a significant improvement in Communications when a facilitator was present. Requirements Scope showed a significant improvement when either a facilitator or the CONOPS Matrix was used, but was degraded when both elicitation techniques were used in combination. A significant improvement in Requirements Quality was observed when the groups were facilitated versus when they were not facilitated. Overall, both the presence of the facilitator and the use of the CONOPS Matrix showed benefits. Degradation in Requirements Scope, observed when both techniques were used in combination, is believed to be the result of the time constraints imposed on the subjects. The results of the experimentation support the use of FARE as an effective approach for capturing requirements early in the development lifecycle, thereby avoiding costly requirements changes. © 2001 John Wiley & Sons, Inc. Syst Eng 4: 272–286, 2001

Date: 2001
References: View complete reference list from CitEc
Citations: View citations in EconPapers (2)

Downloads: (external link)
https://doi.org/10.1002/sys.1023

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:wly:syseng:v:4:y:2001:i:4:p:272-286

Access Statistics for this article

More articles in Systems Engineering from John Wiley & Sons
Bibliographic data for series maintained by Wiley Content Delivery ().