You have requested a machine translation of selected content from our databases. This functionality is provided solely for your convenience and is in no way intended to replace human translation. Neither SPIE nor the owners and publishers of the content make, and they explicitly disclaim, any express or implied representations or warranties of any kind, including, without limitation, representations and warranties as to the functionality of the translation feature or the accuracy or completeness of the translations.
Translations are not retained in our system. Your use of this feature and the translations is subject to all use restrictions contained in the Terms and Conditions of Use of the SPIE website.
9 September 2015Requirements management lessons learned: fuzzy "most likely" versus clean shaven "not to exceed"
Mission objectives often have a level of imprecision that lends itself to a fuzzy logic approach, even though the more traditional approach is to flow down bimodal pass/fail “not to exceed” type of requirements. Examples will be given for large astronomical telescope applications involving optical performance, active wave front and control, and radiometric/stray light controls demonstrating the pros and cons of the two contrasting strategies. This paper provides an overview of lessons learned on different programs and how that information can be used reduce the cost, schedule, and success of future missions.
Paul A. Lightsey
"Requirements management lessons learned: fuzzy "most likely" versus clean shaven "not to exceed"", Proc. SPIE 9583, An Optical Believe It or Not: Key Lessons Learned IV, 95830B (9 September 2015); https://doi.org/10.1117/12.2196564
The alert did not successfully save. Please try again later.
Paul A. Lightsey, "Requirements management lessons learned: fuzzy "most likely" versus clean shaven "not to exceed"," Proc. SPIE 9583, An Optical Believe It or Not: Key Lessons Learned IV, 95830B (9 September 2015); https://doi.org/10.1117/12.2196564