ASTM F3201-16

Standard Practice for Ensuring Dependability of Software Used in Unmanned Aircraft Systems (UAS)

SCOPE
1.1 This standard practice intends to ensure the dependability of UAS software. Dependability includes both the safety and security aspects of the software.  
1.2 This practice will focus on the following areas: (a) Organizational controls (for example, management, training) in place during software development. (b) Use of the software in the system, including its architecture and contribution to overall system safety and security. (c) Metrics and design analysis related to assessing the code. (d) Techniques and tools related to code review. (e) Quality assurance. (f) Testing of the software.  
1.3 There is interest from industry and some parts of the CAAs to pursue an alternate means of compliance for software assurance for small UAS (sUAS).  
1.4 This practice is intended to support sUAS operations. It is assumed that the risk of sUAS will vary based on concept of operations, environment, and other variables. The fact that there are no souls onboard the UAS may reduce or eliminate some hazards and risks. However, at the discretion of the CAA, this practice may be applied to other UAS operations.  
1.5 This standard does not purport to address all of the safety concerns, if any, associated with its use. It is the responsibility of the user of this standard to establish appropriate safety and health practices and determine the applicability of regulatory limitations prior to use.

General Information

• Status: Published
• Publication Date: 31-Aug-2016
• ICS: 35.240.60 - IT applications in transport
• ICS: 49.020 - Aircraft and space vehicles in general
• Technical Committee: F38 - Unmanned Aircraft Systems
• Drafting Committee: F38.01 - Airworthiness

Relations

• Referred By: ASTM F3341/F3341M-23 - Standard Terminology for Unmanned Aircraft Systems
• Effective Date: 01-Sep-2016
• Referred By: ASTM F3196-18 - Standard Practice for Seeking Approval for Beyond Visual Line of Sight (BVLOS) Small Unmanned Aircraft System (sUAS) Operations
• Effective Date: 01-Sep-2016
• Referred By: ASTM F3298-19 - Standard Specification for Design, Construction, and Verification of Lightweight Unmanned Aircraft Systems (UAS)
• Effective Date: 01-Sep-2016

Standards Content (Sample)

This international standard was developed in accordance with internationally recognized principles on standardization established in the Decision on Principles for the
Development of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.
Designation: F3201 − 16
Standard Practice for
Ensuring Dependability of Software Used in Unmanned
1
Aircraft Systems (UAS)
This standard is issued under the fixed designation F3201; the number immediately following the designation indicates the year of
original adoption or, in the case of revision, the year of last revision. A number in parentheses indicates the year of last reapproval. A
superscript epsilon (´) indicates an editorial change since the last revision or reapproval.
3
1. Scope 2.2 IEC Standard:
IEC 62304 Medical Device Software—Software Life Cycle
1.1 This standard practice intends to ensure the dependabil-
Processes
ity of UAS software. Dependability includes both the safety
4
2.3 ISO Standards:
and security aspects of the software.
ISO 9001 Quality Management Systems—Requirements
5
1.2 This practice will focus on the following areas: (a)
2.4 ICAO Standard:
Organizationalcontrols(forexample,management,training)in ICAO 9859 Safety Management Manual
6
place during software development. (b) Use of the software in
2.5 NASA Standard:
the system, including its architecture and contribution to
NASA Technical Briefs Making Sense out of SOUP (Soft-
overall system safety and security. (c) Metrics and design
ware of Unknown Pedigree)
7
analysis related to assessing the code. (d) Techniques and tools
2.6 RTCA Standards:
related to code review. (e) Quality assurance. (f) Testing of the
RTCA DO-178C Software Considerations in Airborne Sys-
software.
tems and Equipment Certification
RTCA DO–278A Software Integrity Assurance Consider-
1.3 There is interest from industry and some parts of the
ations for Communication, Navigation, Surveillance, and
CAAs to pursue an alternate means of compliance for software
Air Traffic Management (CNS/ATM) Systems
assurance for small UAS (sUAS).
RTCADO-326 AirworthinessSecurityProcessSpecification
8
1.4 This practice is intended to support sUAS operations. It
2.7 Military Standards:
is assumed that the risk of sUAS will vary based on concept of Department of Defense Joint Software System Safety Hand-
operations, environment, and other variables. The fact that book
there are no souls onboard the UAS may reduce or eliminate MIL-STD-882E Department of Defense Standard for Sys-
tem Safety
somehazardsandrisks.However,atthediscretionoftheCAA,
this practice may be applied to other UAS operations.
3. Terminology
1.5 This standard does not purport to address all of the
3.1 Definitions of Terms Specific to This Standard:
safety concerns, if any, associated with its use. It is the
3.1.1 application programming interface (API)—definition
responsibility of the user of this standard to establish appro-
of the inputs and outputs for operations intended for use by
priate safety and health practices and determine the applica-
other software modules.
bility of regulatory limitations prior to use.
3.1.2 architecture—architecture is made up of the definition
of the sUAS Software components, the data that flows between
2. Referenced Documents
2
2.1 FAA Standard:
3
Available from International Electrotechnical Commission (IEC), 3, rue de
FAA 23.1309–1E System Safety Analysis and Assessment
Varembé, P.O. Box 131, 1211 Geneva 20, Switzerland, http://www.iec.ch.
for Part 23 Airplanes
4
Available from International Organization for Standardization (ISO), ISO
Central Secretariat, BIBC II, Chemin de Blandonnet 8, CP 401, 1214 Vernier,
Geneva, Switzerland, http://www.iso.org.
5
Available from International Civil Aviation Organization (ICAO), 999 Robert-
1
This practice is under the jurisdiction ofASTM Committee F38 on Unmanned Bourassa Blvd., Montreal, Quebec H3C 5H7, Canada, http://www.icao.int.
6
Aircraft Systems and is the direct responsibility of Subcommittee F38.01 on Available from U.S. National Air and Space Administration (NASA), 300 E.
Airworthiness. Street, SW, Suite 5R30, Washington, DC 20546, http://www.nasa.gov.
7
Current edition approved Sept. 1, 2016. Published September 2016. DOI: Available from Radio Technical Commission for Aeronautics (RTCA), 1150
10.1520/F3201-16. 18th St., NW, Suite 910, Washington, DC 20036, http://www.rtca.org.
2 8
Available from Federal Aviation Administration (FAA), 800 Independence Available from DLA Document Services, Building 4/D, 700 Robbins Ave.,
Ave., SW, Washington, DC 20591, http://www.faa.gov. Philadelphia, PA 19111-5094, http://quicksearch.dla.mil.
Copyright © ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United States
1

---------------------- Page: 1 ----------------------
F3201 − 16
the components (data flow), and the order of execution of the could be used in safety evaluations, and could lead to d
...