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/AIR6515 AEROSPACE INFORMATION REPORT AIR6515 Issued 2016-12 Unmanned Systems (UxS) Control Segm
5、ent (UCS) Architecture: EA Version of UCS ICD Model RATIONALE This document is the SAE publication of the Department of Defense UxS Control Segment (UCS) Architecture: EA Version of the UCS ICD Model (UCS-INF-ICD-EA) Version 2.4(PR) approved for Distribution A public release 15.S-1859. FOREWORD The
6、Unmanned Systems (UxS) Control Segment (UCS) Architecture is described in AS6512 UxS Control Segment (UCS) Architecture: Architecture Description. This User Guide describes the content of the Enterprise Architect (EA) version of the UCS Architectural ICD Model and how to use this model within the EA
7、 modeling tool environment. 1. SCOPE This User Guide describes the content of the Enterprise Architect (EA) version of the UCS Architectural Model and how to use this model within the EA modeling tool environment. The purpose of the EA version of the UCS Architectural Interface Control Document (ICD
8、) model is to provide a working model for Enterprise Architect tool users and to serve as the source model for the Rational Software Architect (RSA) and Rhapsody models (AIR6516 and AIR6517). The AIR6515 EA Model has been validated to contain the same content as the AS6518 model for: all UCS ICD int
9、erfaces all UCS ICD messages all UCS ICD data directly or indirectly referenced by ICD messages and interfaces the Domain Participant, Information, Service, and Non-Functional Properties Models 2. REFERENCES There are no referenced publications specified herein. SAE INTERNATIONAL AIR6515 Page 2 of 5
10、 3. DIFFERENCES COMPARED WITH THE UCS ARCHITECTURE AS6518 MODEL Compared with AS6518 Model, the AIR6515 EA Model: does not include the full EA Conceptual Data Model, which contains some elements that are only referenced during elaboration of non-UCS message sets does not include the EA Use Case Syst
11、em Model, which is not a normative part of the AIR6514 UCS Interface Control Document (ICD) does not include Refinements elements or elements of the ICD that are not directly or indirectly referenced by UCS messages modifies association end role names required for navigable association ends sets nav
12、igability correctly for association ends without role names The AIR6515 EA Model was produced per the Model Interchange Guide (UCS-G-MIG), an internal committee process document, and was validated per those processes so that the AIR6515 EA Model content is equivalent to the corresponding AS6518 Mode
13、l content. In the AS6518 Model there are two sets of interfaces, one set of interfaces in the Domain Participant Model references messages that use Conceptual Data Model elements and the other set of interfaces in the ICD Model reference UCS logical messages and data model elements. When the Concept
14、ual message model is transformed to the Logical message model, the two sets of interfaces are identical. So in the AIR6515 EA Mode only the logical Domain Participant Model interfaces are provided. Figure 1 shows how AIR6515 relates to other UCS Architecture products. Figure 1 - Relationships among
15、SAE products 4. RELATIONSHIP TO AIR6516 RSA AND AIR6517 RHAPSODY MODELS The AIR6515 EA Model is the source model from which Rational Software Architect and Rhapsody models are derived. Figure 2, excerpted from the UCS Model Interchange Guide (UCS-G-MIG), shows how AIR6515 is used to produce the AIR6
16、516 and AIR6517 products. SAE INTERNATIONAL AIR6515 Page 3 of 5 Figure 2 - Workflow for generating model products 5. CONTENT OF AIR6515 EA MODEL Figure 3 shows the content of the upper level package structure. Figure 3 - Upper-Level package structure SAE INTERNATIONAL AIR6515 Page 4 of 5 The UCS Arc
17、hitectural Model package contains the AS6518 Model Domain Participant, Information, and Service Contract and Non Functional Property Models. The Service Contract and Non-Functional Property Model contains the same information as the AS6518 Models package, including NFP libraries for Safety, Security
18、, and QoS. The Domain Participant Model package contains the definitions of the UCS ServiceInterfaces and the interfaces that they use and realize to provide services. The Information Model contains the same content as the AS6518 Models Information Model package. This includes the Data Products and
19、Logical Data Model packages. NOTE: In this model the UCS Interface ICD/Services package has been renamed MessageModel to reflect that it no longer contains duplicated interfaces and only contains messages. 6. PRECONDITIONS FOR USING THE AIR6515 EA MODEL Preconditions for using the AIR6515 EA Model i
20、nclude: experience with Enterprise Architect 10 or higher experience with the Unified Modeling Language (UML) an understanding of the UCS Architectural Model as originally created in the EA Model AS6518 Model installation of the UCS_MDG.xml add-in for Sparx Enterprise Architect 7. INSTALLATION AND U
21、SE The following steps will provide a working Enterprise Architect model. Unpack the AIR6515.zip archive into a working directory. Open the AIR6515.eap file in Enterprise Architect. Select Tools/MDG Technology Import. Browse to the UCS_MDG.xml file in the working directory and click OK. Note that in
22、 EA12, MDG Technology Import is under the Project menu. 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. Rest
23、art Enterprise Architect. Figure 4 SAE INTERNATIONAL AIR6515 Page 5 of 5 8. NOTES 8.1 Revision Indicator A change bar (I) located in the left margin is for the convenience of the user in locating areas where technical revisions, not editorial changes, have been made to the previous issue of this doc
24、ument. An (R) symbol to the left of the document title indicates a complete revision of the document, including technical revisions. Change bars and (R) are not used in original publications, nor in documents that contain editorial changes only. PREPARED BY SAE SUBCOMMITTEE AS-4UCS, UNMANNED SYSTEMS CONTROL SEGMENT OF COMMITTEE AS-4, UNMANNED SYSTEMS
