MBSE在航空飞行控制系统的应用研究

现代飞机系统的复杂性不断增长,传统的开发方法在管理和维护方面变得越来越具有挑战性。首先,对航空飞控系统研发过程在当前系统工程实践方面进行了评估,阐述了传统开发方式的不足和基于模型的系统工程（MBSE）的核心原则和优点,以及在实现中常用的工具和方法;然后,展示了MBSE如何在飞行控制系统研发时使用模型来支持复杂系统的规范、设计、分析、验证和确认的过程;最后,结合先进的MBSE工具和方法的发展,MBSE结合敏捷的开发前景,以及提高MBSE实践的互操作性和标准化的需求对未来的研究方向进行了展望。本文研究为利用MBSE方法论和工具来改进飞行控制系统的设计、开发和性能感兴趣的航空工业专业人员、系统工程师提供资源和解决思路。     

What is systems engineering?

There are probably more definitions of “Systems Engineering” than there are AESS members. In its simplest form systems engineering is the design of the whole as opposed to the design of the parts. The vast number, complexity and diversity of elements can overwhelm and degrade system performance and reliability. Embedded processing and software can be both a boon and a bane. A systems engineer analyzes and optimizes an ensemble of elements that relate to the flow of energy, mass and communications into a design that performs the desired function. “Systems engineering” is used herein to cover a very broad spectrum of processes and controls to engineer a product at the many levels required to satisfy all aspects of the original requirement. Our definition is not intended to either include or exclude systems engineering and integration as used in the computer field. In any case, systems engineering is the application of solid engineering principles to design and develop a large enterprise within cost and schedule to satisfy the needs of the ultimate user. It involves conceptualization, design, development, test, implementation, approval/certification and operation (including human factors) of a system. In essence, systems engineering is a problem-solving discipline for the modern world     

Lessons learned using software-assisted systems engineering on large satellite development contracts

Over the years, the world's defense industries have become quite proficient at developing large, complex hardware and software systems. In recent years, the ubiquitous deployment of personal computers has changed the way we work. Additionally, took designed to facilitate systems engineering have recently matured enough to start having a major impact on many major systems development efforts. Finally, the government's faster-better-cheaper acquisition philosophy has started driving prime contractors to a concurrent engineering approach toward systems engineering. This confluence of experts is has had unexpected impacts on both the flexibility and rigor of requirements management processes. While the maturing requirements and design took hold great promise in maintaining requirements traceability throughout the design process, the widespread use of desktop computing systems has inadvertently lulled many experienced systems engineers into sloppy processes because it now appears to be a simple matter to make a requirements change in a softcopy of a requirements document. Without strong process and management support, requirements changes inevitably start being derived in a broad spectrum of incompatible took and formats. This author is currently participating in the design phase of a major classified government satellite development effort. As an integral member of an extremely experienced requirements management team (boasting over 150 years of combined experience in the defense industry), this author has had the opportunity to watch the team navigate straight into many of the systems engineering potholes created when talented engineers implement concurrent engineering using a variety of tools without a consistent process framework. This paper, therefore, specifically addresses process and implementation challenges that arose when establishing a software-assisted concurrent-engineering approach on a large satellite development contract.     

Spacecraft engineering and research at Saint Louis University

Parks College of Engineering and Aviation of Saint Louis University [1i] has a tradition of offering an outstanding aerospace engineering education to prepare students at the undergraduate and graduate level for careers in commercial aviation, defense systems, and space systems fields. Courses are offered across the engineering spectrum (aerospace, electrical and computer engineering, and physics departments) ranging from an introduction to aerospace engineering to spacecraft design, spacecraft communications, and space physics. Students participate in courses that include orbital mechanics, space dynamics, spacecraft engineering, and space systems. Senior capstone project work is also included. A separate Astronautics Engineering track as well as a Minor in Space Systems Engineering for non-aerospace engineering students is currently being developed. A, number of student-driven space systems projects are in process that involve design, development, and test of small satellites similar to those recently highlighted in the March 2009 Systems article entitled The First one Hundred University-Class Spacecraft 1981 - 2008. Reference [4] identifies student spacecraft launched over the past 27 years.     

The aerodynamic design of multi-element high-lift systems for transport airplanes

High-lift systems have a major influence on the sizing, economics, and safety of most transport airplane configurations. The combination of complexity in flow physics, geometry, and system support and actuation has historically led to a lengthy and experiment intensive development process. However, during the recent past engineering design has changed significantly as a result of rapid developments in computational hardware and software. In aerodynamic design, computational methods are slowly superseding empirical methods and design engineers are spending more and more time applying computational tools instead of conducting physical experiments to design and analyze aircraft including their high-lift systems. The purpose of this paper is to review recent developments in aerodynamic design and analysis methods for multi-element high-lift systems on transport airplanes. Attention is also paid to the associated mechanical and cost problems since a multi-element high-lift system must be as simple and economical as possible while meeting the required aerodynamic performance levels.     

可靠性系统工程的理论与技术框架

