Transcription
UNCLASSIFIEDUAS Control Segment (UCS)Technical OverviewBrian SchechterApplication Architecture Subcommittee ChairUCS Working GroupAugust 18, 2011UNCLASSIFIED
UNCLASSIFIEDOA UCSAcquisitionObjectivesArchitectureGoalsUtilizing an Open, Standards-Based Service-OrientedArchitecture (SOA) approach , the UCS Architecture willenhance: Operational and Acquisition Efficiencies System-to-System Interoperability Warfighter CapabilityUCS Architecture does not currently cover: Low-level C2 interface between UAVs and groundstations as existing standards such as STANAG 4586provide standardization path-forward in this area Human-Machine Interfaces (HMIs)UNCLASSIFIED2
UNCLASSIFIEDUCS ArchitectureTime LineTime LineStt iStructuringFeb 2009ADM2009ConceptpExplorationDec 2009Version 0.5Incl. AV-1Architecture Definition and DemonstrationNov 2010IWP DemoMar 2011JSIL DemoJune 2010Version 1.0Architecture Modeling1QFY12Version 2.1Current Focus3UNCLASSIFIED3
sApplication Architecture ModelServicesServicesServicesServicesServices ViewsService Domain 1 Service Domain 2Service Domain 3 Service Domain 4Technical ArchitectureAbstractionOperating Environment, Development Environment, CertificationEnvironmentStandards / CertificationViewsReference ArchitectureIA andSecurityManagementApplication 1Application 2Application 3Application eGuest OSGuest OSGuest OSGuest OSGuest OSSystem ViewsEmbedded Hypervisor and Separation KernelMulti-Core ProcessorImplementation ArchitecturesDeployment ViewsUNCLASSIFIED4
ArchitectureExecutive ApplicationBoard ProvidesMgmt & GuidanceUNCLASSIFIED UCS Working Group Executive MgmtIntegrated Master ScheduleWorking Group ScorecardsWorking Group Plenary MeetingsInterface with OSD UCS Steering GroupAV-1 Program of Work Terms of Reference Business ProcessesConfiguration Control Board (CCB) Change Request (CR) Management Document Release ApprovalArchitecture Guidance Document Architecture Overview and Rationale ImplementationI lt ti GuidanceG idandd LessonsLLearnedLd External Communicationg Materials, ResourcesBriefingPublic WebsitePresentations and MeetingsOpen Business Model (OBM)UNCLASSIFIED5
OSDUCSWorkingGroupSubcommittees Perform the Technical itecturesData ModelComputingInfrastructureIAM3 ArchitectureExperimentsMission ControlSecurity Mgmt& IASystem eServicesDynamicAirspaceMDA ProcessExternalMessaging &CommunicationPayloadP dProductPED Subcommittees form Task Groupsto perform well-defined portions oftheir work Task Groups exist until these tasksare completedl t dSystem UseCasesUNCLASSIFIED6
UNCLASSIFIEDApplication ArchitectureSubcommitteeSubcommittee2: ApplicationArchitectureDefine and developarchitecture for command andp a common,, openp and scalable applicationppSystem (UAS)Use Casescontrol of Unmanned Aircraft SystemsGroup 2 through Group 5 at Platform IndependentModel (PIM) level using OMG Model Driven Architecture (MDA)System Use Cases Mission-Level Use Case and Scenario Textual Descriptions Mission-Level Use Case Diagrams (UML) System-Level Activity / Sequence Diagrams (UML)Data Model() Data Meta-Model (UML) Logical Data Model (UML) Logical Data Model to Interface Data Model Projections (UML) Domain ArchitectureUCS Architecture partitioned into Domains based on Subject MatterDomain / Sub-domain Textual DescriptionsDomain-Level Use Cases and Activity / Sequence Diagrams (UML)SService-Leveli Ll TextualT t l DescriptionsDi tiService-Level Interfaces (SOAML)7UNCLASSIFIED7
UNCLASSIFIEDPlatform ArchitectureSubcommitteeSubcommittee2: ApplicationArchitectureDefine and develop an implementation architecture for a flexible, technology-neutralinfrastructure for UCS that: Implementsand Casesdistributes Application Service Interfaces and DataSystem UseModels; Provides a safe/secure computer architecture, reusable PSM mappings to supportingmiddleware, OS, and hardware; Supports composability of mission services, referenceimplementation, and testing.Computing Infrastructure Core API Standards (CAPIS) DODAF viewpoint StdV-1 Standards ProfileSecurity Management & Information Assurance Security and Information Management Use Cases (UML) System Security and Information Assurance Management Plans (IAMP)Infrastructure Services and Configuration Infrastructure Services PIM (UML) Definition of underlyingy g Platform Technologiesg System Configurability RequirementsMDA Process MDA Process Guidance PIM to PSM Transformation ExamplesUNCLASSIFIED8
UNCLASSIFIEDCertification rchitectureIdentify the best technical approaches for Certification (Information Assurance,Assurance System Safetyand Airworthiness) for the UCS SystemArchitecturerelative to DoD Certification guidance; assess theUse CasesUCS Architecture relative to these DoD Certification considerations; and propose changes to theUCS Architecture where Certification deficiencies are identified.Information Assurance (IA) Information Assurance Management Plan (IAMP) Canonical Information Assurance Case (Goal Structured Notation)System Safety and Airworthiness Data Meta-Model (UML) Logical Data Model (UML) LogicalL i l DataD t ModelM d l tot InterfaceI t fDataD t ModelM d l ProjectionsP j ti(UML)UNCLASSIFIED9
UNCLASSIFIEDArchitecture ImplementationSubcommittee2: ApplicationSubcommitteeArchitectureAddress aspects related to the implementation of the UCS architecture, including : Developing areference architecture or architectures;Definingexperiments to aid in the validation of the UCSSystem UseCasesarchitecture; Determining conformance of systems and services to the UCS architecture.System Architectures ReferenceR fAArchitecturehit t Reference Implementations Dismounted User Transportable/Mobile System Fixed Facility Implementation Lessons LearnedExperimentsAV 1 Experiments defined to validate Architecture Quality Attributes in AV-1Conformance Data DictionaryOpen Architecture Assessment ToolGuidance on measuring Program of Record (PoR) complianceG idGuidanceon program ‘on-ramps’‘’Component Specification TemplateUNCLASSIFIED10
UNCLASSIFIEDDevelopmentTools SubcommitteeSubcommittee2: ApplicationArchitectureProvides guidanceguidance, recommendations,recommendations and implementations of tools for use in the Model DrivenEngineering approach adopted Systemby the UCS-WG.This includes tools for specifying, analyzing,Use Casesdeveloping, and implementing the UCS 2.0 Architecture. The scope of this activity includes UMLdevelopment tools, code generation capabilities, model import/export, and configurationmanagement.M3 Architecture Common Development Environment (tools) for UCS Architecture Based on OMG Model Driven Architecture (MDA) ApproachConfiguration, Change and Data Management Architecture Governance Processes11UNCLASSIFIED11
2.12.1Scheduled22, 2011Volunteer OrganizationsFunded OrganizationsHASHeterogeneous mix of 17 funded companiesUNCLASSIFIED12
reference architecture or architectures; DefiniSystem Use Casesng experiments to aid in the validation of the UCS architecture; Determining conformance of sy stems and services to the UCS architecture. Rf Ahitt System Architectures Reference Architecture Reference Implementations Dismounted User Transportable/Mobile System Fixed Facility
