Cleared for launch — Lessons learned from the OSIRIS-REx system requirements verification program
dc.contributor.author | Stevens, Craig | |
dc.contributor.author | Williams, Bradley | |
dc.contributor.author | Adams, Angela | |
dc.contributor.author | Goodloe, Colby | |
dc.date.accessioned | 2019-06-26T19:28:50Z | |
dc.date.available | 2019-06-26T19:28:50Z | |
dc.date.issued | 2017 | |
dc.identifier.citation | C. Stevens, B. Williams, A. Adams and C. Goodloe, "Cleared for launch — Lessons learned from the OSIRIS-REx system requirements verification program," 2017 IEEE Aerospace Conference, Big Sky, MT, 2017, pp. 1-14. doi: 10.1109/AERO.2017.7943831 | en_US |
dc.identifier.issn | 978-1-5090-1613-6 | |
dc.identifier.doi | 10.1109/AERO.2017.7943831 | |
dc.identifier.uri | http://hdl.handle.net/10150/633027 | |
dc.description.abstract | Requirements verification of a large flight system is a challenge. This paper describes the approach to verification of the Origins, Spectral Interpretation, Resource Identification, Security-Regolith Explorer (OSIRIS-REx) system requirements. It also captures lessons learned along the way from the systems engineers embroiled in this process. This paper begins with an overview of the mission and science objectives as well as the project requirements verification program strategy. A description of the requirements flow down is presented including an implementation for managing the thousands of program and element level requirements and associated verification data. This paper discusses both successes and methods to improve the managing of these data across multiple organizational interfaces. The teams risk-based approach to verifying system requirements at multiple levels of assembly is presented using examples from work at instrument, spacecraft, and ground segment levels. A discussion of system end-to-end testing limitations and their impacts to the verification program is included. Finally, this paper describes lessons learned during the execution of the verification program across multiple government and commercial organizations. These lessons and perspectives can be valuable to all space system engineers developing a large NASA space mission. | en_US |
dc.description.sponsorship | National Aeronautics and Space Administration through the New Frontiers Program [NNG15CR64C, NNG12FD66C, NNM10AA11C] | en_US |
dc.language.iso | en | en_US |
dc.publisher | IEEE | en_US |
dc.relation.url | http://ieeexplore.ieee.org/document/7943831/ | en_US |
dc.rights | U.S. Government work not protected by U.S. copyright. | en_US |
dc.rights.uri | https://creativecommons.org/publicdomain/mark/1.0/ | |
dc.title | Cleared for launch — Lessons learned from the OSIRIS-REx system requirements verification program | en_US |
dc.type | Article | en_US |
dc.contributor.department | Univ Arizona | en_US |
dc.identifier.journal | 2017 IEEE AEROSPACE CONFERENCE | en_US |
dc.description.note | Public domain article | en_US |
dc.description.collectioninformation | This item from the UA Faculty Publications collection is made available by the University of Arizona with support from the University of Arizona Libraries. If you have questions, please contact us at repository@u.library.arizona.edu. | en_US |
dc.eprint.version | Final published version | en_US |
dc.source.beginpage | 1 | |
dc.source.endpage | 14 | |
refterms.dateFOA | 2019-06-26T19:28:51Z |