简要回顾了可靠性系统工程的形成过程,以产品故障为核心,阐述了可靠性系统工程的概念与定义,把认识产品故障发生规律和故障表现规律作为可靠性系统工程基础理论,把故障预防技术、故障控制技术和故障修复技术作为可靠性系统工程的基础技术,把基础技术的集成作为可靠性系统工程的应用技术,从而初步建立了可靠性系统工程的理论与技术框架,细化了可靠性系统工程的学科内涵。可靠性系统工程作为初现的新学科,虽然尚未达到严格定义与清晰表达的完善状态,但是我们完全有信心期待其作为一种新的方法论,帮助工程设计人员更好地完成工程系统的设计。     

Air traffic management design considerations

An air traffic management system (ATMS) is a network-centric system being used to manage another network-centric system, namely, an air transportation system. We are developing a design language for network-centric systems and design guidelines for the development system of engineers and domain specialists involved in designing and integrating systems. Note: this development system with today's technology is also a network-centric system. An outline of the design language under construction and the design guidelines being studied is provided. Specifically we discuss ATMS mission objectives (e.g., average yearly throughput of people and freight for a high demand scenario); ATMS sample usage scenarios (e.g., ATMS reroutes air traffic in time and space in reaction to major weather deviation along the northeast coast); and system objectives for an ATMS (e.g., timelines of a specific high volume of messages from aircraft, weather sensors, and airports). We lay out some key design decisions associated with both the development system of engineers and domain specialists and the operational ATMS. Examples of key design decisions for the engineering system are: 1) appropriate partitioning of functional/physical architectures of the engineering system; 2) appropriate degree to telecollaboration and collaboration among design/integration groups; 3) appropriate incremental delivery packages for an incremental delivery schedule of ATMS elements; and 4) appropriate levels and thrusts of the risk management program. Examples of key design decisions for the operational ATMS are: 1) throughput and security trades of the ATMS and 2) throughput and resiliency to weather changes. Finally, we relate network-centric architecture issues to both of the above sets of design decisions.     

基于MBSE的副翼及其操纵系统研发技术及应用

飞机的设计研发是一项涉及多学科领域、多目标、多约束的复杂系统工程过程,系统耦合紧密、参与人员众多、设计信息庞杂,以文档为中心的需求管理等传统研发方法突显出一定的困难,亟需探索新的飞机设计研发方法。以副翼及其操纵系统为研究对象,对基于模型的系统工程(Model Based System Engineering,以下简称MBSE)方法进行了探索研究:采用达索MBSE方法论-MMS(Modeling Methodology for Systems,以下简称MMS),从使命、服务、功能和组件不同视角对副翼及其操纵系统研发的各个方面进行解析,进而完整定义系统;利用达索3D Experience平台,通过RFLP系统工程架构,进行了副翼及其操纵系统的需求开发、功能分析及逻辑架构设计,完成了需求、功能、逻辑架构、系统仿真、物理设计等模型的关联追溯,实现了以达索MBSE方法论为核心的研发技术的有效应用。     

基于模型的航空电子系统体系化需求分析与仿真

借鉴体系工程思想及体系结构设计方法,结合航空武器装备需求论证实践,提出基于模型的航空电子系统体系化需求分析与仿真方法,以及体系架构模型协同仿真环境设计方案,能够有效支撑航空电子体系化需求论证和顶层设计,具有重要的理论价值和实践意义。     

Definitions of Effectiveness Terms: A Report on the Purpose and Contents of MIL-STD-721B

The impact of the Systems Effectiveness concept upon U.S. military terminology required for acquisition of modern weapon systems necessitated a thorough revision of MIL-STD-721A and consolidation with MIL-STD-778 and MIL-STD447. Inclusion of a number of new terms and their definitions, as well as addition of standard definitions for terms on human factors and safety, was found to be necessary. The resulting military standard has been approved by the U.S. Department of Defense for use by all of its departments and agencies. Its contents should be of great interest to management and engineers in private industry who are concerned with the development and production of weapon systems for the Army, Navy, and Air Force. This standard is now in print and will be available for distribution early in 1967; this paper is written by one of the participants in the revision and compilation of this military standard and is published here for the purpose of information on its scope and contents.     

Security Systems Research and Testing Laboratory at Edith Cowan University

The testing and evaluation of sophisticated security systems has remained in the domain of governments in national facilities and the commercial security industry through manufacturers and engineering consultants. As well, the production of testing protocols and industry standards has been developed by national organisations, professional security, and engineering bodies in the appropriate security fields. The Security Systems Research and Testing Laboratory in the School of Engineering and Mathematics at Edith Cowan University (ECU), Perth, Western Australia has commenced operations in research, testing, and evaluation of security systems. This paper wir describe the first year of operation of the Security Systems Research and Testing Laboratory, and will describe the role that testing and evaluation of security systems plays in the education and training of Security Science graduates, as well as the benefits that the Laboratory brings to the security industry through its testing programme.     

飞行器体系优化设计问题

