The First Requirements Elucidator Demonstration (FRED) tool
- 1 January 2004
- journal article
- research article
- Published by Wiley in Systems Engineering
- Vol. 7 (3) , 243-256
Abstract
The problem of poorly written requirements has been documented for at least the last ten years without much improvement. This paper describes applying technology in the form of a simple software tool containing an Expert System that can minimize the production of poorly worded requirements in the future and help ensure the completeness of the testing of poorly worded requirements. This paper also describes how the tool evolved and discusses how the tool can be used to prevent cost and schedule escalations due to some types of poorly worded requirements. © 2004 Wiley Periodicals, Inc. Syst Eng 7: 243–256, 2004Keywords
This publication has 13 references indexed in Scilit:
- 2.1.5 Does Object‐Oriented System Engineering Eliminate the Need for Requirements?INCOSE International Symposium, 2002
- 6.7.1 Program to Identify Potential Ambiguities in Requirements Written in EnglishINCOSE International Symposium, 2001
- 6.3.2 A Frame‐Based Approach to Requirements EngineeringINCOSE International Symposium, 2001
- 5.1.1 Keeping the Focus During Requirements AnalysisINCOSE International Symposium, 2001
- Knowledge management, insights from the trenchesIEEE Software, 2001
- Providing Pragmatic Advice On How Good Your Requirements Are ‐ The Precept “Requirements Counsellor” UtilityINCOSE International Symposium, 1999
- Yes Virginia, You Can Build a Defect Free System, On Schedule and Within BudgetINCOSE International Symposium, 1997
- Requirements Management Working Group: Characteristics of Good RequirementsINCOSE International Symposium, 1996
- Combining Knowledge and Metrics to Control Software Quality Factors1996
- Gaining the Competitive Edge through Effective Systems EngineeringINCOSE International Symposium, 1994