曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

architectures, HOOD provides a rigorous and validated software design process, and UML 2.0 now brings a
standard notation to describe these systems. A summary of the corresponding mappings and a preliminary
snapshot of the Stood v5 tool are shown below:
AADL UML 2.0 HOOD
component component (parent) module
subcomponent part (child) module
provides features provided interface provided interface
required subcomponents required interface required interface
(server) containment connection delegate (provided) implemented_by
(client) containment connection delegate (required) use (uncle)
components connection assembly use (sibling)
By integrating these new technologies into an already deployed software development environment, the aim is to
ease the dissimination of model based solutions to new projects, and to preserve the investment of those who
already chose advanced modeling techniques during the past ten years.
using the AADL for mission critical software development page 7
References
1. RTCA, Software Considerations in Airborne Systems and Equipment Certification (DO-178B), 1992.
2. ISO/IEC, Information technology, Software life cycle process (ISO/IEC 12207), 1995
3. ECSS, Space Engineering: Software (ECSS-E40B), ESA Publication, 2000.
4. HOOD User Group, HOOD Reference Manual release 3.1, Masson & Prentice-Hall, 1993.
5. HOOD User Group, HOOD Reference Manual release 4.0, HUG, 1995.
6. A. Burns, A. Wellings, HRT-HOOD: A Structured Design Method for Hard Real-Time Ada Systems,
Elsevier, 1995
7. J.P. Rosen, An Industrial Approach for Software Design, HUG, 1997.
8. P. Dissaux, HOOD4 and Ada95, Proceedings DASIA conference in Lisbon, 1999.
9. T. Vardanega, Development of On-Board Embedded Real-Time Systems: An Engineering Approach,
ESA Technical Report STR-260, 1999.
10. P. Dissaux, Real-Time C Code Generation from a HOOD Design,
Proceedings DASIA conference in Montreal, 2000.
11. P. Dissaux, HOOD Patterns, Proceedings DASIA conference in Nice, 2001.
12. P. Dissaux, UML & HOOD for aerospace software development, LTRE conference in Toulouse, 2002
13. P. Farail, P. Dissaux, COTRE, A new Approach for Modelling Real-Time Software for Avionics,
Proceedings DASIA conference in Dublin, 2002.
14. P. Dissaux, HOOD and AADL, Proceedings DASIA conference in Prague, 2003.
15. SAE, Draft Avionics Architecture Description Language (AADL)Version 0.95, AS-2C, 2003
16. P. Farail & P. Gaufillet, The COTRE Project: How to model and verify Real Time Architecture?,
Proceedings ERTS conference in Toulouse, 2004.
Executive Summary http://www.ntsb.gov/publictn/2004/AAR0404.htm
1 of 5 10/27/2004 8:39 AM
NATIONAL TRANSPORTATION SAFETY BOARD
Public Meeting of October 26, 2004
(Information subject to editing)
Report of Aviation Accident
In-Flight Separation of Vertical Stabilizer
American Airlines Flight 587, Airbus Industrie A300-605R, N14053
Belle Harbor, New York
November 12, 2001
NTSB/AAR-04/04
This is a synopsis from the Safety Board’s report and does not include the Board’s rationale for the
conclusions, probable cause, and safety recommendations. Safety Board staff is currently making final
revisions to the report from which the attached conclusions and safety recommendations have been
extracted. The final report and pertinent safety recommendation letters will be distributed to
recommendation recipients as soon as possible. The attached information is subject to further review and
editing.
EXECUTIVE SUMMARY
On November 12, 2001, about 0916:15 eastern standard time, American Airlines flight 587, an Airbus
Industrie A300-605R, N14053, crashed into a residential area of Belle Harbor, New York, shortly after
takeoff from John F. Kennedy International Airport, Jamaica, New York. Flight 587 was a regularly
scheduled passenger flight to Las Americas International Airport, Santo Domingo, Dominican Republic, with
2 flight crewmembers, 7 flight attendants, and 251 passengers aboard the airplane. The airplane’s vertical
stabilizer and rudder separated in flight and were found in Jamaica Bay, about 1 mile north of the main
wreckage site. The airplane’s engines subsequently separated in flight and were found several blocks north
and east of the main wreckage site. All 260 people aboard the airplane and 5 people on the ground were
killed, and impact forces and a postcrash fire destroyed the airplane. Flight 587 was operating under the
provisions of 14 Code of Federal Regulations Part 121 on an instrument flight rules flight plan. Visual
meteorological conditions prevailed at the time of the accident.
The safety issues discussed in this report focus on characteristics of the A300-600 rudder control
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：航空資料23(75)