Software Management

558 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
558
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Software Management

  1. 1. Software Management (Significant Area of Management Concern) Internal Control Council (ICC) Meeting Feb. 5, 2004 Theron M. Bradley, Jr. Chief Engineer NASA Headquarters
  2. 2. <ul><li>Responsible Official: Theron M. Bradley, Jr., Chief Engineer, Code AE </li></ul><ul><li>Description: Software engineering, software assurance (which includes independent software verification and validation), information technology, and software research are core capabilities and key enabling assets necessary for successful missions. A coherent and coordinated approach to effective management of software across functional offices and Enterprises needs to be addressed and has been identified as a Significant Area of Management Concern. </li></ul>Software Management (Significant Area of Management Concern)
  3. 3. Action Plan <ul><li>#1. Form a senior-level steering board/committee/team to address executive level decisions concerning software within the Agency. </li></ul><ul><li>Complete: </li></ul><ul><ul><li>The Software Steering Board (SSB) Charter was signed by the Administrator, Mr. Sean O’Keefe on November 13, 2003 and is now an Agency organization as described in NASA Policy Guide 1000.3. </li></ul></ul><ul><li>#2. Establish appropriate funding for the NASA Software Engineering Initiative to improve the Agency’s capabilities in software engineering. ( http://www.hq.nasa.gov/office/codea/codeae/NSII_Plan.pdf ). </li></ul><ul><li>Complete: </li></ul><ul><li>The Office of Chief Engineer has established the following baseline budget to fund the NASA Software Engineering Initiative </li></ul><ul><li>FY04 FY05 FY06 FY07 FY08 FY09 </li></ul><ul><li>Baseline 4.0M 4.0M 4.0M 4.0M 4.0M 4.0M </li></ul><ul><li>FTEs 31CS 31CS 31CS 31CS 31CS 31CS </li></ul>
  4. 4. Action Plan <ul><li>#3. Conduct an assessment of NASA’s Independent Verification and Validation (IV&V) Facility’s procedures, processes, products, and customers. Under the leadership of Code Q, develop and implement a transition plan to improve the IV&V Facility management reporting, funding, project support, and technical capabilities. This transition plan should also include fulfillment of recommendations in the recent Inspector General (IG) Audit Report # IG-03-011, “Independent Verification and Validation.” </li></ul><ul><li>Complete: </li></ul><ul><li>NASA’s Independent Verification and Validation (IV&V) Facility’s procedures, processes, products, and customers was assessed and transition plan was developed under the leadership of Code Q to improve the IV&V Facility management reporting, funding, project support, and technical capabilities. </li></ul><ul><li>The Inspector General (IG) has communicated to the Chief Engineer the closing of Audit Report Independent Verification and Validation of Software, IG-03-011. The IG has determined that the actions taken by NASA are sufficient to disposition all of the audit's recommendations. (Dec 2003) </li></ul>
  5. 5. Action Plan <ul><li>#4. Coordinate the architecture, development, and update of the Agency’s software NASA Policy Directives/NASA Procedures and Guidelines (NPDs/NPG). </li></ul><ul><li>Responsibility assigned and action is being taken: </li></ul><ul><li>The Software Steering Board is chartered to coordinate and integrate the structure of the Agency's software NASA Policy Directives (NPD) and NASA Procedural Requirements (NPR) and make recommendations for changes to NASA management through the Chief Engineer. </li></ul><ul><li>The Software Steering Board reached agreement that there should be an overarching NPD for software that would be owned by the Office of the Chief Engineer and it would cover the principles, the philosophy, the software lifecycle, the roles and responsibilities across functional offices (Dec. 5, 2003). </li></ul>
  6. 6. Recommendations <ul><li>The Office of Chief Engineer (OCE) recommends that the significant area of management concern entitled Software Management be closed by the Internal Control Council </li></ul><ul><li>The Office of Chief Engineering also recommends that a new significant area of management concern entitled Monitoring Software Capability be opened to monitor the ongoing actions: </li></ul><ul><ul><li>Implementation by Centers of their component Software Engineering Initiative plans </li></ul></ul><ul><ul><li>The development and approval of an architecture for software NASA Policy Directives (NPD) and NASA Procedural Requirements (NPR) across HQ offices </li></ul></ul>
  7. 7. Backup Slides
  8. 8. Coordination of the Agency’s software NPD/NPGs <ul><li>Existing software related NPD/NPGs are: </li></ul><ul><ul><li>NPD 2820.1, NASA Software Policies (Code AO) </li></ul></ul><ul><ul><li>NPD 2800.1, Managing Information Technology (Code AO) </li></ul></ul><ul><ul><li>NPR 2800.1, Managing Information Technology (Code AO) </li></ul></ul><ul><ul><li>NPD 2810.1, Security of Information Technology (Code AO) </li></ul></ul><ul><ul><li>NPR 2810.1, Security of Information Technology (Code AO) </li></ul></ul><ul><ul><li>NPD 8730.4, Software Independent Verification and Validation (IV&V) Policy (Code Q) </li></ul></ul><ul><ul><li>NPD 2210.1, External Release of NASA Software (Code R) </li></ul></ul><ul><ul><li>NPR 2210.1, External Release of NASA Software (Code R) </li></ul></ul><ul><li>Code AO extended NPD 2820.1, NASA Software Policies, for one year (till May 2004) </li></ul>
  9. 9. Software Engineering Initiative Progress Indicators 31 Number of annual Civil Servant FTEs (Agency-wide) 12 Number of CMM/CMMI Rated Assessments (Agency-wide) 20 Number of CMM/CMMI Pre-Assessments (Agency-wide) 6 Number of Centers that have a Center Software Improvement website 165 Training Classes (Agency cumulative total FT, internal, etc. hosted by Center) 6 Number of Centers who have conducted a Software Profile, Census, or Organizational Scan 9 Number of Centers with software Management Steering Groups (MSG)* & Engineering Process Groups (EPG)*
  10. 10. Detailed Center Status Summary

×