Phase C, Information Systems ArchitectureDerived from TOGAF

Application to Function Matrix

Show whether each business function has full, partial or no application support, so tooling gaps surface as columns with no full entry.

All tools

Application to function: where support is full, partial or missing

Applications run down the side and the six business functions run across the top. Full marks an application that meets a function on its own; Partial marks a contribution that needs others alongside it, so functional gaps surface as columns with no Full entry.

Application to function: where support is full, partial or missing The TOGAF Application/Function Matrix for London Grid Distribution. Rows are eight applications; columns are six business functions from manage connections to bill and settle. Full marks an application that supports a function on its own; Partial marks a contribution that needs other applications alongside it. The plan capacity column carries six Partial marks and no Full, exposing a tooling gap, while the emphasised GIS row contributes to five functions without completing any. Source: TOGAF Standard 10, Phase C Application Architecture artifacts. Application Manage connections Operate network Maintain assets Plan capacity Publish network data Bill and settle ConnectionsportalFullPartialPartial CRMPartialPartialPartial GISPartialPartialPartialPartialPartial AssetregisterPartialFullPartialPartial SCADAhistorianFullPartialPartialPartial Meter dataservicePartialPartialPartialPartial LTDS publicationsystemPartialFull BillingenginePartialFull Full meets the function alone, Partial contributes. Source: TOGAF Standard 10, Phase C artifacts

Read the columns for gaps: plan capacity draws Partial support from six applications yet none supports it fully, which is how a missing planning tool shows up in Phase C. The emphasised GIS row contributes to five functions without completing any, the shared foundation.

In Phase C, before planning investment, to find the functions held together by partial contributions from many systems.

What you need and what you get

You'll need

  • The application portfolio
  • The business functions the architecture serves

You'll get

  • A support grid of full and partial coverage
  • The functional gaps that justify new tooling

Taught in

No course modules linked yet.

Derived from

  • The Open GroupTOGAF Standard 10, Architecture Content: Application/Function MatrixSource

TOGAF is a registered trademark of The Open Group in the United States and other countries. This tool is independently produced, TOGAF-aligned, and is not affiliated with, endorsed by, or certified by The Open Group.