ARINC 627-2 : 2002

1.0 Introduction
1.1 Purpose of this Document
1.2 Background
1.3 Goals of ARINC 626 ATLAS
1.4 ARINC Report 627 Overview
1.5 Relationship Between ATLAS Test Specification and ATLAS
     Test Program
1.6 Related Documents
2.0 ATLAS TEST PROGRAM STRUCTURE
2.1 Introduction
2.2 The Benefits of a Standard Test Program Structure
2.3 The TPS Template
3.0 GOOD PROGRAMMING PRACTICES
3.1 Introduction
3.2 Test Objectives
3.3 Preparation for ATLAS Test Program Development
3.4 Use of Virtual Resources
3.5 Proper Test Sequence
3.6 Test Program Maintainability
3.7 Complete and Partial Testing
3.8 Diagnostics
3.9 Programming Methodology
4.0 OPERATOR INTERFACE
4.1 Introduction
4.2 Operator Skill Level
4.3 Operator Directive Messages
4.4 PASS/FAIL Messages
4.5 Use of INPUT/OUTPUT Statements
4.6 Long Test Execution Time
4.7 Consistency
4.8 Standardized Test Reports
4.9 Use of Graphics Within SMART
5.0 GUIDANCE FOR USING SELECTED ARINC 626 CONSTRUCTS
5.1 Use of EXTEND ATLAS Noun
5.2 Manometrics and Fluid Signals
5.3 Digital Testing
5.4 Bus Testing
5.5 Use of NON-ATLAS Modules in Digital Testing
5.6 The DEFINE DRAWING Statement
5.7 Implementation of Decimal and Integer
5.8 Implementation Differences Between ARINC 626 and SMART
6.0 DOCUMENTATION
6.1 Introduction
6.2 CMM Documentation
6.3 ATE Documentation
6.4 TPS Documentation
7.0 TUA AND TUA DIRECTIVE FILES
7.1 Relationship Between ATLAS And Test Unit Adapter
7.2 Relationship Between ATLAS And TUA Directive File
7.3 Directive File
7.4 Relationship Between TUA Directive File and Other
     SMART System Models
7.5 SMART TUA Directive File Limitations
7.6 TUA Directive File Description
7.7 Test Unit Adapter Development
Appendices