We are upgrading the repository! A content freeze is in effect until November 22nd, 2024 - no new submissions will be accepted; however, all content already published will remain publicly available. Please reach out to repository@u.library.arizona.edu with your questions, or if you are a UA affiliate who needs to make content available soon. Note that any new user accounts created after September 22, 2024 will need to be recreated by the user in November after our migration is completed.

Show simple item record

dc.contributor.authorStevens, Craig
dc.contributor.authorWilliams, Bradley
dc.contributor.authorAdams, Angela
dc.contributor.authorGoodloe, Colby
dc.date.accessioned2019-06-26T19:28:50Z
dc.date.available2019-06-26T19:28:50Z
dc.date.issued2017
dc.identifier.citationC. 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.7943831en_US
dc.identifier.issn978-1-5090-1613-6
dc.identifier.doi10.1109/AERO.2017.7943831
dc.identifier.urihttp://hdl.handle.net/10150/633027
dc.description.abstractRequirements 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.sponsorshipNational Aeronautics and Space Administration through the New Frontiers Program [NNG15CR64C, NNG12FD66C, NNM10AA11C]en_US
dc.language.isoenen_US
dc.publisherIEEEen_US
dc.relation.urlhttp://ieeexplore.ieee.org/document/7943831/en_US
dc.rightsU.S. Government work not protected by U.S. copyright.en_US
dc.rights.urihttps://creativecommons.org/publicdomain/mark/1.0/
dc.titleCleared for launch — Lessons learned from the OSIRIS-REx system requirements verification programen_US
dc.typeArticleen_US
dc.contributor.departmentUniv Arizonaen_US
dc.identifier.journal2017 IEEE AEROSPACE CONFERENCEen_US
dc.description.notePublic domain articleen_US
dc.description.collectioninformationThis 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.versionFinal published versionen_US
dc.source.beginpage1
dc.source.endpage14
refterms.dateFOA2019-06-26T19:28:51Z


Files in this item

Thumbnail
Name:
20170002018.pdf
Size:
1.405Mb
Format:
PDF
Description:
Final Published version

This item appears in the following Collection(s)

Show simple item record

U.S. Government work not protected by U.S. copyright.
Except where otherwise noted, this item's license is described as U.S. Government work not protected by U.S. copyright.