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 theref
2、rom, 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 2016 SAE InternationalAll rights reserved. No part of this publi
3、cation 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-4970 (out
4、side USA)Fax: 724-776-0790Email: CustomerServicesae.orgSAE WEB ADDRESS: http:/www.sae.orgSAE values your input. To provide feedback on thisTechnical Report, please visithttp:/standards.sae.org/AS6512 AEROSPACESTANDARDAS6512Issued 2016-12Unmanned Systems (UxS) Control Segment (UCS) Architecture: Arch
5、itecture DescriptionRATIONALEThis document is the SAE publication of the Department of Defense UAS Control Segment (UCS) Architecture: Architecture Description Version 3.4(PR) approved for Distribution A public release 15.S-1859.FOREWORDThis Architecture Description (AD) establishes the content of t
6、he SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture. The UCS Architecture is expressed by a library of SAE publications, of which this publication is the highest in the document tree. The official designation of the UCS Architecture is therefore AS6512. The other SAE publications in the
7、 UCS Architecture Library are: AS6513, AIR6514, AIR6515, AIR6516, AIR6517, AS6518, AIR6519, AIR6520, AIR6521, and AS6522.The UCS Architecture was originally applicable to all systems that control unmanned aircraft above 10kg gross take-offweight (nominal), however it has since been extended to addre
8、ss all unmanned systems whose means of conveyance includes air, water, and ground. This extension will be fully addressed in later revisions of the standard. The UCS Architecture is concerned with control station software but not the control station software external environment, which including inf
9、ormation access, communications, and human-computer interfaces.The UCS Architecture defines a Service Oriented Architecture (SOA) and modeling framework for the specification, integration, implementation, and deployment of control station software. The architecture is centered on a SOA Platform Inde
10、pendent Model (PIM) and associated foundation models. Platform independence (independence of the software operating environment) allows the UCS Architecture to be implemented on different computing infrastructures and with different communication protocols. This supports technology insertion and ado
11、ption on multiple UCS systems and related architectures.The UCS Architecture is extensible and describes approximately 150 application software services to support the current capabilities of military UAS. The architecture is deployable on any control station from a hand-held device to a fixed facil
12、ity with multiple mission planners, operators, and analysts.The United States Office of the Secretary of Defense (OSD) UCS Working Group developed the UCS Architecture through Release 3.4. In April 2015, governance and management of the UCS Architecture was transferred to the SAE AS-4UCS Technical C
13、ommittee. The historical purpose and rationale for the OSD UCS Architecture is set out in the documentation associated with Release 3.4. The SAE UCS Architecture Library is a subset of the configuration items in that release. The SAE UCS Architecture Library omits OSD planning documentation and some
14、 OSD guidance documentation applicable to Department of Defense programs of record.SAE INTERNATIONAL AS6512 Page 2 of 50TABLE OF CONTENTS1. SCOPE 41.1 Scope and Project Identification . 41.2 Developing Organization. 41.3 UCS Architecture Library 41.3.1 Governance Configuration Items 51.3.2 Model Con
15、figuration Items 51.3.3 Document Configuration Items . 81.4 Organization of this Document 102. REFERENCES 102.1 Definitions . 102.1.1 General Definitions 102.1.2 Architecture Description 112.1.3 Model Driven Architecture. 122.1.4 Architecture Concepts. 122.1.5 Business Model. 132.2 Acronyms 133. SYS
16、TEM-OF-INTEREST 163.1 Environment 164. ARCHITECTURAL DECISIONS . 164.1 Partitioning into Domains 164.1.1 Primary Mission Control 174.1.2 Mission Planning . 174.1.3 Dynamic Airspace . 174.1.4 External Messaging and Communication . 184.1.5 Sensor Product Processing, Exploitation, and Dissemination 184
17、.1.6 System Support. 184.2 System Use Case Model. 184.3 Platform Independence. 194.3.1 Platform Independent Model. 194.3.2 Platform Specific Models. 194.3.3 Platform Technologies and Architectural Styles . 205. ARCHITECTURE FRAMEWORK. 205.1 Model Package Structure 205.2 Architecture Technical Govern
18、ance Policies 226. ARCHITECTURE VIEWS . 246.1 Version Description Document . 256.2 Architectural Model and ICD . 256.2.1 System Use Case Model. 266.2.2 Domain Participant Model. 306.2.3 Information Model . 316.2.4 Service Contract and NFP Model . 346.2.5 Use Case Trace 366.2.6 Interface Control Docu
19、ment (ICD) 366.3 Conformance Specification . 406.3.1 UCS Product Service Description 426.3.2 Application Program Interfaces 446.3.3 Architecture Description 446.3.4 Product Test Artifacts 446.4 Guidance Configuration Items 456.4.1 DDS. 457. NOTES 457.1 Revision Indicator 45SAE INTERNATIONAL AS6512 P
20、age 3 of 50APPENDIX A 46FIGURE 1 UCS ARCHITECTURE LIBRARY CONFIGURATION ITEMS . 4FIGURE 2 RELATIONSHIP BETWEEN MODEL FILES IN UCS ARCHITECTURE LIBRARY. 6FIGURE 3 AS6518 PACKAGES. 6FIGURE 4 AS6518 UCS ARCHITECTURAL MODEL PACKAGES. 6FIGURE 5 AIR6515-MODEL PACKAGES . 7FIGURE 6 UCS MODEL (IN DOMAIN PART
21、ICIPANT MODEL PACKAGE). 17FIGURE 7 UCS MISSION THREADS AND L0 USE CASES. 19FIGURE 8 MODEL PACKAGE STRUCTURE 22FIGURE 9 AD CONCEPTUAL MODEL FOR ARCHITECTURE VIEWS (ISO/ISO/IEEE 42010) 25FIGURE 10 L1 USE CASE DIAGRAM EXAMPLE. 27FIGURE 11 L2 USE CASE DIAGRAM EXAMPLE. 28FIGURE 12 ACTIVITY DIAGRAM EXAMPL
22、E 29FIGURE 13 UML SEQUENCE DIAGRAM EXAMPLE . 29FIGURE 14 L2 COLLABORATION DIAGRAM IN PRIMARY MISSION CONTROL . 30FIGURE 15 SOA PARTICIPANT DIAGRAM EXAMPLE 31FIGURE 16 UCS SERVICE CONTRACT AND NON-FUNCTIONAL PROPERTY METAMODEL 35FIGURE 17 AIR6515-MODEL PACKAGE STRUCTURE 38FIGURE 18 AIR6517-MODEL PACK
23、AGE STRUCTURE VIEWED IN RHAPSODY . 39FIGURE 19 AIR6516-MODEL PACKAGE STRUCTURE VIEWED IN RSA 40TABLE 1 MODEL CONFIGURATION ITEMS 5TABLE 2 ADDITIONAL CONFIGURATION ITEMS . 8TABLE 3 ARCHITECTURE TECHNICAL GOVERNANCE POLICIES 23TABLE 4 SYSTEM USE CASES VIEW . 26TABLE 5 DOMAIN PARTICIPANT VIEW. 31TABLE
24、6 INFORMATION VIEW. 34TABLE 7 SERVICE CONTRACT AND NON-FUNCTIONAL PROPERTY VIEW 35TABLE 8 USE CASE TRACE VIEW. 36TABLE 9 ICD VIEW 37TABLE 10 CONFORMANCE SPECIFICATION. 45SAE INTERNATIONAL AS6512 Page 4 of 501. SCOPE1.1 Scope and Project IdentificationThis document is the Architecture Description (AD
25、) for the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture. This AD serves as the official designation of the UCS Architecture - SAE AS6512. The UCS Architecture is expressed by a library of SAE publications as referenced herein. The other publications in the UCS Architecture Library ar
26、e: AS6513, AIR6514, AIR6515, AIR6516, AIR6517, AS6518, AIR6519, AIR6520, AIR6521, and AS6522.1.2 Developing OrganizationThe developing organization for the SAE UCS Architecture is the SAE AS-4UCS Technical Committee. Governance and management of the UCS Architecture was transferred from OSD to the S
27、AE in April 2015.1.3 UCS Architecture LibraryThe UCS Architecture is expressed by the UCS Architecture Library, which comprises the configuration items listed below. The library itself shares the designation of this AD - AS6512.The document tree for configuration items in the UCS Architecture Librar
28、y is shown in Figure 1. The document tree shows the general flow of architectural decisions, with a lower-level configuration item conforming to the higher-level configuration item in the tree.Figure 1 - UCS architecture library configuration itemsSAE INTERNATIONAL AS6512 Page 5 of 501.3.1 Governanc
29、e Configuration Items1.3.1.1 Architecture Technical GovernanceArchitecture Technical Governance, AS6522, comprises a set of policies, processes, and standard definitions to establish consistency and quality in the development of architecture work products. It provides guidance for the use of adopted
30、 industry standards and modeling conventions in the use of the Unified Modeling Language (UML) and Service Oriented Architecture Modeling Language (SoaML), including where the UCS Architecture deviates from normal UML conventions.The document identifies the defining policies, guidelines, and standar
31、ds of architecture technical governance in the followingareas:xIndustry standards adopted by the SAE AS-4UCS Technical Committee: these are the industry standards and specifications adopted by the committee in the generation and documentation of the architecture.xUCS Architecture development: UCS sp
32、ecific policies on the development of the UCS Architecture, specifically the UCS Architecture Model (see 1.3.2).Architecture Technical Governance is supported by these additional work products that are available to members of the SAE AS-4UCS Technical Committee: Model Interchange Guide and ICD Metho
33、dology.Further information on Architecture Technical Governance is provided in 5.2.1.3.2 Model Configuration ItemsThe UCS Architecture Library includes four model files. These configuration items are listed in Table 1. The authoritative UML tool used by the SAE AS-4UCS Technical Committee is Sparx E
34、nterprise Architect. The authoritative model configuration item for the UCS Architecture is the Model, AS6518.To support the development of ICD-conformant UCS products, three derived archive (zip) files are provided. These are the EA Version of UCS ICD Model, AIR6515, the RSA Version of the UCS ICD
35、Model, AIR6516, and the Rhapsody Versionof UCS ICD Model, AIR6517. The correspondence between the model files is shown in Figure 2. This figure also shows the correspondence between the models and the Interface Control Document (ICD), AIR6514. The ICD is described in 1.3.3.4.Table 1 - Model configur
36、ation itemsReference Title RevisionAS6518 Model originalAIR6515 EA Version of UCS ICD Model originalAIR6516 RSA Version of UCS ICD Model originalAIR6517 Rhapsody Version of UCS ICD Model originalSAE INTERNATIONAL AS6512 Page 6 of 50Figure 2 - Relationship between model files in UCS architecture libr
37、ary1.3.2.1 ModelUCS Architecture Model, AS6518, is expressed in Sparx Enterprise Architect and is the authoritative source of the UCS Architectural Model. The high-level package structure for AS6518 is shown in Figure 3. The Model has three top level packages: NOTICES, UCS Architecture Technical Gov
38、ernance, and UCS Architectural Model.Figure 3 - AS6518 packagesThe NOTICES package contains data distribution statements in the form of notes. The UCS Architecture Technical Governance package provides material in support of the authoritative document AS6522. The authoritative UCS Architectural Mode
39、l package comprises four packages: the Service Contract and Non-Functional Property Model, theSystem Use Case Model, the Domain Participant Model, and the Information Model. The UCS services are described by the service packages within the Domain Participant Model. A list of the service packages is
40、provided in Appendix A.Figure 4 - AS6518 UCS architectural model packagesFurther information on the UCS Architectural Model and derived ICD work products is provided in 6.2.SAE INTERNATIONAL AS6512 Page 7 of 501.3.2.2 EA Version of UCS ICD ModelThis configuration item is an archive (zip) file. It in
41、cludes the AIR6515.eap file, which is the the ICD subset of the AS6518.eap file. The zip file includes the following contents:AIR6515-LICENSE.txtAIR6515-README.txtAIR6515-UG.pdfAIR6515-MODEL.eapUCS_MDG.xmlAIR6515-LICENSE.txt provides the data distribution and permitted usage statement. AIR6515-READM
42、E.txt describes the version history and contents of the archive (zip) file. AIR6515 User Guide, AIR6515-UG.pdf, describes the content of the AIR6515-MODEL.eap file, and how to install the UCS_MDG.xml file (required UML profiles) into the EA environment. The packages contained in AIR6515-MODEL.eap fi
43、le are shown below.Figure 5 - AIR6515-model packagesFurther information on this configuration item is provided in AIR6515, 6.2.6.1.1.3.2.3 RSA version of UCS ICD ModelThis configuration item is an archive (zip) file that includes the following contents:AIR6516-LICENSE.txtAIR6516-README.txtAIR6516-UG
44、.pdfAIR6516-MODEL.emxUCS_DM.epxUCS_NFP.epxUCS_SoaML.epxThe purpose of RSA Version of UCS ICD Model is to support model-based engineers who are familiar with the Rational Software Architect (RSA) modeling tool and UML. They will use this product just as they would use elements of the EA Version of th
45、e Model, but within the RSA tool environment. AIR6516-LICENSE.txt provides the data distribution and permitted usage statement. AIR6516-README.txt describes the version history and contents of the archive (zip) file. AIR6516 User Guide, AIR6516-UG.pdf, describes the content of the AIR6516-MODEL.emx
46、file and how to install the *.epx files (required UML profiles) into the RSA environment. The package structure of the AIR6516-MODEL.emx file is identical to the AIR6515-MODEL.eap file (EA).Further information on this configuration item is provided in 6.2.6.3.SAE INTERNATIONAL AS6512 Page 8 of 50Thi
47、s configuration item is an archive (zip) file that includes the following contents:AIR6517-LICENSE.txtAIR6517-README.txtAIR6517-MODEL (folder)AIR6517-UG.pdfAIR6517-MODEL.rpyThe purpose of the Rhapsody Version of UCS ICD Model is to support model-based engineers who are familiar with the Rhapsody mod
48、eling tool and UML. They will use this product just as they would use the EA Version of UCS ICD Model,but within the Rhapsody tool environment.AIR6517-LICENSE.txt provides the data distribution and permitted usage statement. AIR6517-README.txt describes the version history and contents of the archiv
49、e (zip) file. AIR6517 User Guide, AIR6517-UG.pdf, describes the content of the AIR6517-MODEL.rpy file, and how to use this content. The package structure of this file is identical to the AIR6515-MODEL.eap file (EA).Further information on this configuration item is provided in 6.2.6.2.1.3.3 Document Configuration ItemsTable 2 lists the document configuration items in the UCS Architecture Library. These documents are additional to Archi
