1 / 12

Software Engineering Improvement Plan FY12

Software Engineering Improvement Plan FY12. Process Improvement Goal(s). Maintain and improve LaRC’s capabilities to manage, develop, maintain, and acquire quality, safe, and reliable software Actively support NASA software process improvement efforts

stash
Download Presentation

Software Engineering Improvement Plan FY12

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. Software Engineering Improvement PlanFY12

  2. Process Improvement Goal(s) Maintain and improve LaRC’s capabilities to manage, develop, maintain, and acquire quality, safe, and reliable software Actively support NASA software process improvement efforts Champion software process improvements across LaRC

  3. Scope of Process Improvement -LaRC Organizations Develop/Manage/Acquire Class A-E Software Develop/Manage/Acquire Class C-E Software Pursuing CMMI Appraisal ratings within the Directorate

  4. Tactic for Phasing in HQ Software Requirements & Improvements • NASA HQ Software Requirements: • Maintain awareness of NASA HQ software requirement development/modifications • Identify and support LaRC needs • Flow-down approved NASA HQ software requirements to the Center • Initially target organizations with higher classes of software (A-C) • Follow-up with needs for lower classes of software • Sponsor training opportunities as required • Provide improvement support to software projects • CMMI practices/ratings: • Maintain awareness of NASA HQ expectations • Monitor organizations with current CMMI ratings and ongoing process improvement activities • Sponsor CMMI appraisals/renewals as required • Sponsor training opportunities as required • Identify and distribute lessons learned and best practices

  5. Ownership of the LaRC Software Engineering Improvement Plan • The activities documented in this Plan are managed and monitored by the SEPG, under the direction of the software MSG in accordance with their charters (see Langley Policy Directive 1150.2). • The NASA Software Engineering Initiative Implementation Plan requires the naming of a “software champion” for the Center, and the Chair of the SEPG is hereby so designated.

  6. Tactic for Monitoring Plan • Progress, accomplishments, and status on the plan are briefed by the Chair of the SEPG to Headquarters/Office of Chief Engineer (HQ/OCE) and the Agency/Software Working Group approximately every six months • Status on the plan is also briefed by the Chair of the SEPG to the LaRC MSG approximately annually • Highlights of major Plan accomplishments (e.g. successful CMMI appraisals) are submitted to the HQ/OCE Head of the Software Engineering Initiative to include in the monthly brief to the NASA Chief Engineer

  7. Contact List

  8. NASA HQ Strategies and Objectives FY 12 • SW Engineering Handbook: Agency review and completion 2nd Qtr • Common Agency-wide Software Processes: Begin Phase 1 • Small Projects and Software Requirements • SW Cost Estimation Guidance • Update SW Engineering Curriculum & begin filling course gaps FY 13 • Common Agency-wide Software Processes: Complete Phase 1, Begin Phase 2 • Strategy to adopt/incorporate industry software standards • SW Engineering Training: complete filling course gaps FY 14 • Common Agency-wide Software Processes: Complete Phase 2, Begin Phase 3 (Agency-wide appraisal) • Update NPR 7150.2 Rev. “B” and submit for NODIS Review

  9. Tactic for Supporting Implementation of NASA HQ Strategies & Objectives • Maintain awareness of NASA HQ improvement efforts • Attend weekly Software Working Group meetings/telecoms • Attend scheduled Software Working Group Face-to-Face meetings • Support NASA HQ sponsored tasks/working groups • Consolidated Agency Principles and Processes for Software (CAPPS) • Strategy to Adopt/Incorporate Industry-wide Standards • NASA Software Cost Estimation Improvement • Software Engineering Processes for Small Projects • Software Engineering Handbook Review • Training Requests and Reviews • Software Inventory

  10. Schedule FY12 Schedules will be worked with the NASA SWG Task Leads Nov 2011 – Software Working Group Face-to-Face (MSFC) Dec 2011 – LaRC OCE Survey Software Inventory May 2012 – Software Working Group Face-to-Face (IV&V Facility)

  11. LaRC Software Training Plan – Part 1 The SEPG training responsibilities • Once notified, through the Software Working Group or NASA Safety Center (NSC), of training class seats available at other NASA Centers: • An article on the @LaRC web site is also posted to provide details • The class name, vendor, and registration instructions are posted on LaRC SPII web site under “Agency Software Assurance and Engineering Training” (https://sites-e.larc.nasa.gov/sweng/ ) • The SEPG encourages the software Branch managers to submit yearly a list of software engineering training needs to both the SEPG call and the LaRC local training office call • Training requests and CMMI assessment needs sent to the SEPG are prioritized, and submitted to the OCE Training Subgroup Chair as part of a yearly OCE call; the OCE determines what training and assessment requests HQ will fund Implementation • When on site LaRC classes are funded (either by the local training office or by OCE or NSC), the SEPG assists the local training office as needed in setting up the training logistics, classroom preparation, class advertisements, coordinating delivery of training materials, etc. • When LaRC CMMI activities (assessments/workshops) are funded by OCE, the SEPG works directly with the vendor to: develop a schedule of events and participant involvement, schedule rooms, obtain necessary plan signatures, provide briefing materials, etc.; the SEPG also oversees and participates in the CMMI activities

  12. LaRC Software Training Plan – Part 2 Training Records and Forms • Individual student training records and forms are housed in the NASA SATERN • Yearly training and assessment requests submitted to the OCE are provided using the form and format provided by Training Subgroup Chair • Records of CMMI assessments are maintained by the SEPG (aeroCOMPASS) Training resource • Because of reductions in OCE Center Plan funding and FTEs, the SEPG has no funding of its own to pay for software classes or CMMI activities • The SEPG relies on HQ/OCE, the local training office, NSC, and APPEL to fund training courses or CMMI activities • Once funded, the SEPG helps coordinate and facilitate the activities Minimum training requirements • Minimum training requirements are those required by CMMI • Those training requirements are fulfilled by SEPG and Process Area Owners mentoring and training on an as needed basis (usually in conjunction with CMMI process area specific improvement efforts) • SEPG 1-on-1 mentoring is also provided to projects and Branch Heads Training class availabilities are published through @LaRC announcements and on the SPII web site

More Related