ARINC 652-1993 Guidance for Avionics Software Management《航空电子设备管理指南》.pdf
《ARINC 652-1993 Guidance for Avionics Software Management《航空电子设备管理指南》.pdf》由会员分享,可在线阅读,更多相关《ARINC 652-1993 Guidance for Avionics Software Management《航空电子设备管理指南》.pdf(73页珍藏版)》请在麦多课文档分享上搜索。
1、 GUIDANCE FORAVIONICS SOFTWARE MANAGEMENTARINC REPORT 652PUBLISHED: JANUARY 15, 1993AN DOCUMENTPrepared byAIRLINES ELECTRONIC ENGINEERING COMMITTEEPublished byAERONAUTICAL RADIO, INC.2551 RIVA ROAD, ANNAPOLIS, MARYLAND 21401Copyright 1993 byAERONAUTICAL RADIO, INC.2551 Riva RoadAnnapolis, Maryland 2
2、1401-7465 USAARINC REPORT 652GUIDANCE FOR AVIONICS SOFTWARE MANAGEMENTPublished: January 15, 1993Prepared by the Airlines Electronic Engineering CommitteeReport 652 Adopted by the Airlines Electronic Engineering Committee: November 5, 1992Report 652 Adopted by the Industry: January 15, 1993REPORT 65
3、2TABLE OF CONTENTSITEM SUBJECT PAGE1.0 INTRODUCTION 11.1 Purpose of this Document 11.2 Background 11.3 Airline Objectives 11.4 ARINC 652 Overview 11.5 Relationship to Other Documents 11.5.1 Relationship to RTCA DO-178B/EUROCAE ED-12B 21.5.2 Relationship to ARINC Report 651 21.6 Use of “Specification
4、 Language“ 21.7 Other Considerations 22.0 SOFTWARE COST DRIVERS 32.1 Overview of Costs Drivers 32.2 Airline Related Costs 32.2.1 Operational Costs Due to Low MTBF/MTBR 32.2.2 Post Delivery Changes 32.2.3 Modification Due to Lack of Hardware 32.2.4 Selection Of Customer Options 32.2.5 Tolerant Design
5、 42.2.6 Post Delivery Support-Customer Relationship 42.2.7 Cost of Configurable Software 42.2.8 Cost of Interfacing to Flight Simulators 42.3 Equipment Supplier-Development Costs 42.3.1 Project Management 42.3.1.1 Development Schedules 42.3.1.2 Stability of Requirements 42.3.1.3 Customer/Supplier Re
6、lationship 42.3.2 Product Related Factors 42.3.2.1 Complexity and Size 42.3.2.2 Target Hardware Design 42.3.2.3 Memory and Throughput Constraints 52.3.2.4 Re-Use of Existing Software 52.3.2.5 Use of Commercial Off-The-Shelf (COTS) Software 52.3.2.6 Software Criticality Level 52.3.3 Use of Developmen
7、t Tools 52.3.3.1 Requirement, Analysis and Design 52.3.3.2 Verification 52.3.3.3 Documentation Tools 62.3.3.4 Software Configuration Management 62.3.3.5 Host Computers 62.3.3.6 Software Test and Integration Facility 62.3.3.7 Introduction of Tools 62.3.3.8 Tool Qualification 62.3.4 Personnel Factors
8、62.3.4.1 Staff Capability 62.3.4.2 Multi-Site Development 72.3.4.3 Staff Continuity 62.3.4.4 Use of Sub-Contract Engineers 72.4 Aircraft Integrator Costs 72.4.1 Functional Specification Elaboration 72.4.2 Supplier Monitoring 72.4.2.1 Project Management 72.4.2.2 Software Quality Assurance 72.4.3 Syst
9、em Integration Costs 72.4.3.1 Ground Tests 82.4.3.2 Flight Tests 82.4.4 Certification Process 82.5 Cost Distribution 83.0 SOFTWARE MANAGEMENT 93.1 The Software Development Process 93.1.1 Integral Processes 93.1.1.1 Software Management Process 93.1.1.2 Certification Liaison 9iiiREPORT 652TABLE OF CON
10、TENTSITEM SUBJECT PAGE3.1.1.3 Software Quality Assurance Process 103.1.1.4 Software Configuration Management Process 103.1.1.5 Software Verification Process 113.1.2 Term Processes 113.1.2.1 System Definition Process 113.1.2.2 Software Planning Process 113.1.2.3 Software Requirements Process 113.1.2.
11、4 Software Design Process 123.1.2.5 Code Process 123.1.2.6 Combined Integration Proccess 133.1.2.6.1 Software Integration 133.1.2.6.2 Hardware/Software Integration 133.1.3 Post Development Software Related Activities 133.2 Enhancements of Models for Field Performance 133.3 The User and Supplier Rela
12、tionship 143.4 Managing Software Development 143.4.1 Software Design Tradeoffs 153.4.2 Relationship between Complexity and Cost 153.4.3 Value of Software Development Tools 153.4.4 Software Personnel 153.4.5 Schedule 153.4.6 Managing Small Projects 163.4.6.1 Architecture Tradeoffs 163.4.6.2 Reviews a
13、nd Assurances 163.4.6.3 Testing 173.5 Software Documentation 173.6 Managing User-Modifiable Software 183.6.1 Management Goals 183.6.2 Availability of Tools 183.6.3 Integrity of the Changed Software 183.6.4 User Training 183.7 Software Security 193.7.1 Computer Security 193.7.1.1 Vulnerabilities 193.
14、7.1.2 Causes of Preventable Losses 193.7.1.3 Frequency and Cost of Losses 203.7.1.4 Defense Mechanisms 203.7.1.5 Government Security Standards 203.7.2 Methodology 203.7.2.1 Threat Assessment 203.7.2.2 External Threats 203.7.3 Dealing with External Threats 203.7.3.1 Software Protection 203.7.3.2 Data
15、 Protection 203.7.3.3 Other Protection 213.7.3.4 Computer Virus Defense Mechanisms 213.7.4 Software Security Recommendations 213.7.4.1 Unauthorized Access 213.7.4.2 Input Tape Tampering 213.7.4.3 Software Security Verification at Run-Time 213.7.4.4 Recovery Provisions 213.7.4.5 Security Management 2
16、13.7.4.5.1 Never-Alone Principle 213.7.4.5.2 Limited-Tenure Principle 213.7.4.5.3 Separation-of-Duties Principle 213.7.4.6 Detection and Surveillance 223.7.5 Fault Tolerance and Security 223.7.5.1 Fault Tolerance Techniques 224.0 SOFTWARE DEVELOPMENT 234.1 Software Development Environment 234.2 Cons
17、iderations for Software Design 234.2.1 General Considerations 234.2.1.1 Use of Ada High-Order Language 23ivREPORT 652TABLE OF CONTENTSITEM SUBJECT PAGE4.2.1.2 Modularity 244.2.1.3 Consistency of Design 244.2.1.4 Design for Software Criticality Level 244.2.1.5 Throughput 244.2.1.6 Memory Size 244.2.1
18、.7 Documentation 244.2.1.8 Verification Considerations 244.2.1.9 Expandability for Future Applications 244.2.2 Special Considerations 254.2.2.1 Partitioning for Convenience 254.2.2.2 Partitioning for Criticality 254.2.3 Design for Change 254.2.4 Design for Re-Use 254.2.5 Design for Portability 264.2
19、.5.1 Why Transport Software? 274.2.6 Design for Robustness 274.2.6.1 Defensive Programming 274.2.6.2 Design of Built-In Test (BIT) Software 274.2.7 Design for Compatibility with Flight Simulator 274.3 Customer/Supplier Relationships 284.3.1 Life Cycle Model 284.3.2 Customer Participation in Defining
20、 Requirements 284.3.3 Schedule Implications 284.4 Software Certification 285.0 USER-MODIFIABLE SOFTWARE 305.1 User-Modifiable Software Goals 305.2 Software Modification Environment 305.2.1 Change Within Limits 305.2.2 Configuration Control 305.2.3 Documentation 305.2.4 Other Considerations 305.2.5 E
21、xample of User-Modifiable Software 305.2.5.1 Characteristics of this Example 315.2.5.2 Tool Related Issues 325.3 Managing User-Modifiable Software 325.3.1 Selection of Preprogrammed Options 325.3.1.1 Responsibility 325.3.1.2 Tools 325.3.1.3 Training 325.3.1.4 User Requirements 325.3.1.5 Installation
22、 on Aircraft 325.3.1.6 Cost Impact 325.3.1.7 Password Protection 325.3.2 Tables, Configurable via Resident Table Manager 325.3.2.1 Responsibility 325.3.2.2 Tools 325.3.2.3 Training 325.3.2.4 User Requirements 325.3.2.5 Documentation 325.3.2.6 Problem Reports 335.3.2.7 Relation to Ground Based System
23、s 335.3.2.8 Software Labeling 335.3.2.9 Configuration Control and Verification 335.3.2.10 Installation on Aircraft 335.3.2.11 Cost Impact 335.3.2.12 Password Protection 335.3.3 Tables, Configurable via Ground Support Equipment 335.3.3.1 Responsibility 335.3.3.2 Tools 335.3.3.3 Training 335.3.3.4 Use
24、r Requirements 335.3.3.5 Documentation 335.3.3.6 Problem Reports 33vREPORT 652TABLE OF CONTENTSITEM SUBJECT PAGE5.3.3.7 Interfaces with Ground Based Systems 335.3.3.8 Software Labeling 335.3.3.9 Evaluation on Aircraft 335.3.3.10 Installation on Aircraft 335.3.3.11 Software Installation Procedure 335
- 1.请仔细阅读文档,确保文档完整性,对于不预览、不比对内容而直接下载带来的问题本站不予受理。
- 2.下载的文档,不会出现我们的网址水印。
- 3、该文档所得收入(下载+内容+预览)归上传者、原创作者;如果您是本文档原作者,请点此认领!既往收益都归您。
下载文档到电脑,查找使用更方便
10000 积分 0人已下载
下载 | 加入VIP,交流精品资源 |
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- ARINC6521993GUIDANCEFORAVIONICSSOFTWAREMANAGEMENT 航空 电子 设备管理 指南 PDF

链接地址:http://www.mydoc123.com/p-429518.html