ARINC 652 : 1993

1.0 INTRODUCTION
1.1 Purpose of this Document
1.2 Background
1.3 Airline Objectives
1.4 ARINC 652 Overview
1.5 Relationship to Other Documents
1.6 Use of 'Specification Language'
1.7 Other Considerations
2.0 SOFTWARE COST DRIVERS
2.1 Overview of Costs Drivers
2.2 Airline Related Costs
2.3 Equipment Supplier-Development Costs
2.4 Aircraft Integrator Costs
2.5 Cost Distribution
3.0 SOFTWARE MANAGEMENT
3.1 The Software Development Process
3.2 Enhancements of Models for Field Performance
3.3 The User and Supplier Relationship
3.4 Managing Software Development
3.5 Software Documentation
3.6 Managing User-Modifiable Software
3.7 Software Security
4.0 SOFTWARE DEVELOPMENT
4.1 Software Development Environment
4.2 Considerations for Software Design
4.3 Customer/Supplier Relationships
4.4 Software Certification
5.0 USER-MODIFIABLE SOFTWARE
5.1 User-Modifiable Software Goals
5.2 Software Modification Environment
5.3 Managing User-Modifiable Software
5.4 Configuration Management
6.0 POST-CERTIFICATION SOFTWARE CHANGES
6.1 Introduction
6.2 Software Maintenance Process
6.3 Re-Certification of Modified Systems
6.4 Approach to Certification
6.5 Change Within Limits
6.6 Change Process
ATTACHMENTS
1 Glossary
1 Acronyms and Abbreviations
2 System Life Cycle
3 System/Software Development Process
APPENDICES
A Reference Documents
B Software Life Cycle Models
FIGURES
B-1 An Example of System Development Reviews and
              Audits
B-2 Detailed Waterfall Representation
B-3 Software Development and Verification Activities
B-4 Starts V-Diagram
B-5 The Two-Leg Process Model
B-6 Incremental Development
B-7 Domain Dependent Software Life Cycle
B-8 Third Generation
B-9 System Development Life Cycle
B-10 Spiral Model of the Software Process
B-11 New Model
B-12 Object-Oriented Model

Provides guidance for the design and development of avionics software for traditional ARINC 700-series equipment and IMA.