Ransford's NotesCourses
Workspace

TOGAF with DoDAF/FEAF Bridge

Map TOGAF architecture views and deliverables to DoDAF viewpoints and FEAF reference models so practitioners working in defence or government contexts can navigate both frameworks.

ADM-wideDerived from TOGAF

TOGAF, DODAF and FEAF: same concerns, different artefacts

Four shared architecture concerns run down the side; each framework column names the equivalent artefact it ships, with TOGAF as the reference.

DODAF and FEAF are public-sector cousins of TOGAF. The grid names the equivalent artefact in each framework so a practitioner can map a concern across all three before reusing work.

TOGAF, DODAF and FEAF: same concerns, different artefacts A comparison grid. Four shared architecture concerns run down the left as blue-spined label cells: stakeholders and context, capability, application and interface, and technology and standards. Three columns name the equivalent artefact. The reference column, TOGAF, reads in the blue accent with its Phase A to D artefacts: stakeholder map, capability map, application portfolio and technology architecture. DODAF names OV-1 and OV-2, CV-2, SV-1 and SV-3, and SV-6 with StdV. FEAF names the BRM stakeholders, BRM business areas, ARM applications, and IRM and TRM. A closing note in red states the equivalences are approximate, so you must declare which mapping is exact and which only partial. Shared concernTOGAFOpen GroupDODAFUS DoDFEAFUS federal Stakeholders and contextWho matters, and the picture they shareStakeholder mapPhase A artefactOV-1, OV-2Operational contextBRM stakeholdersBusiness reference model CapabilityWhat the organisation must be able to doCapability mapPhase B artefactCV-2Capability taxonomyBRM business areasCapability areas Application and interfaceWhat software exists and how it connectsApplication portfolioPhase C artefactSV-1, SV-3System interfacesARM applicationsApplication reference model Technology and standardsWhat it runs on and the rules it followsTechnology architecturePhase D artefactSV-6, StdVStandards profileIRM, TRMInfrastructure model Equivalences are approximate.Map each concern across the row, then declare which mapping is exact and which is only partial before you reuse an artefact across frameworks.