Refine Your Search

Search Results

Viewing 1 to 10 of 10
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: Conformance Specification

2016-12-20
CURRENT
AS6513
This document is the authoritative specification within the SAE Unmanned Systems (UxS) Control Segment (UCS) Architecture for establishing conformance requirements for UCS products. The UCS products addressed by this specification are UCS software components and UCS software configurations that provide one or more UCS services, and UCS systems that employ one or more UCS services. 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.
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: Data Distribution Service (DDS)

2016-12-20
CURRENT
AIR6521
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.
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: EA Version of UCS ICD Model

2016-12-20
CURRENT
AIR6515
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) 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 interfaces 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
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: RSA Version of UCS ICD Model

2016-12-20
CURRENT
AIR6516
This User Guide describes the content of the Rational Software Architect (RSA) version of the UCS Architectural Model and how to use this model within the RSA modeling tool environment. The purpose of the RSA version of the UCS Architectural Interface ICD model is to provide a model for Rational Software Architect (RSA) users, derived from the Enterprise Architect (EA) ICD model (AIR6515). The AIR6515 EA Model, and by derivation, the AIR6516 RSA Model, have been validated to contain the same content as the AS6518 model for: all UCS ICD interfaces 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
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: Rhapsody Version of UCS ICD Model

2016-12-20
CURRENT
AIR6517
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) 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 UCS ICD data directly or indirectly referenced by ICD messages and interfaces the Domain Participant, Information, Service and Non-Functional Properties Models
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: UCS Architecture Model

2018-06-24
WIP
AS6518A

This brief User Guide recaps the content 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: Architecture Description.

Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: UCS Architecture Model

2016-12-20
CURRENT
AS6518
This brief User Guide recaps the content 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: Architecture Description.
Standard

Unmanned Systems (UxS) Control Segment (UCS) Architecture: Version Description Document

2016-12-20
CURRENT
AIR6520
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.
Standard

UxS Control Segment (UCS) Architecture: UCTRACE

2016-12-20
CURRENT
AIR6519
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?”
X