Software Quality SQ

1
Software Quality (SQ)

• Providing a set of tools for Software Assurance
  practitioners in the NASA community

Systems Assurance Manager (SAM) Role in SQ
Program
2
Course Objectives

• Provide an overview of Code 300s Software
  Quality Program
• Highlight the role of the SAM in implementing a
  successful program
• Raise awareness of NASA Agency and Center
  software initiatives that impact our efforts

3
Agenda

• NASA Software Assurance
• NASA Software Process Initiative (SPI)
• NASA GSFC CMMI Initiative
• NASA Software Assurance Requirements
• OSSMA Code 300 Software Quality (SQ) Program
• Process Map for SQ Program
• Software Assurance Website
• SEI CMMI
• CMMI PPQA Specific Goals and Practices
• CMMI Generic Goals and Practices
• Mapping SQ Program to PPQA
• SAMs Role
• Summary

4
NASA Software Assurance

• NASA SPI Initiative
• NASA GSFC CMMI Initiative
• NASA Software Assurance Requirements

5
NASA Software Process Improvement (SPI)

• The NASA Software Process Improvement (SPI)
  Initiative involves all NASA centers. Each
  center is required to have an Engineering Process
  Group (EPG) and an SPI Plan
• The SPI Goal is to advance software engineering
  practices to effectively meet the scientific and
  technological objectives of NASA
• Improve cost and schedule predictability, safety,
  reliability, and quality of software
• SPI has four top-level strategies to meet the
  initiative goals
• Implement a continuous software process and
  product improvement program across NASA and its
  contract community
• Improve safety, reliability, and quality of
  software through the integration of sound
  software engineering principles and standards
• Improve NASAs software engineering practices
  through research
• Attract and retain software engineers and improve
  their knowledge and skills

6
NASA Software Improvement Initiative
(SPI)Continued

• NASA SPI Plan requires each Center to select
  either
• SEI SW-CMM - Software Engineering Institute (SEI)
  Capability Maturity Model for Software or
• SEI CMMI SE/SW/SS - Software Engineering
  Institute (SEI) Capability Maturity Model
  Integration
• The Goddard Space Flight Center (GSFC) has
  selected CMMI-Systems Engineering/Software/
  Supplier Sourcing (SE/SW/SS) continuous
  representation

So what does this mean to Code 300?
7
NASA GSFC CMMI Initiative

• Code 300 is required to meet the requirements of
  the CMMI Process and Product Quality Assurance
  (PPQA) key process area
• Code 300 will work with Code 500 as they
  implement the new process model
• Code 300 will be pre-assessed for PPQA (for
  JWST, SDO, and ST-5) the week of August 16, 2004,
  with target dates as follows for GSFC Software
• CMMI Level 2 by the end of 2005 for FLT SW
• CMMI Level 3 by the end of 2006 for FLT SW
• CMMI Level 2 by the end of 2006 for ISD and
  Code 400 Mission SW
• CMMI Level 3 by the end of 2007 for ISD and
  Code 400 Mission SW

So what does this mean to you as SAMs?
8
NASA GSFC CMMI Initiative (cont.)

• What will this initiative entail?
• Formal SQ Programs based on NASA Agency
  requirements standards
• New SQ procedures for Assessments, Reporting,
  Records, and Metrics
• SQ Tools (e.g., forms, checklists, and templates)
• Training (for the people performing or supporting
  the process)
• Service Order updates to include
• SQA Plan (based on IEEE 730 STD) for each
  software system
• SQ Schedule of planned activities
• SQ Reports for each assessment
• Records of all assessments
• SQ Metrics

9
NASA GSFC CMMI Initiative (cont.)

• What about Resource Commitment?
• SQEs regularly attend 1-hour meetings with the
  Software Assurance Lead to discuss the CMMI
  initiative and approach
• 1st SQ Training Module detailing the SQ
  Program/approach was conducted on April 6, 2004
• All SQEs have developed draft SQA Plans (using a
  standard template)
• SQ Schedules have been developed to coordinate
  process and product assessments for all projects
• To date, new SQ requirements have been met as
  part of OJT

Going forward, SQEs will be required to broaden
their assessment scope for in-house software
efforts!!
10
NASA Software Assurance (SA) Requirements
NASA HQ with the help of the Software Working
Group is in the process of revising all standards
and guidebooks that relate to software. Both the
Software Assurance and Software Safety Standards
are in final review. The Software Safety
Guidebook has been released and the Software
Assurance Guidebook is scheduled for updates in
FY05.

• SA Standard NASA-STD-8739.8 Draft 03/26/04
• SA Guidebook TBD
• Software Safety Standard NASA-STD-8719.13
• Software Safety Guidebook NASA-GB-8719.13
• NASA Software Engineering Requirements
  NPR-7150.x Draft 6/4/04

11
OSSMA Software Quality Program

• Software Quality Pyramid
• Software Quality Process Map
• Software Assurance Web Site

12
OSSMA Code 300Software Quality ProgramPyramid
OSSMAs SQ Program is based on updated NASA
Standards and Policies and documented using the
GDMS and GSFC Software Assurance Web Site
13
Process Map for Software Quality Program

• SQ Schedule- Approved SQA Plan- Assessment
  Plan (optional)

- Assessment Report- Reporting Form- Status
Weekly/Mthly/Qtrly
- Completed Checklist- Findings/Observations/Risk
s
Outputs
Write Assessment Reports
Repository and Records
SQ Start
Develop SQA Plan
ConductAssessments

• MAR/SOW- Surveillance Plan-303-WI-7120.2.3 -
  SQAP Template- Project Docs

