SAE AIR 6519-2016 UxS Control Segment (UCS) Architecture UCTRACE (Includes Access to Additional Content).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/AIR6519 AEROSPACE INFORMATION REPORT AIR6519 Issued 2016-12 UxS Control Segment (UCS) Architect

5、ure: UCTRACE RATIONALE This document is the SAE publication of the Department of Defense UAS Control Segment (UCS) Architecture: Use Case Trace (UCTRACE) Version 3.4(PR) approved for Distribution A public release 15.S-1859. 1. SCOPE The Use Case Trace (UCTRACE) is SAE publication AIR6519 of the Depa

6、rtment of Defense Unmanned Control Segment (UCS) Architecture. This document is the SAE publication of the Department of Defense UAS Control Segment (UCS) Architecture: Use Case Trace (UCTRACE) Version 3.4(PR) approved for Distribution A public release 15.S-1859. This information is produced from a

7、script run against the System Use Case Model contained in the UCS Architecture Model AS6518-MODEL.eap configuration item. The System Use Case Model includes, at its lowest level of elaboration, use cases Level 2/3 (L2/L3) that describe specific scenarios of message exchanges between Actors and inter

8、nal system Participants via ServiceInterfaces. These message exchanges provide a way to create detailed traces that answer the question: “What UCS service interfaces must my components implement to satisfy functional requirements represented by a given Level 2/3 UCS use case?” The AIR6519-UCTRACE sp

9、readsheet contains trace information derived directly from the message sequences in the L2/L3 use cases. 2. REFERENCES There are no referenced publications specified herein. 3. LEGEND The information on the Data worksheet is produced directly from the corresponding released AS6518-MODEL System Use C

10、ase Model. This model is available in the release library as the Enterprise Architect file AS6518-MODEL.eap (the Document History specifies which version this AIR6519-UCTRACE product derives from). The UseCase2ServiceInterface script visits each of the lowest level “leaf“ UseCases and extracts speci

11、fic information about which ServiceInterfaces must be provided by one or more participants to accomplish the UseCase. “Leaf“ UseCases represent the lowest level of UseCase decomposition, where sequence diagrams show actual interaction of participants via ServiceInterfaces. Usually these are Level 3

12、(L3) UseCases, but Level 2 (L2) UseCases are included if the UseCases have a tagged value “isLeafUseCase“ = “True“. SAE INTERNATIONAL AIR6519 Page 2 of 2 Data Column Name Column Description Domain The top-level domain for the UseCase. Sub domain The sub domain the UseCase is part of. Use Case Name o

13、f the UseCase. ServiceInterface Name of a ServiceInterface that some participant must provide to enact the UseCase. Interface Name of an Interface the ServiceInterface provides. Operation Name of the Interface operation used for this UseCase. Stereotype Stereotype indicates that an informative opera

14、tion is included in the sequence diagram as a relevant task or information but is not a message from the UCS Message set. Seq Sequence numbers that indicate which distinct Sequence Diagram the entry comes from (the 1000s digit) and the position of the specific operation/message in that sequence diag

15、ram. Parameters The parameter type for the Operation. Some elements in the ServiceInterface column have names that begin with colons. Some of these elements represent infrastructure services, like :File Transfer Service in the L2 Provide Feature Data sequence diagram. These services do not have serv

16、ice interfaces, but instead are represented as Components in an adjacent subpackage. Since these components do not have defined interfaces, the Interface column has the keyword informative. Other elements do represent instances of Participants that have ServiceInterfaces, like “:Feature” in the L2 P

17、rovide Feature Data sequence diagram. However, in these sequence diagrams, the specified Operation name is an informative placeholder for an internal message to self or an external message from an actor or subsystem which has not been modeled in UCS. These informative placeholder messages do not hav

18、e a corresponding ServiceInterface or ServiceInterface operation. These rows of the table also have the keyword informative in the Interface column. When the Interface name is a concatenation of the ServiceInterface name with Notifications, as in SensorPayloadOperatorActorNotifications, the name sho

19、wn in the Operation column is a representative name for the type of information being passed to the Actor. On these rows of the Data sheet, the Operation name does not represent the name of a message in the UCS Message Set. 4. NOTES 4.1 Revision Indicator A change bar (l) located in the left margin

20、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 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