Search Results

The Use Case Trace (UCTRACE) is SAE publication AIR6519 of the Department 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 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 internal 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?”

This platform specific Interface Control Document (ICD) provides an example mapping to the Object Management Group’s (OMG) Data Distribution Service (DDS) infrastructure middleware. The mapping is based on the Unmanned Systems (UxS) Control Segment (UCS) Architecture: Model, AS6518. A series of non-normative implementation choices have been made that are specific to this ICD. These implementation choices may not be appropriate for different system implementations. The machine readable ICD and result of this mapping and implementation choices are provided with AIR6521. Use and understanding of this document assumes a working knowledge of the UCS Architecture, the model structure and its contents.

Governance of the Unmanned Aircraft System (UAS) Control Segment (UCS) Architecture was transferred from the United States Office of the Secretary of Defense (OSD) to SAE International in April 2015. Consequently, a subset of the UCS Architecture Library Release 3.4(PR) has been published under SAE as the Unmanned Systems (UxS) Control Segment (UCS) Architecture, AS6512. This Version Description Document (VDD) describes the correspondence and differences between the two architecture libraries.

Governance of the Unmanned Aircraft System (UAS) Control Segment (UCS) Architecture was transferred from the United States Office of the Secretary of Defense (OSD) to SAE International in April 2015. Consequently, a subset of the UCS Architecture Library Release 3.4(PR) has been published under SAE as the Unmanned Systems (UxS) Control Segment (UCS) Architecture, AS6512. This Version Description Document (VDD) describes the correspondence and differences between the two architecture libraries.

This revision of AS6513 concerns conformance to the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture Revision B, designated AS6512B (or later). The superseded AS6513A concerned conformance to the previous UCS Architecture, designated AS6512A. This document is the authoritative specification within the UCS Architecture for establishing conformance requirements for UCS products. The conformance of UCS products is determined by assessing the conformance of the UCS Product Description to the UCS Architecture. The UCS Product Description includes test artifacts.

The scope and purpose of the UCS Architecture Library Revision A is provided in AS6512™A. The scope of this document is to identify the elements of the UCS Architecture Model Revision A as distributed in the AS6518A.zip file, establish the terms and conditions and user license agreement for the architecture model, and provide other metadata.

This brief User Guide recaps the content of the AS6518B UCS Architectural Model. 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 AS6512B UCS Architecture: Architecture Description.