曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
system specifications and contractual documents.
A.5.1.4 Provide historical safety data to developers.
A.5.1.5 Monitor the developer’s system safety activities and review and approve
delivered data in a timely manner, if applicable, to ensure adequate performance and compliance
with safety requirements.
A.5.1.6 Ensure that the appropriate system specifications are updated to reflect results of
analyses, tests, and evaluations.
A.5.1.7 Evaluate new lessons learned for inclusion into appropriate databases and submit
recommendations to the responsible organization.
A.5.1.8 Establish system safety teams to assist the program manager in developing and
implementing a system safety effort.
A.5.1.9 Provide technical data on Government-furnished Equipment or Governmentfurnished
Property to enable the developer to accomplish the defined tasks.
A.5.1.10 Document acceptance of residual mishap risk and associated hazards.
A.5.1.11 Keep the system users apprised of system hazards and residual mishap risk.
A.5.1.12 Ensure the program meets the intent of the latest MIL-STD 882.
A.5.1.13 Ensure adequate resources are available to support the program system safety
effort.
A.5.1.14 Ensure system safety technical and managerial personnel are qualified and
certified for the job.
A.6 NOTES
A.6.1 DoD acquisition practices and safety analysis techniques. Information on DoD
acquisition practices and safety analysis techniques is available at the referenced Internet sites.
Nothing in the referenced information is considered binding or additive to the requirements
provided in this standard.
A.6.1.1 Defense Acquisition Deskbook. Wright-Patterson Air Force Base, Ohio:
Deskbook Joint Program Office.
MIL-STD-882D
APPENDIX A
25
A.6.1.2 System Safety Analysis Handbook. Unionville, VA: System Safety Society.
MIL-STD-882D
26
CONCLUDING MATERIAL
Custodians: Preparing activity:
Army - AV Air Force - 40
Navy - AS
Air Force – 40 Project SAFT - 0038
Reviewing activities:
Army - AR, AT, CR, MI
Navy - EC, OS, SA, SH
Air Force - 10, 11, 13, 19
STANDARDIZATION DOCUMENT IMPROVEMENT PROPOSAL
INSTRUCTIONS
1. The preparing activity must complete blocks 1, 2, 3, and 8. In block 1, both the document number and revision letter
should be given.
2. The submitter of this form must complete blocks 4, 5, 6, and 7, and send to preparing activity.
3 The preparing activity must provide a reply within 30 days from receipt of the form.
NOTE: This form may not be used to request copies of documents, nor to request waivers, or clarification of
requirements on current contracts. Comments submitted on this form do not constitute or imply authorization to waive any
portion of the referenced document(s) or to amend contractual requirements.
I RECOMMEND A CHANGE: 1. DOCUMENT NUMBER
MIL-STD-882
2. DOCUMENT DATE (YYYYMMDD)
20000210
3. DOCUMENT TITLE
System Safety
4. NATURE OF CHANGE (Identify paragraph number and include proposed rewrite, if possible. Attach extra sheets as needed.)
5. REASON FOR RECOMMENDATION
6. SUBMITTER
a. NAME (Last, First, Middle Initial)
b. ORGANIZATION
c. ADDRESS (Include zip code)
d. TELEPHONE (Include Area Code)
(1) Commercial
(2) DSN
(if applicable)
7. DATE SUBMITTED
(YYYYMMDD)
8. PREPARING ACTIVITY
a. NAME
Headquarters, Air Force Materiel Command
System Safety Division
b. TELEPHONE (Include Area Code)
(1) Commercial (937) 257-6007
(2) DSN 787-6007
b. ADDRESS (Include Zip Code)
HQ AFMC/SES
4375 Chidlaw Road
Wright Patterson AFB, Ohio 45433-5006
IF YOU DO NOT RECEIVE A REPLY WITHIN 45 DAYS, CONTACT:
Defense Standardization Program Office (DLSC-LM)
8725 John J. Kingman Road, Suite 2533
Fort Belvoir, Virginia 22060-6621
Telephone 703 767-6888 DSN 427-6888
DD Form 1426, FEB 1999 (EG) PREVIOUS EDITION IS OBSOLETE. WHS/DIOR, Feb 99
FAA System Safety Handbook, Appendix J: Software Safety
December 30, 2000
J-1
Appendix J
Software Safety
SOFTWARE SAFETY..............................................................................................................................1
J.0 SOFTWARE SAFETY DURING LIFE CYCLE PHASES................................................................2
FAA System Safety Handbook, Appendix J: Software Safety
December 30, 2000
J-2
J.0 Software Safety During Life Cycle Phases
The safety process should support a structured program life cycle model that incorporates both the system
design and engineering process and the software acquisition process. Prominent software life cycle models
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
System Safety Handbook系统安全手册下(125)
