SAE AIR 6110-2011 Contiguous Aircraft System Development Process Example《连续飞机 系统开发程序范例》.pdf
《SAE AIR 6110-2011 Contiguous Aircraft System Development Process Example《连续飞机 系统开发程序范例》.pdf》由会员分享,可在线阅读,更多相关《SAE AIR 6110-2011 Contiguous Aircraft System Development Process Example《连续飞机 系统开发程序范例》.pdf(107页珍藏版)》请在麦多课文档分享上搜索。
1、_ SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising there
2、from, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your written comments and suggestions. Copyright 2011 SAE International All rights reserved. No part of this p
3、ublication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-497
4、0 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org/technical/standards/AIR6110 AEROSPACE INFORMATION REPORT AIR6110 Issued 2011-12 Contiguous Aircraft/S
5、ystem Development Process Example RATIONALE This document provides additional supporting material for the implementation of the processes described in ARP4754A/ED-79A. FORWARD ARP4754A/ED-79A contains information which places the information in this AIR in context. This AIR should be used in conjunc
6、tion with the main body and the appendices of ARP4754A/ED-79A. In addition, this example shows the interrelationships with ARP4761. 1. INTRODUCTION 1.1 Scope This AIR provides a detailed example of the aircraft and systems development for a function of a hypothetical S18 aircraft. In order to presen
7、t a clear picture, an aircraft function was broken down into a single system. A function was chosen which had sufficient complexity to allow use of all the methodologies, yet was simple enough to present a clear picture of the flow through the process. This function/system was analyzed using the met
8、hods and tools described in ARP4754A/ED-79A. The aircraft level function is “Decelerate Aircraft On Ground” and the system is the braking system. The interaction of the braking system functions with the aircraft are identified with the relative importance based on implied aircraft interactions and s
9、ystem availabilities at the aircraft level. This example does not include validation and verification of the aircraft level hazards and interactions with the braking system. However, the principles used at the braking system level can be applied at the higher aircraft level. The methodologies applie
10、d here are an example of one way to utilize the principles defined in ARP4754A/ED-79A. The function chosen was the braking system. Other formats may be used to accomplish the documentation, so long as the principles outlined in ARP4754A/ED-79A are followed. This example contains references to docume
11、ntation that a company may use to assure itself of the safety of its products but does not include the documentation that the Original Equipment Manufacturer (OEM) would be required to submit at the aircraft level for aircraft certification. Some of these documents are submitted to the regulatory ag
12、encies for the purpose of certification (e.g. the Wheel Brake System FHA). Other documents are internal to the company and not required to be submitted for certification. No implication is made that these documents should be submitted to a regulatory agency and none should be implied, although all d
13、ocuments should be available for submission if requested by the regulatory agency. Safety and Certification are not synonymous terms. The example shows the systems engineering process as applied to the development of an aircraft, including some processes that are beyond certification requirements. F
14、igure 1 depicts the flow of activities within this example. This figure provides a guide to the structure of this AIR and should allow the reader to quickly find specific areas within the example using the cross references. SAE AIR6110 Page 2 of 107 Figure 1 includes the top aircraft level tasks to
15、provide the reader a reference point. The detailed example in Section 3 of this AIR covers only the activities related to the braking system. Figure 1 presents a sequence of activities found in a typical development program. In a real development program, the development process is usually far more
16、complex. For example, in a real development program, development of the different levels (aircraft, system and item) often occurs concurrently, rather than serially as depicted in example flow. The top row of Figure 1 represents the activities that will occur within the aircraft development. The mid
17、dle row represents the activities that occur within the wheel brake system development. The bottom row represents the activities that are covered for the subsystem-level Brake System Control Unit (BSCU) development, as well as the integration and verification activities at the higher levels. The Fig
18、ure 1 example flow also shows where major artifacts from the System Safety Process (ARP4761) will be utilized. The example flow shows how the sections and artifacts are laid out and represents the step by step process detailed in ARP4754A/ED-79A. In a real development program, the System Safety Proc
19、ess occurs concurrently with ARP4754A/ED-79A, constantly receiving inputs from the ARP4754A/ED-79A process and providing feedback to ARP4754A/ED-79A processes. Figure 1 also shows a box titled Integral Processes to illustrate to the reader that the integral processes are utilized throughout the deve
20、lopment process. The reader is encouraged to use this example flow diagram to help navigate the example. This will allow the reader to either read the example in its entirety or use it as a quick reference guide in order to quickly find the desired section. 1.2 Document Format This AIR contains the
21、following sections and appendices: Section 1 is an introduction to the document, giving the scope, format, references to other documents, an acronym list, and a description of the example aircraft function being developed. Section 2 describes the overall example aircraft development process, focusin
22、g on activities leading to the development of the braking system. The hypothetical aircraft in this example is introduced and its basic requirements are given. Aircraft-level planning documents are identified. Top-level aircraft functions are decomposed to determine the functions required of the bra
23、king system. The aircraft level safety assessment process, including the aircraft FHA and the Preliminary Aircraft Safety Assessment (PASA), is conducted. The PASA assigns development assurance levels to aircraft functions. These functions are allocated to the braking system as part of the overall a
24、ircraft architecture. Aircraft requirements relevant to the braking system are validated. The braking system is integrated and validated with the other systems on the aircraft. (Note: PASA is introduced in ARP4754A/ED-79A, but detailed guidance for completing it awaits the release of ARP4761A. This
- 1.请仔细阅读文档,确保文档完整性,对于不预览、不比对内容而直接下载带来的问题本站不予受理。
- 2.下载的文档,不会出现我们的网址水印。
- 3、该文档所得收入(下载+内容+预览)归上传者、原创作者;如果您是本文档原作者,请点此认领!既往收益都归您。
下载文档到电脑,查找使用更方便
10000 积分 0人已下载
下载 | 加入VIP,交流精品资源 |
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- SAEAIR61102011CONTIGUOUSAIRCRAFTSYSTEMDEVELOPMENTPROCESSEXAMPLE 连续 飞机 系统 开发 程序 范例 PDF

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