Skip to main content

Currently Skimming:

3 Requirements Setting
Pages 25-32

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 25...
... The panel recognizes that requirements are often initially set at overly optimistic levels so that a program will attract funding. This issue is beyond the scope of our study and is not explicitly addressed here.
From page 26...
... If, on the other hand, the JCIDS/CBA/AoA process provided a quantitative linkage between mission accomplishment and system attributes, the acquisitions community would have an effective method for making decisions on threshold levels set by the requirements process and for understanding the cost effectiveness of changing those requirements.
From page 27...
... Testers are encouraged to double-check that proper reliability growth is planned and executed, to interact with independent operational testers, and to plan and execute developmental test and evaluation thoroughly enough to virtually ensure success in initial operational test and evaluation. With this approach, pro gram management offices, with only a small initial investment, can poten tially save large sums of money.
From page 28...
... In 3Thompson (1992:738-739) notes that the F-16a fighter is good example of the effects on system reliability when one is allowed to keep changing requirements: "Instead of the simple, austere, pure fighter it was originally planned to be, the air force made it into a dual purpose aircraft, used to attack ground targets as well as a dog-fighter.
From page 29...
... The focus is on the use of tools to formally translate and quantify requirements from high-level system and subsystem specifications, assess the feasibility of proposed requirements, and help examine the implications of trading off various performance capabilities (including various aspects of effectiveness and suitability, such as durability and maintainability)
From page 30...
... Furthermore, an overall modeling and simulation-based vision is crucial for identifying where initial efforts should be concentrated to achieve the required performance levels. Then, as development proceeds, modeling and simulation can be used to ensure that subsequent efforts remain focused on what is needed to achieve performance goals.
From page 31...
... Also, by verifying the control system before hardware prototyping and by using production code generated from the controller models, GM has rolled out production vehicles featuring the hybrid powertrain within four years of starting the control system design process. The ability to reuse design infor mation has helped the global development teams foster more efficient com munication and reduced response time, eliminating integration issues.
From page 32...
... Recommendation 1: The Office of the Under Secretary of Defense for Acquisition, Technology, and Logistics, and the Office of the Director of Operational Test and Evaluation, and their service equivalents should acquire expertise and appropriate tools related to model-based approaches for the requirements-setting process and for test case and scenario generation for validation. This expertise will be very beneficial in collaborating with defense contractors and in providing a systematic and rigorous framework for overseeing the entire requirements generation process.


This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.