How to Set Requirements and Manage to Them
- Paper number
IAC-19,D1,5,10,x49628
- Author
Dr. Francesco Bordi, United States, The Aerospace Corporation
- Coauthor
Dr. Debra Emmons, United States, The Aerospace Corporation
- Coauthor
Mr. Steven Shinn, United States, NASA
- Coauthor
Mr. ROBERT BITTEN, United States, The Aerospace Corporation
- Year
2019
- Abstract
The portfolio of space flight science missions at NASA is divided into various classes, ranging from large and complex flagship missions to small responsive missions. We discuss in this paper a scheme to rationally decide to which class a proposed mission should be assigned, how to define the requirements for that mission, and how to manage to those requirements. The decision criteria include: expected development time; whether technology development is required prior to mission initiation; the life-cycle budget; the difficulty of the measurement and/or the operational requirements; the flexibility of the funding and performance requirements (to achieve Level 1 science), and the design lifetime. In our scheme, the requirements definition phase and management to those requirements will differ based on the class of the mission. This paper seeks to reduce the perceived ambiguity around mission class designation, and the resulting requirements definition and mission implementation processes.
- Abstract document
- Manuscript document
IAC-19,D1,5,10,x49628.pdf (🔒 authorized access only).
To get the manuscript, please contact IAF Secretariat.