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/AS6513AEROSPACESTANDARDAS6513Issued 2016-12Unmanned Systems (UxS) Control Segment (UCS) Architecture:Confor
5、mance SpecificationRATIONALEThis document is the SAE publication of the Department of Defense UAS Control Segment (UCS) Architecture: Conformance Specification (UCS-SPEC-CONFORMANCE) Version 2.4(PR) approved for Distribution A public release 15.S-1859.TABLE OF CONTENTS1. SCOPE31.1 Purpose.31.2 Field
6、 of Application31.3 Precedence .32. REFERENCES32.1 Applicable Documents 32.1.1 SAE Publications.32.1.2 ISO Publications42.2 Definitions .42.3 Terminology 53. OVERVIEW.53.1 Background .53.2 Application Areas and Limitations.63.3 Basic Structure64. GENERAL REQUIREMENTS.64.1 Delivery Requirements65. PR
7、ODUCT IDENTIFICATION/METADATA66. SERVICE DESCRIPTION.76.1 Service Interface Description 76.2 Service Package Extensions 86.3 Service Reachability Description 96.3.1 Platform-Specific Protocol.96.3.2 Service Presence and Endpoint96.3.3 Service Contract97. APPLICATION PROGRAMMING INTERFACES .98. ARCHI
8、TECTURE DESCRIPTION 9SAE INTERNATIONAL AS6513 Page 2 of 129. PRODUCT TEST ARTIFACTS .109.1 Test Unit/Test Environment 109.2 Software Installation Instructions 109.3 Test Drivers/Test Harness 109.4 System User Guide.109.5 Test Plan and Traceability Matrix109.6 Test Results 1110. NOTES1110.1 UCS Servi
9、ce Package.1110.2 Service Description Format.1210.3 Revision Indicator12FIGURE 1 VEHICLE FLIGHT CONTROL SERVICE PACKAGE IN AS6518 11SAE INTERNATIONAL AS6513 Page 3 of 121. SCOPEThis document is the authoritative specification within the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture f
10、or establishing conformance requirements for UCS products. The UCS products addressed by this specification are UCS software components and UCS software configurations that provide one or more UCS services, and UCS systems that employ one or more UCS services.The conformance of UCS products is deter
11、mined by assessing the conformance of the UCS product description to the UCS Architecture. The UCS product description includes test artifacts.1.1 PurposeThe purpose of this specification is to establish verifiable conformance requirements for UCS products.1.2 Field of ApplicationThis specification
12、applies to all conformant UCS software components, UCS software configurations, and UCS systems that are described in a UCS product registry or UCS product repository. The document is applicable to the complete lifecycle of UCS product descriptions, including requirements definition, acquisition and
13、 development, deployment and maintenance, and obsolescence.1.3 PrecedenceThis document is the authoritative source of conformance requirements for UCS products and takes precedence over all other documents in the UCS Architecture Library and all other references on the subject of UCS product conform
14、ance. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.2. REFERENCES2.1 Applicable DocumentsThe following publications form a part of this document to the extent specified herein. The latest issue of SAE publications shall ap
15、ply. The applicable issue of other publications shall be the issue in effect on the date of the purchase order. In the event of conflict between the text of this document and references cited herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable
16、 laws and regulations unless a specific exemption has been obtained.2.1.1 SAE PublicationsAvailable from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA and Canada) or +1 724-776-4970 (outside USA), www.sae.org.AS6512 UxS Control Segment (UCS) Arch
17、itecture: Architecture DescriptionAIR6514 UxS Control Segment (UCS) Architecture: Interface Control Document (ICD)AIR6515 UxS Control Segment (UCS) Architecture: EA Version of UCS ICD ModelAIR6516 UxS Control Segment (UCS) Architecture: RSA Version of UCS ICD ModelAIR6517 UxS Control Segment (UCS) A
18、rchitecture: Rhapsody Version of UCS ICD ModelAS6518 UxS Control Segment (UCS) Architecture: ModelAS6522 UxS Control Segment (UCS) Architecture: Architecture Technical GovernanceSAE INTERNATIONAL AS6513 Page 4 of 122.1.2 ISO PublicationsAvailable at http:/webstore.ansi.org/.ISO/IEC/IEEE 42010 System
19、s and software engineering - Architecture description2.2 DefinitionsThe following technical definitions apply to this publication.AUTHORITATIVE: Recognized as true and dependable.RESOURCE: An identifiable entity that has value to a stakeholder.SERVICE DESCRIPTION: The description of a service provid
20、ed by a software component, software configuration or system if the technical assumptions are satisfied. SERVICE REACHABILITY: The means by which service presence is known and the service is accessed, and the means by which service contracts are established.UCS PRODUCT: A UCS product is a separately
21、 managed UCS system or unit of deployable software that may be acquired and used independently of other UCS products.UCS PRODUCT ARTIFACT: A configuration item that is part of a UCS product description. UCS product artifacts include documents, drawings, models, and software.UCS PRODUCT CONFORMANCE:
22、Adherence of a UCS product description or a UCS product artifact to a release of the UCS Architecture.UCS PRODUCT DESCRIPTION: The metadata and artifacts that collectively describe a UCS product.UCS PRODUCT METAMODEL: Searchable public data about a UCS product. The term includes descriptive metadata
23、, structural metadata, and administrative metadata.UCS PRODUCT REGISTRY: A database containing metadata about UCS products.UCS PRODUCT REPOSITORY: A database containing metadata and artifacts about UCS products.UCS SOFTWARE COMPONENT: A UCS software component is a unit of deployable UCS software tha
24、t is not further decomposed into other separately managed software components described in a UCS registry or repository. A UCS software component may be as small as a single UCS service participant or as large as a complete UCS domain or collection of UCS domains. Note: a conformant UCS software com
25、ponent will be assigned at least one UCS Architecture Model service package as specified herein.UCS SOFTWARE CONFIGURATION: A UCS software configuration is a unit of deployable UCS software that comprises multiple UCS software components and/or (separately managed) UCS software configurations descri
26、bed in a UCS registry or repository. Note: a conformant UCS software configuration will be assigned at least one UCS Architecture Model service package as specified herein.UCS SYSTEM: A UCS system is a physical item that independently satisfies its system-of-interest use cases1, has external communi
27、cation interfaces, and at least one human/machine interface (HMI). UCS systems may include man-portable systems, vehicle-transportable systems, and fixed facilities. UCS systems include UCS software configurations and/or UCS software components. These MAY be described in a UCS product repository or
28、UCS product registry. Note: a conformant UCS system will be assigned at least one UCS service package as specified herein.1 Note: conformance to the Use Case Model package in UCS-SPEC-MODEL is not required.SAE INTERNATIONAL AS6513 Page 5 of 12VERIFICATION: The authoritative establishment that an ite
29、m is conformant to a requirement.VERIFICATION PROCEDURE: The means by which verification is achieved.2.3 TerminologyThe following terminology applies to this specification.SHALL: This term requires that there is no deviation in conformance.SHOULD: This term is to be used wherever the criterion for c
30、onformance is to meet a business objective. Failure to meet a “Should” statement SHALL be justified.MUST: This term is used for a legislative or regulatory requirement (e.g., safety or security) with which the parties shall comply. It is not used to express a requirement of the specification.WILL: T
31、his term is used for the future tense. It does not express a requirement of the specification.MAY: This term expresses a permissible practice or action. It does not express a requirement of the specification.3. OVERVIEW3.1 BackgroundThe UCS products of interest to this specification are UCS software
32、 components and UCS software configurations that provide one or more UCS services, and UCS systems that employ one or more services. This specification establishes UCS product conformance requirements based on UCS product description artifacts as summarized below.xProduct Identification/MetadataxSer
33、vice DescriptionxApplication Programming InterfacesxArchitecture DescriptionxProduct Test ResultsUCS Architecture conformance is based on elements of these configuration items in the UCS Architecture Library as specified herein.xThe UCS Architecture Model, AS6518: the source model for establishing U
34、CS product conformance. The following informational configuration items are derived from the UCS Architecture Model and are not specifications or technical standards. The use of these configuration items in lieu of AS6518 is discussed in Section 10.xEA Version of the UCS ICD Model, AIR6515xRSA Versi
35、on of the UCS ICD Model, AIR6516xRhapsody Version of the UCS ICD Model, AIR6517xInterface Control Document (ICD), AIR6514SAE INTERNATIONAL AS6513 Page 6 of 123.2 Application Areas and LimitationsThis specification is intended for use in the governance and management of all UCS product descriptions i
36、ncluding those held in UCS registries and UCS product repositories such as those managed by government and industry. This specification is applicable throughout the UCS product lifecycle, including acquisition planning, acquisition, development, deployment, maintenance, and obsolescence phases.This
37、specification does not define conformance verification procedures or conformance verification artifacts, and does not establish conformance verification roles and responsibilities. This specification does not provide governance on how UCS products are to be described in a UCS product registry or UCS
38、 product repository. This specification does not establish requirements for UCS product policies. 3.3 Basic StructureThis specification establishes the general requirements for UCS product description artifacts in Section 4. Sections 5 through 9 establish the specific requirements for each product d
39、escription artifact identified in 3.1. Section 10 provides additional notes and is not normative.4. GENERAL REQUIREMENTSThe following UCS product types SHALL be conformant to the UCS Architecture as specified herein:xUCS software componentsxUCS software configurationsxUCS systemsConformance SHALL be
40、 determined using the UCS product description. UCS products SHALL have a UCS product description in accordance with the requirements herein. A product description SHALL exist for each released configuration of a UCS product.The UCS product description MAY be extended and MAY be made available to oth
41、er parties via a UCS product registry or UCS product repository.UCS product conformance verification procedures and conformance verification artifacts are not considered part of the UCS product description. UCS product policies are not considered part of the UCS product description.4.1 Delivery Requ
42、irementsThe UCS product description SHALL be delivered to the conformance verification agent in machine-readable form via DVD or pre-arranged electronic submittal. Text documents SHALL be delivered in Microsoft Word 2003 (or later) format or Portable Document Format (PDF) with text that can be searc
43、hed and parsed; PDF files consisting of scanned images SHALL NOT be submitted as conformance artifacts. All model information SHALL be delivered in two forms: the original model file(s), with tool(s) and version clearly identified, and in export XMI format suitable for importation into other designt
44、ools. 5. PRODUCT IDENTIFICATION/METADATAAt a minimum the UCS product description SHALL include the following technical metadata.xName of UCS productxProduct versionSAE INTERNATIONAL AS6513 Page 7 of 12xUCS product type, which SHALL be one of the following (see 2.2):o UCS software componento UCS soft
45、ware configurationo UCS systemxList of UCS service packages in AS6518 that are assigned to the UCS product (see Section 6). The version of AS6518 SHALL be identified for each assigned UCS service package. For each assigned UCS service package, it SHALL be indicated if the base service package in AS6
46、518 has been extended (see 6.2). xList of UCS services (if any) in AS6518 that are required by the UCS product. The version of AS6518 SHALL be identified for each required UCS service. For each required UCS service, it SHALL be indicated if the base service package in AS6518 must be extended (see 6.
47、2).Additional metadata MAY be required for a UCS registry or UCS repository.6. SERVICE DESCRIPTIONThe UCS product description SHALL include one or multiple UCS product service descriptions. A UCS product service description SHALL comprise two distinct elements:xService interface descriptionxService
48、reachability descriptionUCS Architecture conformance applies to the service interface description. The service reachability description is system/platform-specific, but is required to communicate with and test the service.6.1 Service Interface DescriptionThe UCS product service interface description
49、 MAY be provided in any format/tool. However, the UCS product service interface description SHALL clearly show the correspondence between it and the service packages in the UCS Architecture Model. See Section 10.In the authoritative UCS Architecture Model and derived ICD models, services are described in service packages (packages that contain service interfaces). The location of service packages in the UCS Architect