• Work Instructions- Checklists -
  Product/Process Items- Standards

• Report Template- Findings- Observations -
  Risks- Recommendations

- Findings repository - Assessment Rpt-
Checklists- Reporting Form
Inputs
14
SW-Assurance Web Site

• The Software Assurance web site was developed as
  a tool for Practitioners (i.e., software
  assurance personnel)  http//sw-assurance.gsfc.nas
  a.gov
• This site has been designed to be a one stop
  resource that provides the latest tools or assets
  required to perform software assurance activities
  and tasks
• The site is currently available to NASA GSFC only
  -- with plans to open it up to all NASA centers
  after all of the disciplines (quality,
  reliability, safety, VV, and IVV) are populated
  Target date of 08/09/04
• Use the sites Feedback Form to provide comments
  or recommendations

15
SEI CMMI
What does the model look like?

• CMMI PPQA Specific Goals and Practices
• CMMI Generic Goals and Practices
• Mapping SQ Program to CMMI PPQA

16
CMMI PPQA Specific Goals and Practices
Purpose Provide staff and management
with objective insight into the processes and
work products

• SG 1 Objectively Evaluate Processes and Work
  Products
• SP 1.1-1 Objective Evaluate Processes
• SP 1.2-1 Objectively Evaluate Work Products and
  Services
• SG 2 Provide Objective Insight
• SP 2.1-1 Communicate and Ensure Resolution of
  Noncompliance Issues
• SP 2.2-1 Establish Records

17
CMMI Generic Goals and Practices

• GG 1 Achieve Specific Goals
• GP 1.1 Perform Base Practices
• GG 2 Institutionalize a Manage Process
• GP 2.1 Establish an Organizational Policy
• GP 2.2 Plan the Process
• GP 2.3 Provide Resources
• GP 2.4 Assign Responsibility
• GP 2.5 Train the people performing or supporting
  the process
• GP 2.6 Manage Configuration
• GP 2.7 Identify and Involve Relevant Stakeholders
• GP 2.8 Monitor and Control the Process
• GP 2.9 Objectively Evaluate Adherence
• GP 2.10 Review Status with Higher Level
  Management
• GG 3 Institutionalize a Defined Process
• GP 3.1 Establish a Defined Process
• GP 3.2 Collect Improvement Information

18
Mapping SQ Program to PPQA
19
Mapping SQ Program to PPQA
20
SAMs Role

• Read and understand the new NASA requirements
• Read and understand the Software Quality PG
  requirements
• 303-PG-7120.2.1, Procedure for Developing and
  Implementing Software Quality Programs (GDMS)
• Know what records will be maintained and what
  metrics will be collected
• 303-WI-7120.2.3, Software Quality Assessment
  Process (GDMS)
• 303-WI-7120.2.2, Software Quality Reporting
  Process (GDMS)
• 303-FRM1_RPT, Software Quality Reporting Form
  (Web Site)
• Update Service Orders to reflect new software
  quality requirements
• Know what deliverables to expect!

21
SAMs Role (cont.)

• Baseline and Release SQA Plans
• Use the SQA Plans and schedules to gauge the
  necessary resources required to provide SQ
  support
• Understand how SQ personnel add value to projects
• Reference the Software Quality Activity Matrix
  (Web Site)
• Review Work instructions and Checklists (Web
  Site)
• Complete Software Assurance (quality,
  reliability, safety, VV, and IVV) training
• Report Software Quality issues to Code 300 Senior
  Management, as well as the Software Assurance
  Lead
• Be a Champion for Software Assurance and Software
  Quality!!

22
Summary

• NASAs CMMI Initiative will increase the
  visibility of Software Assurance across GSFC and
  our software providers
• The timeliness of this initiative will help to
  strengthen our Software Quality Program and our
  value to Center projects
• The new Software Quality Approach meets the goals
  of CMMI, while providing consistent SQ support to
  current and future projects
• SQEs are committed to your projects and
  enthusiastic about the improvements to our
  Software Quality Program

23
Backup
Contact Information Susan Sekira
Software Assurance Lead x 6160 Saul Harris
Software Quality Engineer x 7379 Sandra
Toalston MASC Software Quality Engineer x
0096
24
Additional Training Modules

• Available on web site
• http//sw-assurance.gsfc.nasa.gov

25
Module 1 SQ Processes, Reporting, and Records
Overview

• Quality Processes and Process Map
• Assessment Reporting
• Records
• Work Product Tools
• Software Assurance Web Site

available now on http//sw-assurance.gsfc.nasa.go
v
26
Module 3 Preview CMMI - Process and Product QA
for SQ Personnel

• SEI CMMI Model and GSFC Initiative
• PPQA Process Area (GG, GP, SP, SG)
• Mapping SQ processes and records to PPQA
• Goals for PPQA pre-assessment 4Q 2004
• Role of SQ Personnel in PPQA

coming soon to http//sw-assurance.gsfc.nasa.gov
27
Acronym List

• CMMI Capability Maturity Model Integration
• GDMS Goddard Directives Management System
• GG Generic Goals
• GP Generic Practices by Goal
• IEEE Institute of Electrical and Electronic
  Engineers
• IVV Independent Verification and Validation
• OSSMA Office of Systems Safety and Mission
  Assurance
• PPQA Process and Product Quality Assurance
• SEI Software Engineering Institute
• SG Specific Goals
• SP Specific Practices by Goal
• SQA Software Quality Assurance
• SQ Software Quality
• SW - Software
• VV Verification and Validation