SAE JA 1005 : 2012

SOFTWARE SUPPORTABILITY PROGRAM IMPLEMENTATION GUIDE

SAE International

More details

More info

1 Scope
  1.1 Purpose
  1.2 Audience
  1.3 Applications
2 References
  2.1 Applicable Publications
3 Definitions
4 Overview of Software Supportability Program
  4.1 The Importance of Planning
  4.2 Determining Support Requirements Through Analysis
  4.3 Outputs of Supportability Analysis
5 Supportability Program Life Cycle Management
  5.1 Concept and Feasibility Analysis
  5.2 Design and Production
  5.3 In-Service
  5.4 Tailoring Supportability Life Cycle Management
  5.5 Relationship of Software Supportability Program to
      Existing Standards
6 Supportability Analysis - Methods and Techniques
  6.1 Use Study
  6.2 Software Identification and Breakdown
  6.3 Categorization and Selection of Software Support
      Significant Items
  6.4 Support Scenario Modeling
  6.5 Block Release Profile Modeling
  6.6 Life Cycle Costs and Trade-offs
  6.7 Design for Supportability
  6.8 Supportability Assessment
  6.9 Interdiscipline Methods and Techniques
7 Notes
  7.1 Marginal Indicia
Appendix A Glossary of Acronyms and Terms
  A.1 Acronyms
  A.2 Key Terms
Appendix B Software Supportability Plan and Case Templates
  B.1 Example Software Supportability Plan Template
  B.2 Example Software Supportability Case Template
Appendix C Software Logistics Support Activity Tasks
  C.1 Program Planning and Control
  C.2 Mission, Development, and Support Systems Definition
  C.3 Preparation and Evaluation of Alternatives
  C.4 Determination of Software Support Requirements
  C.5 Software Supportability Assessment
  C.6 In-Service Software Supportability
Appendix D Software Support Scenario Examples
  D.1 Example Operator Problem Reporting Support Scenario
  D.2 Example Problem/Change Request Resolution Scenario
Appendix E Off-the-Shelf Software Support Guidance
  E.1 OTS Software Support Concerns and Benefits
  E.2 Through-Life Support Strategy and Guidance
LIST OF ILLUSTRATIONS
Figures

Abstract

Intended to be guidance for business purposes and should be applied when it provides a value-added basis for the business aspects of development, use, and sustainment of support-critical software.