1 / 11

OSMA SARP Briefing

OSMA SARP Briefing . Nelson Keeler NASA IV&V Facility (304) 367-8201 Nelson.H.Keeler@ivv.nasa.gov. Overview. What is OSMA SARP? Objective of SARP Research Areas Who Manages OSMA SARP? Lifecycle of a Center Initiative Statistic for FY 2001 Partnership through Center & Academia

banyan
Download Presentation

OSMA SARP Briefing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OSMA SARP Briefing Nelson KeelerNASA IV&V Facility(304) 367-8201 Nelson.H.Keeler@ivv.nasa.gov

  2. Overview • What is OSMA SARP? • Objective of SARP • Research Areas • Who Manages OSMA SARP? • Lifecycle of a Center Initiative • Statistic for FY 2001 • Partnership through Center & Academia • Where to now??

  3. What is OSMA SARP? • Office of Safety and Mission Assurance (OSMA) Software Assurance Research Program (SARP) • Delegated Program designed to address fundamental problems in the field of software engineering, primarily as it relates to: • Software Safety • Quality • Testability • Reliability • IV&V (a lot of focus this year)

  4. Objective of SARP • Identify promising new information technologies that facilitate NASA missions • Support NASA’s strategic goals of safer, faster, better, cheaper missions • Identify, develop, adopt and integrate software engineering “best practices” into NASA programs that result in reduced software cost, improved delivery time and increase software safety and quality

  5. Research Areas • Historically, OSMA focuses on, but not limited to the following research areas: • Software Requirements Engineering • Software Architecture Verification • Operating Systems • Software Code Verifications • Software Test Engineering • System Safety & Risk Management • Software Reliability Engineering • New and Advanced Engineering

  6. Who manages OSMA SARP? • Sponsored by the Office of Safety and Mission Assurance • Delegated Program Manager • Appointed each year by the NASA Deputy Associate Administrator to oversee the SARP • NASA Independent Verification and Validation Facility • Day to day management

  7. Lifecycle of a Research Initiative • Two types of Research Initiatives: • Center Initiatives • West Virginia University Initiatives • Research Initiatives are submitted each fiscal year (October 1 to September 30) in the form of a Center Software Initiative Proposal (CSIP) • Research Initiatives can last up to three years, but must be resubmitted each year • Results of each year’s initiatives are presented at the OSMA Software Assurance Symposium

  8. Statistic for FY 2001 • FY 2001 funding was 3.5 million with 900K over guidance. (With the restoration of the 900K, FY 2002 funding will be 4.9 million.) • 22 Center Initiatives (CIs) • 6 NASA Centers plus the IV&V Facility • Multiple Universities and contractors • 2 Independent Universities • 1 Independent Contractor • 8 University Initiatives through WVU

  9. Partnerships through Centers & Academia University of Montana University of Maryland GRC Portland State SEI JPL GSFC Ames LaRC IV&VWVU FAU JSC MSFC

  10. Where to Now? • The Key Word is “Relevance” We have to conduct the research which NASA needs before NASA needs it • Mission requirements drive new demands on software • Long duration • Compressed development • New software development tools and practices won’t allow “business as usual” • Developer will use the tools available • Software assurance must stay a step ahead • Do research which is extremely valid

  11. Where to Now?? • To this end, researchers must: • Understand what tools and practices software developers will likely be using 5 years from now • Read, attend conferences, be part of the research community • Be familiar with the requirements of upcoming missions • Tie their research to one or more ongoing NASA projects and grow with the projects • Must contribute to mission success • Follow through with training and documentation that will make research results usable, by future developers

More Related