January Software Research and Technology Infusion 14 January 2008 Presented by Lisa Montgomery, NASA Pavan Rajagopal, GCS

January Overview  Background  Goal & Approach  Collaboration concept  Funding for Collaboration  Selected Technologies  Collaboration Roles  Next Steps

January Background  Materialized as a collaborative effort between Office of the Chief Engineer and the Software Assurance Research Program (SARP).  Goal: Transfer mature technology into practice …and reduce the risk of doing so NOT – further develop the technology

January Background  As a part of the SARP, Research Infusion seeks to support NASA’s missions. To do that, we look to the Centers to both propose work and evaluate those proposals.  Selection recommendations are made by a group representing most, if not all, Centers. This group will be reconfigured this year to ensure balance.  Final approval is given by the SEB so that an Agency perspective is maintained.

FY07 Research Infusion Initiatives ► Infusion of Perspective-Based Inspection in NASA IV&V ► Infusion of Requirements Assistance into CEV IV&V Validation Activities ► Supporting Model-Based Systems and Software Engineering with SpecTRM ► Technology Infusion of CodeSonar into the Space Network Ground Segment ► Technology Infusion of SAVE into STRS Architecture Compliance Verification at GRC ► Technology Infusion of SDA into the MOD Software Development Process January 2008

Previously completed Research Infusion Initiatives ► Technology Infusion of SAVE into the Common Ground Software Development Process for NASA Missions at JHU/APL ► Application of SCR to ISS Biological Research Project On-Orbit Crew Displays at ARC ► Application of SpecTRM at JPL's Advanced Project Design Team (TeamX) ► Infusion of CodeSurfer into TCMS Sustaining ► Infuse CodeSurfer into NASA Code S IV&V Process GSFC FSB Application of Perspective-Based Inspections ► Visit for the deliverables from these efforts that have been cleared for public releasehttp://sarpresults.ivv.nasa.gov January 2008

7 Infusing Software Research and Technologies  Intent of RI is to support increased software assurance and technical excellence ►By providing an opportunity for NASA project teams to evaluate new technologies − While mitigating some of the risks  Approach ►The RI Team identifies technologies to solve Software Development and Assurance challenges − Surveys new SW engineering research areas − Identifies promising technologies which could be adopted by NASA ►The Team also surveys the commercial marketplace for potential technologies not already in widespread use in NASA

January Infusing Software Research and Technologies  Approach (continued) ►Offer selected technologies to the NASA software development/assurance community ►Foster collaborations between the technology developers and NASA software developers and SQA ►Provide funding to reduce the risk of applying a new technology ►Generate empirical data to support good engineering decisions about the value of adopting these technologies.

January Collaborations  How ►Initiated by a individual involved with software development or assurance who wants to bring on board a candidate technology  Purpose ►Benefit the software development project ►Validate the technology ►Generate empirical data to assess adoption − Not intended to develop the research Funding available for— ►Training and consulting in the use of the technology ►License fees in the case of commercial technologies ►Applying the technology ►Collecting & analyzing data ►Reporting results

January Funding for Collaborations  Funding for collaborations available via the Software Assurance Research Program (SARP). ►History: 15+ projects in the range $15K - $45K ►Competition for SARP funds is among the NASA Centers and JPL. Proposals must come from a civil servant or a contractor who has a contractual vehicle in place with NASA. − Scope and POP of contract must be able to support the collaboration − Note: NO NEW CONTRACTS WILL BE AWARDED ►Proposal template and instructions on the Research Infusion website u ►Proposals Due: By 5:00 PM ET Friday, 21 st March 2008 ►Collaborations Start: 9 th June 2008

January Funding for Collaborations (cont.)  Mechanization ►The Principal Investigator (PI) represents the organization which plans to apply the new technology. PI can be a civil servant or contractor. ►Proposals must identify a NASA CS Point of Contact (POC) responsible for managing the collaboration − If PI is a contractor, often the POC is the COTR or technical manager on the PI’s contract − POC is responsible for coordinating the mechanization of the funding ►Either the PI or the POC can pay the technology provider ►In-kind funding is welcome!

January Selected Technologies  Identified from ►NASA-sponsored software engineering and assurance research ►Leading edge commercial tools ►Center input  Reviewed by researchers experienced in tech transfer of software engineering research  Send us suggestions for next time. ►SE & SA development problem areas ►SE & SA technologies ►Send suggestions to

January Selected Technologies (continued)  Technology Selection Criteria ►Focus on Software Development or Software Assurance ►Address a known need/requirement: − Software Architecture Specification and Analysis − Model based software development and assurance − Improvement of SW development processes − Enhanced SW verification ►Robust and mature with good user documentation ►Demonstrated successes outside of a single domain or application ►Not currently in widespread use within NASA ►Assurance of user support from technology providers

January Selected Technologies (continued)  List and detailed description of offered technologies provided on RI Website ►Over 40 technologies reviewed ►Twenty-five technologies selected for 2008 Infusion

January Collaboration Roles  Roles of the Principal Investigator ►During proposal preparation: − Works with technology provider to plan collaboration and select suitable application  Must have buy-in from the technology provider − Writes and submits the proposal ►Should proposal be selected: − Coordinates training course with developer − Identifies software artifacts to which the technology will be applied − Applies the technology (may require multiple iterations) − Collects data & evaluates its performance − Writes final report

January Collaboration Roles (continued)  Roles of the Technology Provider : ►During proposal preparation − Helps to plan the collaboration, including assisting in the selection of a suitable application ►If Principal Investigator’s proposal is accepted − Provides any necessary training course (preferably on-site) − Provides tutorial and other user documentation − Provides customer support throughout the collaboration

January Next Steps  If you’re interested in a collaboration involving a Research Infusion technology, check out the collaboration proposal process at:  We will help broker matches of technology and software developers.

Next Steps for FY 08 (and beyond)  Telecon Wednesday, 23 rd January  Proposal template released Friday, 25 th January  Solicitation closes Friday, 21 st March  Initial recommendations made Friday, 18 th April  SEB meets Friday, 2 nd May  Work for FY 08 initiatives should begin 2 nd June  FY 09 Research Infusion  Telecons for the FY09 Research Infusion activities should be held in July January 2008

Final thoughts  Research Infusion should be an opportunity to try an approach that you and your team thinks will help you do your work better  We are here to help  If you need more information,  If you need access to previous work not yet published,  If you need help making contact,  If you need additional support, contact us January 2008

20 Contact Information  RI Team   Lisa Montgomery, RI NASA Lead   Pavan Rajagopal, RI Contractor 

21 Questions? January 2008