针对传统的飞行器设计与体系（SOS）设计相互独立造成的飞行器实际作战效能不足的问题,对同时考虑飞行器与体系耦合设计的飞行器体系优化设计问题展开研究。首先,根据体系工程（SOSE）原理给出了耦合飞行器设计与体系结构设计的飞行器体系优化设计问题的基本概念与通用数学定义;其次,基于多层体系架构,构建了飞行器体系设计优化模型,提出了包含问题定义、体系架构建模、学科建模、优化求解4个步骤的通用建模求解流程;最后,以巡飞/精确打击武器协同作战为例,构建了面向任务成本最低、时间最短的协同作战体系最优化问题并对其进行优化求解。与先设计飞行器后设计体系结构的解耦设计结果对比表明,解耦优化设计忽略了体系结构与飞行器的强耦合特征,无法最优化体系效能;耦合优化设计能够获得体系效能最大化的飞行器设计方案。     

Open Systems: a process for achieving affordability

A major factor that will drive the definition and design of future avionics systems is affordability. Affordability is being addressed on numerous fronts such as hardware re-use, software re-use, COTS leveraging, and reduced cycle times. Each of these thrusts provide potential cost saving along with unique challenges. What is needed is a process that integrates these initiatives while ensuring the overall system objectives are achieved. An Open Systems-based process is key to integrating these initiatives and balancing affordability and system performance goals. Although Open Systems are being widely recognized as a key to affordability, most interpret Open Systems as a set of system attributes that need to be achieved. There are numerous claims of vendors saying they have an Open Systems architecture; or how their system will evolve to an Open Systems architecture. This emphasis is not on increasing affordability, but on attaching a politically-correct label to their product. In this paper, we focus on the Open Systems process as the key to affordability. An Open Systems process is based on Open Systems principles. This paper discusses the Open Systems principles and process in detail and shows how this process integrates numerous affordability initiatives     

Open systems-a process for achieving affordability [in avionicssystems]

A major factor that will drive the definition and design of future avionics systems is affordability. Affordability is being addressed on numerous fronts such as hardware re-use, software re-use, COTS leveraging, and reduced cycle times. Each of these thrusts provide potential cost savings along with unique challenges. What is needed is a process that integrates these initiatives while ensuring the overall system objectives are achieved. An Open Systems-based process is key to integrating these initiatives and balancing affordability and system performance goals. Although Open Systems are being widely recognized as a key to affordability, most interpret Open Systems as a set of system attributes that need to be achieved. There are numerous claims of vendors saying they have an Open Systems architecture or how their system will evolve to an Open Systems architecture. This emphasis is not on increasing affordability but on attaching a politically correct label to their product. In this paper, we focus on the Open Systems process as the key to affordability. An Open Systems process is based on Open Systems principles. This paper discusses the Open Systems principles and process in detail and shows how this process integrates numerous affordability initiatives     

设备总体工作中的软件质量控制

设备软件的质量控制工作是设备总体工作不可缺少的一部分,它直接影响产品的使用质量和维护成本。本文从软件工程化管理角度出发,结合设备总体工作实践和软件测试工作实践,提出了在设备软件研制的不同阶段应该特别关注的质量要素,对设备总体工作人员具有一定的帮助。     

Got software? what managers and engineers need to know

As part of a JPL-wide software quality initiative aimed at addressing the challenges of developing, managing, and acquiring software, a team at JPL generated a detailed Software Training Plan for both managers and engineers. The team took the approach of treating the software training program as though it were a system development task and went through all the typical phases of system development including requirements, design, and implementation. During the requirements collection phase, the team conducted dozens of interviews and identified the specific skills needed. The skills fell into categories such as software management, software engineering, systems engineering, and other technical areas. However, an equally important finding was that several "soft" skills were deemed critical for the successful and timely management and implementation of software-intensive systems. This discusses JPL's approach and "lessons learned" from planning and delivering a software training program in an engineering and scientific environment.     

计算飞行力学的产生和发展

综述了计算飞行力学的产生背景、问题表述、理论框架和飞行力学的计算系统,以及计算飞行力学在未来飞行器研制和应用研究中的重要意义。     

Avionics Development and Integration System Methods

This paper describes a set of life cycle methods that were developed in 1980 and 1981 and used in the later phases of the 757/767 airplane programs. They have been used as a framework to establish and guide the introduction of a wide use of similar methods for the future avionics of Boeing's next airplane, the 7J7. The methods were designed to improve communication of the system's requirements, architecture and implementation to a wide group of interested parties ? not just the development engineers but also the users, maintainers, customers and support organizations. A major aspect of these methods is that they were designed to be used for systems in general not just software systems. This paper will describe the background and goals and objectives leading to the need for systems engineering methods, describe the methods and give an example of their use. It will conclude with remarks on steps taken to introduce methods of this type on a wide scale to support the next Boeing airplane.     

Future test system architectures

An expanding number of test system architectural choices has caused confusion in the test engineering community. This will show the strengths and weaknesses of existing test system architectures including rack and stack systems with GPIB instruments and modular systems like VXI and PXI. It will provide a glimpse into an emerging new architecture: LAN-based test systems. The paper reviews key concerns such as costs, channel counts, footprints, IO speeds, ease-of-integration, and flexibility. The objective of the paper is to provide engineers insight into the most effective test systems for their future applications.