搜索
FINALTextstarswreathDoDArchitectureFrameworkVersion2.0Volume3:DoDAFMeta-modelPhysicalExchangeSpecificationDeveloper’sGuide28May2009FINALThispageleftintentionallyblankFINALiFINALTABLEOFCONTENTSSECTIONPAGE1.INTRODUCTION.................................................................................................................12.PURPOSE..............................................................................................................................13.DODAFPHYSICALEXCHANGESPECIFICATION....................................................14.EXCHANGEOFDM2PESXMLDOCUMENTS............................................................35.DODAFV1.5ANDDODAFV2.0........................................................................................5APPENDIXA-ACRONYMS.................................................................................................A-1FINALiiFINALLISTOFFIGURESFIGUREPAGEFigure4-1:IllustrationofDM2RoleinProvidingaNeutralModelforDataExchange...............3Figure4-2:PESXSD,PESXML,XMI,UML,andSysMLRelationships...................................4LISTOFTABLESTABLEPAGETable3-1:ListofModelsandXSDs..............................................................................................1Table5-2:ExchangeActionsbetweensArchitectures...................................................................5FINAL1FINAL1.INTRODUCTIONDepartmentofDefenseArchitectureFramework(DoDAF)Version2.0introducesaDoDAFMeta-model(DM2),consistingofaConceptualDataModel(CDM),LogicalDataModel(LDM),andPhysicalExchangeSpecification(PES)asanintegralpartofthearchitectureframework.Volume3introducestheDM2,whichreplacestheCoreArchitectureDataModel(CADM)referencedinpreviousversionsofDoDAF.TheDM2providesameanstocollectarchitecture-relateddata,organizethedataintousefulinformationbyarchitectsandarchitectureDevelopmentTeams,storetheinformationforlaterreuse,andfacilitatemanagementanalysisofarchitecturaldataandinformationfordecision-makingpurposes,asfurtherdescribedbelow.ThisvolumeprovideslinksforDoDAFPESfiles,theroleofthePESandits’relationships,andguidanceforactionsthatneedtobetakenwhenexchangingarchitecturaldatabetweenarchitecturesdevelopedusingthesameordifferentversionsofDoDAF.2.PURPOSECollection,management,utilization,andreuseofarchitecturaldataandinformationareacomplextask.Successfulexecutionofthattaskrequiresknowledgeofbothdatastructuresandthebodyofknowledgerelatedtothepurposeforwhichanarchitectureisbeingcreatedi.e.,“Fit-for-Purpose”asdescribedinSection2ofVolume1.Ifexchangingarchitecturaldata,thePESisthespecificationfortheexchange.ThePESprovidesanefficientandstandardmeanstoensurethatdatasharingcanoccurinatoolset-agnostic,methodology-agnosticenvironment.UseoftheeXtensibleMarkupLanguage(XML)SchemaDefinitions(XSDs)byarchitectstodocumentarchitecturaldataandinformationintools,throughspreadsheets,orothermeans,anddepositthatdataandorganizedinformationintofederatedrepositoriesisfacilitatedbythecommonunderstandingunderlyingtheuseofthePES.3.DODAFPHYSICALEXCHANGESPECIFICATIONThePESisorganizedasasetofXMLSchemaDefinition(XSD)filesandisintheDoDAFJournal.ThefilesaretextformatandanXMLdevelopmentapplication,Notepad,etc.,willberequiredtoviewthefiles.TheXSDsforeachDoDAF-describedViewislistedinTable3-1:Table3-1:ListofModelsandXSDsModelModelNameXSDFilenameAV-1OverviewandSummaryInformationAV1.XSDAV-2IntegratedDictionaryAV2.XSDCV-1VisionCV1.XSDCV-2CapabilityTaxonomyCV2.XSDCV-3CapabilityPhasingCV3.XSDCV-4CapabilityDependenciesCV4.XSDCV-5CapabilitytoOrganizationalDevelopmentMappingCV5.XSDCV-6CapabilitytoOperationalActivitiesMappingCV6.XSDCV-7CapabilitytoServicesMappingCV7.XSDFINAL2FINALTable3-1:ListofModelsandXSDsModelModelNameXSDFilenameDIV-1ConceptualDataModelDIV1.XSDDIV-2LogicalDataModelDIV2.XSDDIV-3PhysicalDataModelDIV3.XSDOV-1HighLevelOperationalConceptGraphicOV1.XSDOV-2OperationalResourceFlowDescriptionOV2.XSDOV-3OperationalResourceFlowMatrixOV3.XSDOV-4OrganizationalRelationshipsChartOV4.XSDOV-5aOperationalActivityDecompositionTreeOV5A.XSDOV-5bOperationalActivityModelOV5B.XSDOV-6aOperationalRulesModelOV6A.XSDOV-6bStateTransitionDescriptionOV6B.XSDOV-6cEvent-TraceDescriptionOV6C.XSDPV-1ProjectPortfolioRelationshipsPV1.XSDPV-2ProjectTimelinesPV2.XSDPV-3ProjecttoCapabilityMappingPV3.XSDStdV-1StandardsProfileSTDV1.XSDStdV-2StandardsForecastSTDV2.XSDSvcV-1ServicesContextDescriptionSVCV1.XSDSvcV-2ServicesResourceFlowDescriptionSVCV2.XSDSvcV-3aSystems-ServicesMatrixSVCV3.XSDSvcV-3bServices-ServicesMatrixSVCV3.XSDSvcV-4ServicesFunctionalityDescriptionSVCV4.XSDSvcV-5OperationalActivitytoServicesTraceabilityMatrixSVCV5.XSDSvcV-6ServicesResourceFlowMatrixSVCV6.XSDSvcV-7ServicesMeasuresMatrixSVCV7.XSDSvcV-8ServicesEvolutionDescriptionSVCV8.XSDSvcV-9ServicesTechnology&SkillsForecastSVCV9.XSDSvcV-10aServicesRulesModelSVCV10A.XSDSvcV-10bServicesStateTransitionDescriptionSVCV10B.XSDSvcV-10cServicesEvent-TraceDescriptionSVCV10C.XSDSV-1SystemsInterfaceDescriptionSV1.XSDSV-2SystemsResourceFlowDescriptionSV2.XSDSV-3Systems-SystemsmatrixSV3.XSDSV-4SystemsFunc