SAE AIR 6518-2016 Unmanned Systems (UxS) Control Segment (UCS) Architecture UCS Architecture Model.pdf

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 there

2、from, 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 International All rights reserved. No part of this p

3、ublication 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-497

4、0 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/standards.sae.org/AS6518 AEROSPACE STANDARD AS6518 Issued 2016-12 Unmanned Systems (UxS) Control Segment (UCS) Ar

5、chitecture: UCS Architecture Model RATIONALE This document is the SAE publication of the Department of Defense UAS Control Segment (UCS) Architecture: EA Version of the UCS Model (UCS-SPEC-MODEL) Version 2.4 (PR) approved for Distribution A public release 15.S-1859. FOREWORD The Unmanned Systems (Ux

6、S) Control Segment (UCS) Architecture is described in AS6512 Unmanned Systems Control Segment (UCS) Architecture: Architecture Description This Model applies to the Unmanned System (UxS) Control Segment (UCS) Architecture. The Model is the specification of the UCS Architecture including the System U

7、se Case Model, Domain Participant Model, Information Model, and the Service Contract and Non-Functional Property Model. The System Use Case Model contains the Actors, UCS System level products, all UCS Domain Use Case products. The Domain Participant Model contains the UCS application Domain product

8、s defining the service interfaces as well as the UCS System States and Modes top level definitions. The Information Model contains the UCS Conceptual Data Model (CDM) which specifies the data to build, operate, manage, and maintain a UxS Control System as well as the Logical Data Model specifying th

9、e UCS Messages, their correspondence to the CDM, and the representation of LDM elements. The Service Contract and Non-Functional Property Model defines the Non-Functional properties of UCS Safety, Information Assurance (IA), and Quality of Service (QoS). 1. SCOPE This brief User Guide recaps the con

10、tent of the AS6518 UCS Architectural Model described in detail in AS6512 UCS Architecture: Architecture Description. The purpose of the UCS Architecture Model is to provide the authoritative source for other models and products within the UCS Architecture as shown in the AS6512 UCS Architecture: Arc

11、hitecture Description. 2. REFERENCES There are no referenced publications specified herein. SAE INTERNATIONAL AS6518 Page 2 of 3 3. CONTENT OF AS6518 EA-MODEL 3.1 Package Contents UCS Architecture Model, AS6518, is expressed in Sparx Enterprise Architect and is the authoritative source of the UCS Ar

12、chitectural Model. This configuration item is an archive (zip) file. It includes the AS6518-MODEL.eap file. The zip file includes the following contents: AS6518-LICENSE.txt AS6518-README.txt AS6518 UG.pdf AS6515-MODEL.eap AIR6518 LICENSE.txt provides the data distribution and permitted usage stateme

13、nt. AS6518 README.txt describes the version history and contents of the archive (zip) file. This document, the AIR6518 User Guide, AS6518 UG.pdf, describes the content of the AS6518-MODEL.eap file, and how to use this content within the EA environment. 3.2 Upper Level Package Structure The high-leve

14、l package structure for AS6518 is shown in Figure 1. The Model has three top level packages: NOTICES, UCS Architecture Technical Governance, and UCS Architectural Model. Figure 1 - AS6518 packages The NOTICES package contains data distribution statements in the form of notes. The UCS Architecture Te

15、chnical Governance package provides material in support of the authoritative document AS6522. The authoritative UCS Architectural Model package comprises four packages: The Service Contract and Non-Functional Property Model, the System Use Case Model, the Domain Participant Model, and the Informatio

16、n Model. The UCS services are described by the service packages within the Domain Participant Model. A list of the service packages is provided in Appendix A. Figure 2 - AS6518 UCS architectural model packages Further information on the UCS Architectural Model and derived ICD work products is provid

17、ed in 6.2 Architectural Model and ICD. SAE INTERNATIONAL AS6518 Page 3 of 3 4. PRECONDITIONS FOR USING THE AS6518 EA MODEL Preconditions for using the AS6518 EA Model include experience with Enterprise Architect 10 or higher. experience with the Unified Modeling Language (UML) installation of the UC

18、S_MDG.xml add in for Sparx Enterprise Architect per instructions below 5. INSTALLATION AND USE The following steps will provide a working Enterprise Architect model. Unpack the AS6518.zip archive into a working directory. Open the AS6518-MODEL.eap file in Enterprise Architect. Then select Tools/MDG

19、Technology Import. Browse to the UCS_MDG.xml file in the working directory and click OK. EA11 and later: You can choose whether to import the MDG file into your user %APPDATA% area where it will be available in all models, or import just into this model file. Do not do both. If you do, the MDG profiles will not work correctly. Restart Enterprise Architect. PREPARED BY SAE SUBCOMMITTEE AS-4UCS, UNMANNED AIRCRAFT SYSTEM CONTROL SEGMENT OF COMMITTEE AS-4, UNMANNED SYSTEMS