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/AIR6517 AEROSPACE INFORMATION REPORT AIR6517 Issued 2016-12 Unmanned Systems (UxS) Control Segm
5、ent (UCS) Architecture: Rhapsody Version of UCS ICD Model RATIONALE This document is the SAE publication of the Department of Defense UxS Control Segment (UCS) Architecture: Rhapsody Version of the UCS ICD Model (UCS-INF-ICD-RPY) Version 2.4(PR) approved for Distribution A, public release 15.S-1859.
6、 FOREWORD The 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 Rhapsody version of the UCS Architectural ICD Model and how to use this model within the Rhaps
7、ody modeling tool environment. 1. SCOPE This User Guide describes the content of the Rhapsody version of the UCS Architectural Model and how to use this model within the Rhapsody modeling tool environment. The purpose of the Rhapsody version of the UCS Architectural Interface Control Document (ICD)
8、model is to provide a model for Rhapsody users, derived from the Enterprise Architect (EA) model (AIR6515). The AIR6515 EA Model, and by derivation, the AIR6517 Rhapsody Model, have been validated to contain the same content as the AS6518 model for: all UCS ICD interfaces all UCS ICD messages all UC
9、S ICD data directly or indirectly referenced by ICD messages and interfaces the Domain Participant, Information, Service and Non-Functional Properties Models SAE INTERNATIONAL AIR6517 Page 2 of 7 2. REFERENCES There are no references publications specified herein. 3. DIFFERENCES COMPARED WITH THE UC
10、S ARCHITECTURE AS6518 MODEL Compared with AS6518 Model, the AIR6517 Rhapsody 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 System Model, which is not a norma
11、tive 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 navigability correctly for associ
12、ation 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 AIR6517 Rhapsody Model content is equivalent to the corresponding AS6518 Model content. In the AS6518
13、 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 references UCS logical messages and data model elements. In AIR6515 EA Model, both sets of interfaces
14、would be identical, so only the Domain Participant Model interfaces are provided. Figure 1 shows how AIR6515 relates to other UCS Architecture products. Figure 1 - Relationships among SAE products SAE INTERNATIONAL AIR6517 Page 3 of 7 4. RELATIONSHIP TO AIR6515 EA AND AIR6516 RSA MODELS The AIR6517
15、Rhapsody Model is meant to be the same model as those ICD models provided for Enterprise Architect and Rhapsody. Figure 2, excerpted from the UCS Model Interchange Guide (UCS-G-MIG), shows how AIR6515 is used to produce the AIR6516 and AIR6517 products. Figure 2 - Workflow for generating model produ
16、cts 5. CONTENT OF THE AIR6517 RHAPSODY MODEL Figure 3 describes the content of the upper level package structure. In Rhapsody this structure is laid out in alphabetical order so it will not be in the exact same order as the EA Model. Also note that since the order is arbitrary there is no special me
17、aning implied. The next sections will provide screen shots of the lower level package structure and a brief explanation of each. The UCS Working Group Release 3.4 of the UCS Architecture used the part number UCS-INF-ICD-RPY for this product, and that old part number is still used in the SAE re-publi
18、cation of the Release 3.4 Architecture. 5.1 UCSArchitecturalModel The UCSArchitecturalModel package contains the AIR6515 EA Models Domain Participant, Information, and Service Contract and Non-Functional Property Models. SAE INTERNATIONAL AIR6517 Page 4 of 7 Figure 3 - Top-Level package structure 5.
19、2 DomainParticipantModel The DomainParticipantModel contains the definitions of the UCS ServiceInterfaces and the interfaces that they use and realize to provide services. Figure 4 - Domain Participant Model SAE INTERNATIONAL AIR6517 Page 5 of 7 5.3 InformationModel The InformationModel contains the
20、 same content as the AIR6515 EA Models Information Model package. This includes the DataProducts and LogicalDataModel packages. Figure 5 - Information Model 5.4 ServiceContractandNon_FunctionalPropertyModel This Model contains the same information as the AIR6515 EA Models package, including NFP libr
21、aries for Safety, Security, and QoS. SAE INTERNATIONAL AIR6517 Page 6 of 7 Figure 6 - Service Contract and Non-Functional Property Model 6. PRECONDITIONS FOR USING THE AIR6517 RHAPSODY MODEL Preconditions for using the AIR6517 Rhapsody Model include: experience with the Rhapsody Modeling Tool Enviro
22、nment version 8.1 or higher. This product was validated using Rational Rhapsody Architect for System Engineers, version 8.1.1. experience with the Unified Modeling Language (UML) an understanding of the UCS Architectural Model as originally created in the EA model AS6518-MODEL. 7. FEATURES OF AS6518
23、 UCS ARCHITECTURE MODEL NOT EXPORTED TO AIR6517 The System Use Case Model is not provided in AIR6517. Consult the AS6518 Enterprise Architect model for information on system use cases. A free version of Enterprise Architect available from Sparx Systems allows for reading and navigating the EA model.
24、 8. TECHNICAL NOTES 8.1 Missing Diagram Elements The translation of the UCS Architectural Model from Enterprise Architect to Rhapsody includes diagrams; however, there may be cases where elements are not completely translated to the diagram. In general, every element is in the model and can be re-ad
25、ded to a diagram with a drag and drop or assignment through a Rhapsody dialog box. This is especially true for ports. If an element is missing a port and its associated interface(s), you can create a new port and add the missing interface from the list of interfaces in the port select interface dial
26、og box. All of the interfaces from the AIR6515 EA Model should exist in this dialog box as shown in the Figure7. SAE INTERNATIONAL AIR6517 Page 7 of 7 Figure 7 - Port dialog box 9. NOTES 9.1 Revision Indicator A change bar (I) located in the left margin is for the convenience of the user in locating
27、 areas where technical revisions, not editorial changes, have been made to the previous issue of this document. 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 AIRCRAFT SYSTEM CONTROL SEGMENT OF COMMITTEE AS-4, UNMANNED SYSTEMS
