AADL ANNEX FOR THE FACE™ TECHNICAL STANDARD, EDITION 3
Transcript of AADL ANNEX FOR THE FACE™ TECHNICAL STANDARD, EDITION 3
Copyright2018AdventiumLabs. 1
AADLANNEXFORTHEFACE™TECHNICALSTANDARD,EDITION3.0DISTRIBUTIONA.Approvedforpublicrelease:distributionunlimited.ThismaterialisbaseduponworksupportedbyU.S.ArmyResearchDevelopmentandEngineeringCommand,AviationDevelopmentDirectorateunderContractNo.W911W6-17-D-0003.Anyopinions,findingsandconclusionsorrecommendationsexpressedinthismaterialarethoseoftheauthor(s)anddonotnecessarilyreflecttheviewsoftheU.S.ArmyResearchDevelopmentandEngineeringCommand,AviationDevelopmentDirectorate.ExceptformaterialownedbyTheOpenGroupasdefinedbelow,AdventiumLabs,soleownerofthecopyrightofthismaterial,herebygrantstotheSAEInternationalpermissiontochange,modify,andotherwiseutilizematerialsinthisdocument,inwholeorinpart,tomeetitsgoalsandobjectivesrelatedtotheAADLStandard.AdventiumLabsfurthergrantsSAEInternationalpermissiontocopyrightfutureversions,includingthefinalstandard,asSAEInternationalcopyrightedmaterial.Thislicensegrantdoesnotextendto,andexpresslyexcludes,materialscopyrightedbyotherparties,suchasTheOpenGroup.AdventiumLabsacknowledgesTheOpenGroupforpermissiontoincludetext/figuresderivedfromitscopyrightedFutureAirborneCapabilityEnvironment(FACE)TechnicalStandard,Edition3.0,©2017TheOpenGroup.FACE™andtheFACE™logoaretrademarksofTheOpenGroupintheUnitedStatesandothercountries.
Copyright2018AdventiumLabs. 2
AADLANNEXFORTHEFACE™TECHNICALSTANDARD,EDITION3.0.........................................3
TYPOGRAPHYCONVENTIONS...................................................................................................3
A. RATIONALE.......................................................................................................................3
B. BACKGROUNDANDASSUMPTIONS..................................................................................3
C. REFERENCEEXAMPLE.......................................................................................................8
D. PACKAGING......................................................................................................................9
E. DATAMODEL..................................................................................................................10
F. DATAMODELVIEWS.......................................................................................................11
G. UOPMODEL...................................................................................................................12
H. TSS.................................................................................................................................16
I. ROUTING.........................................................................................................................16
J. IOSS.................................................................................................................................19
K. FACEHEALTHMONITORINGANDFAULTMANAGEMENT(HMFM)..................................20
L. FACEPROFILES................................................................................................................20
M. FACELIFECYCLEMANAGEMENT.....................................................................................20
N. FACEARTIFACTPARSINGGUIDE.....................................................................................20
O. FACEPROPERTYSET.......................................................................................................21
Copyright2018AdventiumLabs. 3
AADLAnnexfortheFACE™TechnicalStandard,Edition3.0Version0.3.0,2018-04-04
TypographyConventionsRegularTextAADL Keyword FACEKeywordIntroductionFACEKeyword
A. Rationale1) Thisannexisintendedtohelpcomponentvendorsandsystemintegratorsusingthe
(FutureAirborneCapabilityEnvironment)FACETechnicalStandard.FACETechnicalStandardEdition3.01providesadatamodelingarchitecturebutdoesnotprovidemechanismsfordescribingcomponentbehaviorortimingproperties.ThisdocumentprovidesguidancefortranslatingaFACEStandardEdition3.0DataArchitectureXMImodel2intoAADLsothatbehaviorandtimingpropertiescanbeaddedandanalyzed.a) SeesectionJ.6oftheFACETechnicalStandardEdition3.0forObjectConstraint
LanguagespecificationsfortheDataArchitecture.2) Thisannexsupportsthemodeling,analysis,andintegrationofFACEartifactsin
AADL.ItgivesAADLstyleguidelinesandanAADLpropertysettoprovideacommonapproachtousingAADLtoexpressarchitecturesthatincludeFACEcomponents.UsingcommonpropertiesandcomponentrepresentationsinAADLmakesAADLmodelsofFACEcomponentsportableandreusableandincreasestheutilityoftoolsthatoperateonsuchAADLmodels.
B. BackgroundandAssumptions3) ThisdocumentprovidesamappingforFACETechnicalStandardEdition3.0and
AADL2.2.4) TheFACETechnicalStandardprovidesaframeworkfordataarchitecturethat
enablesserviceandapplicationportabilityacrossplatformsbyrequiring
1Unlessexplicitlynoted,allreferencestotheFACETechnicalStandardinthisdocumentrefertoEdition3.0.2TheFACETechnicalStandardEdition3.0providesadataarchitecturemetamodelinanEMOFinsectionJ.5.
Copyright2018AdventiumLabs. 4
conformancetotheFACETechnicalStandard’sdatamodelingandsoftwareguidelines.a) AsillustratedinFigure2,theFACETechnicalStandardisdividedintolayers.
IndividualapplicationsorservicesthatresideinoneoftheselayersarecalledUnitsofPortability(UoPs3).UoPsinthePortableComponentsSegment(PCS)andthePlatformSpecificServicesSegment(PSSS)communicatewithoneanotherusingaTransportServiceSegment(TSS)library.ThePCScontainsgeneral-purposeapplications,whilethePSSSisolatesUoPsthatinteractwithdevicesthroughtheI/Osegment(IOS).TheTSSisanabstractgroupingofcomponents(includinglibraries)thatprovidedataexchangerelatedfunctionality.
b) CommunicationbetweenUoPsisaccomplishedusingparametersdictatedbyviews.ViewsandareconstructedfromaFACEdatamodelusingqueries.
c) InasystembuiltfromFACEconformantsoftware,thereisasingledataarchitecturemodel.ThisdataarchitecturemodeliscomposedbythesystemintegratorusingdatamodelsassociatedwitheachUoPinthesystem.
d) Thefieldsthatmakeupeachinter-UoPmessagearetakenfromthedatamodel.Eachfieldineachmessageisassociatedwithahierarchyofdatamodelelements.ThismeanstwoUoPsthatdonotneedtousepreciselythesamedatarepresentation(e.g.,metricorimperial)tocommunicatewithoneanother.i) ForfurtherinformationabouttheFACEDataArchitecture,seesection2.3of
theFACETechnicalStandard.5) TheFACETechnicalStandarddataarchitectureisdividedintothreelayers:TheData
Model,UoPModel,andtheIntegrationModel(seeFigure1).Thisdocumentprovidesguidanceforallthree.
3TheFACETechnicalStandarddefinestwoequivalentterms,UnitofPortability(UoP)andUnitofConformance(UoC).Thisdocumentusestheformer,asFACEconformanceisnotinthescopeofthisannex.
Copyright2018AdventiumLabs. 5
6) TheFACETechnicalStandarddatamodelprovidesarealizationhierarchyformultiplelevelsofdatadescription(conceptual,logical,andplatform).MostAADLanalysesarenotexpectedtorequirethatmultiplelevelsoftheFACETechnicalStandarddatamodelaremappedtoAADL.
a) Figure1DataArchitecture(extractedfromFACETechnicalStandardEdition3.0)
Copyright2018AdventiumLabs. 6
7) AllcommunicationbetweentheFACEUoPsthatresideinthePCSorPSSSlayersisconductedviatheTSSinterfaceaccordingtoViewsdefinedintheDataModel(asshowninthetopandrightofFigure2).
8) InadditiontoitsdatamodelingapproachtointeroperabilityofUoPs,theFACETechnicalStandardalsoprovidesoperatingsysteminterfacespecificationsandI/Odeviceinterfacespecifications.I/OdeviceaccessisrepresentedintheFACEIOSS(I/OServiceSegment).TheoperatingsysteminterfaceisrepresentedintheFACEOSS(OperatingSystemSegment).SeetheleftandbottomofFigure2.
a) Figure2ArchitectureSegmentsExample.(ExtractedfromFACETechnicalStandardEdition3.0)
9) ThetermsspecifictotheFACETechnicalStandardusedinthisannexaredefinedbelow:a) FACE(FutureAirborneCapabilityEnvironment):Agovernment-industry
softwarestandardandbusinessstrategyforacquisitionofaffordablesoftwaresystemsthatpromotesinnovationandrapidintegrationofportablecapabilitiesacrossglobaldefenseprograms.TheFACEStandardalsoprovidesadatamodelinglanguageusedtodescribecomponentinterfaces.
b) FACEConformance:Asoftwarecomponent(UnitofConformance(UoC))iscertifiedasFACEconformantwhenithassuccessfullybeenthroughanindependentverificationandcertificationprocess,whichisdefinedbytheFACEConformanceProgram.ThisincludestechnicalverificationbyadesignatedVerificationAuthority(VA)subsequentcertificationbytheFACECertificationAuthority(CA),andregistrationintheFACELibrary.ThiscertificationrepresentsthatthesoftwareUoCmeetstherequirementsoftheFACETechnicalStandard,whichwasdesignedtofacilitatesoftwareportability.AFACEconformantdataarchitectureisa.facefilethatadherestotheFACETechnicalStandardEdition
Copyright2018AdventiumLabs. 7
3.0metamodel.Seesection1.5oftheFACETechnicalStandardformoreinformation.
c) DataArchitectureModel:ThewholeofFigure1describesthecontentsoftheDataArchitectureModel.i) EachsystemofintegratedFACEconformantUoPswillultimatelyhaveone
DataModel,likelycreatedfrommultipleinputdatamodels.d) DataModel:Asetofconceptual,logical,andplatformentitiesusedasthebasis
forviewdefinition.Eachplatformentityrefinesalogicalentity,andeachlogicalentityrefinesaconceptualentity.SeetopofFigure1.i) Example:“Temperature”isconceptual,“DegreesCelsius”islogical,and
“32bitunsignedinteger”isplatform.e) UoPModel:AdescriptionoftheUoPsinagivensystemofFACEconformant
componentsandtheirassociatedviewsandconnections.SeemiddleofFigure1.i) TheconnectionsdescribedintheUoPModeldonotdescribeinter-UoP
communication.TheyprovideonlytheUoP’sexpectationsofthetypeofconnectionitwillhavewhenintegrated(e.g.,sampling).
ii) AnintegratorwillcombinemultipleUoPModels(oneforeachintegratedUoP)intotheirintegratedUoPModel.
iii) Thistermisnotequivalentto“USM,”whichisdefinedlaterinthissection.f) IntegrationModel:AmodeldescribingthecompositionofFACEUoPsina
systemandtheinter-UoPmessageroutingintheTSS.SeebottomofFigure1.g) View:AFACEviewisdocumentationofaTSAPIdataparameterthatcanbe
passedintheTSInterface.Aviewiscomposedofelementsofadatamodelandisdescribedbyaquery.i) Example:Aview“status”mightincludealtitude,airspeed,andground
speed.ii) ViewsarenominallydefinedintheplatformlayeroftheDataModel.iii) Query:AFACEqueryisanSQL-likeexpressiondescribingfeaturesofthe
FACEdatamodeltouseinaview.iv) Template:AFACEtemplateisusedtospecifythepresentationofdataina
platformview.v) UoP(UnitofPortability):AlsocalledUnitofConformance(UoC).Useofthe
termUnitofPortabilityhighlightstheportableandreusableattributesofasoftwarecomponentorDomainSpecificDataModel(DSDM)developedtotheFACETechnicalStandard.
vi) EachUoPmayhaveanassociatedUSMprovidingitsdatamodeldefinitionandUoPModeldefinition.
h) UoC(UnitofConformance):ADSDMorasoftwarecomponentdesignedtomeettherequirementsforanindividualFACEsegment.UoCsmustbeverifiedasconformanttotheFACETechnicalStandardtobecertified.i) AllFACEcomponentsinthePCS,TSS,PSSS,andIOSSareUoCs.ii) UoCandUoPareequivalentterms.
Copyright2018AdventiumLabs. 8
i) TSS(TransportServiceSegment):ATSSisresponsibleforexchangingdatabetweenUoPs.ATSSisalsoresponsibleformediatingdatabetweenUoPsandotherdataexchangefunctions.i) Forexample,aTSSmighttranslatea“status”parametertoa“heartbeat”
parameterwiththesamefieldsbutdifferentunits(perhapsmetersinsteadoffeet).
ii) TheTSSisoftenshownasasignalentityindiagramsillustratingsystemsofFACEconformantsoftware(suchasFigure2)howeverthereisnorestrictionlimitingasystemtoasingleTSS.
j) FACESharedDataModel:AninstanceofaDataModelwhosepurposeistodefinecommonlyuseditemsandtoserveasabasisforallotherdatamodels.i) TheFACEshareddatamodelprovidescommonconceptssuchas
temperature.k) USM(UoPSuppliedModel):Adatamodelprovidedbyasoftwaresupplierthat
documentsthedataexchangedbyaUoPviatheTSinterface.AnintegratedsystemmayincorporatemanyUSMs.i) TheUSMisprovidedasa.facefilewitheachUoP.
l) IntegratedDataModel:TheintegratorofasystemusingFACEconformancecomponentscombinesFACEUSMstocreatetheIntegratedDataModelforthesystem.
m) FACEUoPVendor:AUoPvendorcreatesthesoftware,datamodel,andUoPmodelassociatedwithaUoP.ThedatamodelandUoPmodelaredeliveredwiththeUoPsoftware.
n) IntegratorofFACEconformancecomponents:TheintegratorofasystemusingFACEconformancecomponentsisastakeholderresponsibleforresolvingUSMsfromFACEUoPvendorsandforconfiguringaTSSthatroutesdatabetweenUoPs.
o) FACEUUID:EveryelementintheDataModelhasauniqueidentifiercreatedusingtheUUIDstandard.
p) UoPInstance:AUoPInstanceisaconfigurationitemdescribingaUoP’srole(s)inagivensystemconfigurationasdescribedbytheIntegrationModel.AsingleUoPmayhavemultipleinstancesinasystem.
q) UoPConnection:AUoPConnectiondescribestheUoP’sassumptionsaboutitsconnection.AUoPConnectiondoesnotidentifythesenderorreceiverontheotherendoftheconnection(SeeFigure7).
r) UoPEndPoint:AUoPEndPointdescribestheroutingconfigurationassociatedwithasingleUoPConnection(SeeFigure7).
C. ReferenceExample10) ThisannexusestheFACEBasicAvionicsLightweightSourceArchetype(BALSA)
exampleasapointofreference.BALSAsourcecodeandFACEmodelsareavailabletomembersofTheOpenGroupFACEConsortium.a) UnderstandingofBALSAisnotrequiredtousethisannex.
Copyright2018AdventiumLabs. 9
Figure3:BALSAmodeledinAADL
D. Packaging11) Thisannexdoesnotprovidespecificpackagingrequirements.However,modelers
areencouragedtocreateseparatepackages.a) OnepackagefortheDataModelb) OneormorepackagesforUoPsc) OnepackageforeachIntegrationModel
12) TheUSMsforeachUoPwillcontributebothtotheDataModelpackageandtotheUoPpackage(s).
13) ExampleFile Description Notes
data_model.aadl data anddata implementations correspondingtoFACEentitiesandviews
IOS.aadl thread groupsforIOSUoCs
OSS.aadl componentsfortheOSS PSSS.aadl thread groupsforPSSS
UoPs
PCS.aadl thread groupsforPCSUoPs
TSS.aadl abstract definingaTSS
Copyright2018AdventiumLabs. 10
integration_model.aadl system and system implementation forasystemincludingFACE
conformantcomponents
Optionallyincludestimeandspacepartitioningviaprocessandvirtual processor
E. DataModel14) TheDataModel(topofFigure1)describesdatarelevanttoasystemusingFACE
conformantcomponents.a) TheSystemIntegratorusestheFACESharedDataModelandUSMsprovidedby
UoPvendorstoconstructaDataModel.b) UoPvendorsuseorextendtheSharedDataModel.Thismeansthatdifferent
UoPswillshareanontologicalhereditybetweentheirviews,easingthepathtotranslatingfromonetotheother.
15) EachentityintheDataModelismodeledinAADLasadata.a) ModelingtherealizationhierarchyofDataModelentitiesisnotnecessaryfor
mostAADLanalysis.
FACEEntity AADLEntity PropertiesDataModel package (optional)
DataModelEntityComposition:Conceptual
data • FACE::UUID • FACE::Realization_Tier => conceptual
DataModelEntityComposition:
Logical
data or data extends…
• FACE::UUID • FACE::Realization_Tier => logical
DataModelEntity:Platform
data or data extends…
• FACE::UUID • FACE::Realization_Tier => platform
• Memory_Properties::Data_Size
16) ExampleConceptual data aircraftID_Conceptual
properties FACE::UUID => "{0540db6f-67fd-430c-bc72-84126daa00cc }"; FACE::Realization_Tier => conceptual; end aircraftID_Conceptual;
Logical data aircraftID_Logical extends aircraftID_Conceptual properties FACE::UUID => "{ cf4c9604-f2a4-4e38-8937-05fd08e00f0a}"; FACE::Realization_Tier => logical; end AircraftID_Logical;
Copyright2018AdventiumLabs. 11
Platform data AircraftID_Platform extends aircraftID_logical properties FACE::UUID => "{5e4a3697-13b0-4c35-ba56-29f61f4cdc35}"; FACE::Realization_Tier => platform; end AircraftID_Platform;
F. DataModelViews17) AFACEPlatformViewiscomposedofdatafromtheplatformtieroftheFACEdata
model.a) APlatformView’scontentsaredefinedbyaquery,thesemanticsofwhichare
providedinsectionJ.3oftheFACETechnicalStandard.b) APlatformView’sorganizationisdefinedbyatemplate,thesemanticsofwhich
areprovidedinsectionJ.4oftheFACETechnicalStandard.c) EachPlatformViewismodeledasasingledata implementation.d) Thesubcomponentsofthedata implementationaredeterminedbythe
PlatformView’stemplateandthattemplate’sboundQuery.FACEEntity AADLEntity PropertiesConceptualView
data and data implementation
• FACE::UUID • FACE::Realization_Tier
=> Conceptual LogicalView data and data
implementation • FACE::UUID • FACE::Realization_Tier
=> logical PlatformView data and data
implementation• FACE::UUID • FACE::Realization_Tier
=> platform18) TheexampleinTable1showstheAADLdataanddata implementationfora
templateanditsboundQuerythatincludeanaircraftIDandtailNumber.PlatformView
data aircraft_config end aircraft_config; data implementation aircraft_config.impl subcomponents aircraftID: data AircraftID_Platform; tailNumber: data Tail_Number_Platform; properties FACE::Realization_Tier => platform; end aircraft_config.impl;
Table1ExampleplatformviewinAADL
Copyright2018AdventiumLabs. 12
G. UoPModel19) ThescopeoftheFACEDataArchitectureisrestrictedtothedataexchangedby
software.FACE3.0doesnotdescribethephysicalattributesofasystem(e.g.,bindinghardwaretosoftware).
20) AllAADLcomponentstranslatedfromFACEUoPsusetheFACE::UUIDpropertytodenotetheUUIDoftheFACEcomponentfromwhichtheywerederived.
21) AcollectionofUoPInstancesismodeledasasystem implementation.22) TheUoPmodeldoesnotincluderoutingofconnectionsbetweenUoPs.Connection
routingisdescribedintheFACEIntegrationModel.
Figure4:ExampleUoP(ADSB.impl)showninsideaprocess(ADSB.linux)
23) EachFACEUoPismodeledinAADLasathread group.a) TheFACETechnicalStandarddoesnotplacerequirementsonthreadingofUoPs,
howeverthestandarddoesprovideformultipleUoPsinasingleARINC653partitionorPOSIXprocess.InFigure4asingleUoPisshowninsideaprocess.However,asingleprocesscouldsupportmultipleUoPs.4
b) Asingle-threadedUoPismodeledasathread groupcontainingasinglethread.InFigure4theUoPiscalledADSB.ItisoftypeADSB.implandisfromthePSSSpackage.
c) UoPConnectionsontheUoParemodeledasportsontheUoPthread group.InFigure4theUoPConnectioniscalledATC_Data_In.
d) AADLportsonUoPsreferenceViewsviatypeconstraints.e) TheFACETechnicalStandardprovidesseveralrefinementsofUoPConnectionas
showninFigure5.Thefollowingaretheavailableconcrete(non-abstract)connectiontypes:i) AClientServerConnectionismodeledasanineventdataportandanout
event data port.
4ThisannextranslatesFACEelementstoAADLcomponentsthatcanbeusedinconjunctionwithaprocessorand/orvirtualprocessor,therebypermittingbutnotrequiringadherencetoARINC653orPOSIXAADLmodelingnorms.
Copyright2018AdventiumLabs. 13
ii) AQueuingConnectionismodeledasanineventdataportoranout event data port.
iii) SingleInstanceMessageConnectionismodeledasanin data port oran out data port.
FACEEntity AADLEntity Properties NotesUoP thread
group• FACE::UUID • FACE::FaceSegm
ent => PSSS or PCS
• FACE::Profile
Canalsobemodeledasanabstract,butthread groupispreferred.
UoPInstance thread group as subcomponent
Whenathread groupisusedassubcomponentofaprocess,itisactingasaUoPInstance.
UoPConnection Seeconcreteimplementations
• FACE::UUID • FACE::ViewUUID • Communication_
Properties::Input_Rate and Communication_Properties::Output_Rate
TherateofaUoPConnectionisspecifiedasaperiodinsecondsintheFACEUoPModel,requiringinversionforrepresentationinAADL.
ClientServerConnection(extendsUoPConnection)
An in event data port with data type fromassociatedviewandan out event data port with data type fromassociatedview
Associatedviews(requestTypeandresponseType)areassociatedwithportsdependingontheClientServerRolepropertyoftheconnection.Iftheconnection’sroleisClient,thentherequestTypeviewisassociatedwiththeout portandtheresponseType
Copyright2018AdventiumLabs. 14
viewisassociatedwiththein port.TheassociationisreversedforClientServerConnectionswithroleServer.
QueuingConnection(extendsUoPConnection)
in orout event data port with data type fromassociatedview.ThedirectionoftheportisdeterminedbytheMessageExchangeTypeproperty.InboundMessagecorrespondstoanin port,OutboundMessagecorrespondstoanout port.
Communication_Properties::Queue_Size setfrom Depth
SingleInstanceMessageConnetion(extendsUoPConnection)
in or out data port with data type fromassociatedview.ThedirectionoftheportisdeterminedbytheMessageExchangeTypeproperty.InboundMessagecorrespondstoanin port,OutboundMessa
Copyright2018AdventiumLabs. 15
gecorrespondstoanout port.
Figure5FACEUoPConnections,extractedfromtheFACETechnicalStandardEdition3.0
24) EachthreaddefinedintheUoPismodeledasanAADLthread.
a) TheperiodpropertyofthethreadisassumedtobeinsecondsandisrepresentedAADLusingthePeriodproperty.
b) TherelativePrioritypropertyofthethreadisassumedtoimplyhighernumericalvaluemeanshigherpriorityandistranslateddirectlytotheAADLPriorityproperty.
c) ThetimeCapacitypropertyofthethreadisassumedtobeinsecondsandisrepresentedinAADLusingtheCompute_Execution_Timeproperty.
25) TheexampleshowninTable2showsathreadgroupcorrespondingtoanAutomaticDependentSurveillance-Broadcast(ADSB)UoP.
UoP thread group ADSB features
ADSB_From_ATCManager_Port: in data port balsa_data_model::atc_data.impl;
properties
Copyright2018AdventiumLabs. 16
FACE::UUID => "{5884a330-a191-498a-9378-11b61f3c1c77}"; FACE::FaceSegment => PCS;
end ADSB; Table2ExampleUoPinAADL
H. TSS26) ATSSismodeledinAADLasanabstractthatcanberefinedtoaccommodate
varyinglevelsofmodeldetail.
FACEEntity AADLEntity PropertiesTSS Anabstractforeach
TSSinthesystem• FACE::UUID • FACE::Segment=>TSS
TSS(addeddetail) AnabstractforeachTSSinthesystemimplementation,refinedasavirtual bus (forexample)
• FACE::UUID • FACE::Segment=>TSS
UoPtoUoPmessageroute
flow through oneormoreTSSabstract.
• FACE::UUID
I. Routing27) TheFACETechnicalStandardspecifies,butdoesnotrequire,aformalmodelforthe
configurationoftheTSScalledtheIntegrationModel.TheIntegrationModelincludestheroutingofdatabetweenUoPs.WhetherornottheyopttousetheFACETechnicalStandardIntegrationModel,systemintegratorswillhavetoconnectUoPs.Thisannexprovidesastandardstylefortheirinterconnection.a) ThisdocumentsupportsuseoftheFACEIntegrationModelasspecifiedbythe
FACETechnicalStandard.b) Thisdocumentprovidesguidancegenerallyapplicabletoroutingconfigurations.
28) TheFACETechnicalStandardintegrationmetamodelprovidesmechanismsfordescribinginter-UoPcommunication,includingviewtranslation(adaptingadatainterfaceparameterfromoneUoPtoanother).
Copyright2018AdventiumLabs. 17
a) TheentitiesoftheFACETechnicalStandardintegrationmetamodelareshowninFigure6andFigure7.
29) AUoPInstanceisaUoPasusedinanIntegrationModel.AsingleUoPmaybeusedmultipletimesinaFACEIntegrationModel.TheUoPismodeledasathread groupandthread group implementation(s).WhentheUoPisusedasasubcomponent,thesubcomponentactsasaUoPInstance.a) ThisannexdoesnotspecifyanAADLrepresentationoftheIntegrationModelas
awhole.b) Forexample,supposeamessageloggingUoPismodeledasathread group
namedloggerandimplementedasathread group implementationnamedlogger.impl.IftheFACEIntegrationModelcallsforaUoPInstancenamedmy_logger,anAADLsubcomponentoftypelogger.implwithnamemy_loggershouldbeused.
30) TheFACETechnicalStandarddoesnotspecifyorganizationofUoPsintoprocesses.MultipleUoPsmaybemodeledinasingleprocessorinmultipleprocesses.
31) AUoPintheUoPModeldefinesitsUoPConnections.TheseUoPConnectionsaremodeledasportsinthethread grouporthread group implementation.Whenthethread groupusedasasubcomponent,itsportsactasUoPEndPoints.a) AUoPEndPointisafeatureoftheFACETechnicalStandardIntegrationModel
anddescribespartoftheTSSconfiguration.EachUoPEndPointreferstoasingleUoPConnectionthatitservices(seeFigure7).
b) NotethataUoPConnectionisnotequivalenttoanAADLconnection.c) NotethataUoPEndPointisnotdirectlyequivalenttoanAADLport.A
UoPEndPointandaUoPConnectiontogetherdefineanAADLport.d) AADLportscorrespondingtoUoPConnectionsmaybeorganizedinto
feature groups.32) ATSNodeConnectiondescribestheconnectionfromaUoPtotheTSS(notto
anotherUoP)33) ATransportChannelismodeledasanAADLvirtualbustowhicha
ViewTransporterisbound.Forexample,aFACEIntegrationModelmightconfigureaviewtobetransportedbetweenUoPsbyaViewTransporterandadaptedbetweentypesusingaViewTransformation.
34) TheexampleinTable3showsUoPdataroutingthroughaTSS.ConnectionsgofromUoPstoaTSSandflowsdescribedatagoingfromUoPtoUoP.a) TheIntegrationModelaloneisinsufficienttodescribeflowsthattraversemore
thantwoUoPs.TheflowsinTable3includeinformationbeyondthatprovidedintheIntegrationModel.
UoPRoutingthroughTSS
connections AirConfig_To_TSS: port airConfig_PSSS.airconfig_out -> TSS.airconfig_in;
TSS_To_ATC_Port: port TSS.airconfig_out -> atc_PCS.airconfig_in;
Copyright2018AdventiumLabs. 18
ATC_To_TSS: port atc_PCS.adsb_out -> TSS.adsb_in; TSS_To_ADSB: port TSS.adsb_out -> ADSB_PSSS.ATC_Data_in;
flows AirConfig_ETE: end to end flow airconfig_PSSS.AirConfig_Source -> AirConfig_To_TSS ->
TSS.AirConfig_flow -> TSS_To_ATC_Port -> atc_PCS.airconfig_adsb_flow -> ATC_To_TSS -> TSS.adsb_flow -> TSS_To_ADSB -> ADSB_PSSS.ATC_Sink;
Table3ExampleUoPRoutingthroughaTSS
FACEEntity AADLEntity PropertiesIntegrationModel system
implementation• FACE::UUID
FACEEntity AADLEntity PropertiesUoPInstance thread group as
subcomponent• FACE::UUID
UoPOutputEndPoint port on thread
group as subcomponent
• FACE::UUID
TSNodePort port ona TSS abstract
• FACE::UUID
TSNodeConnection connection • FACE::UUID ViewTransporter abstract • FACE::UUID
TransportChannel bus with viewtransporterabstractorviewtransporterrefinement bound toit
• FACE::UUID
ViewFilter,ViewTransformation,ViewAggregation,ViewSource,ViewSink
abstract toberefinedonanimplementation-specificbasis
• FACE::UUID
Copyright2018AdventiumLabs. 19
Figure6FACEIntegrationPackage,extractedfromtheFACETechnicalStandardEdition3.0
Figure7FACEIntegrationTransportPackage,extractedfromtheFACETechnicalStandardEdition3.0
J. IOSS35) TheIOSSLayer(bottomofFigure2)providesanAPIbutdoesnothaveaformal
exchangemodel,asIOSScomponentsareinherentlyspecifictoaparticularplatform.
Copyright2018AdventiumLabs. 20
a) IOSScomponentsaremodeledinAADLasabstracts.b) APSSSUoP’suseofIOSSfunctionsismodeledinAADLusingsubprogramcalls.c) ThephysicalcomponenttowhichtheIOSSserviceprovidesaccessismodeledin
AADLasadevice.d) ThebususedbytheIOSSservicetocommunicatewithitsphysicalcomponent(s)
ismodeledinAADLasabus access.FACEEntity AADLEntity PropertiesIOSSService abstract • FACE::UUID
• FACE::Profile • FACE::Segment=>IOSS
IOSSDevice Device • FACE::UUID • FACE::Segment=>IOSS
IOSSBus bus access • FACE::UUID • FACE::Segment=>IOSS
K. FACEHealthMonitoringandFaultManagement(HMFM)36) TheFACEHMFMAPIisasubsetoftheARINC653HMFMAPI,whichisdescribedin
theAADLARINC653annex.
L. FACEProfiles37) TheFACETechnicalStandardprovidesseveraloperatingsystemprofilesdescribing
whichsystemcallsarelegalforaUoC.
M. FACELifecycleManagement38) TheFACELifecycleManagementarchitectureisoutofscopeforthecurrentversion
ofthisdocument,howevertheLifecycleManagementAPIs,States,andTransitionswilllikelytranslatenaturallytotheAADLBehaviorAnnex.
N. FACEArtifactParsingGuide39) TheDataModel,UoPModel,andIntegrationModelareprovidedinastandardized
EMOFformatprovidedinsectionJ.5oftheFACETechnicalStandard.
Copyright2018AdventiumLabs. 21
O. FACEPropertySetpropertysetFACEis Profile:enumeration(security,safety_extended,safety,general)appliesto(all); Tier:typeenumeration(conceptual,logical,platform); UUID:aadlstringappliesto(all); Realization_Tier:FACE::Tierappliesto(all); segment:typeenumeration(PSSS,PCS,IOSS,OSS,TSS); FaceSegment:FACE::segmentappliesto(all);endFACE;