Highlevel walkthrough business architecture using togaf. For process modellers.

1. BUSINESS
ARCHITECTURE
USING THE TOGAF FRAMEWORK
© Henk Harms (henk<at>d-d-d<dot>com<dot>au
1

2. Business Architecture using TOGAF framework:
• Although TOGAF is well defined for technical it is still a bit “light” on Business Architecture.
• Business Architecture is about business vision and business purpose.
• It uses People assets and fixed assets to establish capability patterns.
• It groups these patterns in Motivation, Organisation and Function.
© Henk Harms (henk<at>d-d-d<dot>com<dot>au
2

3. Consolidate different assets :
• Enterprise entities that are part of the community you are
investigating.
• Manual processes
• Social networks and their interactions
• Automatic Processes with their customer and supplier
processes.
© Henk Harms (henk<at>d-d-d<dot>com<dot>au
3

4. © Henk Harms (henk<at>d-d-d<dot>com<dot>au
Orchestration:
• Enterprise Architecture is orchestrating:
• Business Architecture
• Information Architecture
• Application Architecture
• Technical Architecture
• Using the identified patterns within each of the architectures.
4

5. Motivation:
• Consolidates why community and as such projects exist.
• Can be driven by regulatory, safety, environmental contracts.
• Captures:
• the drivers, what makes the organisation tick.
• the goals, how does the organisation tick.
• Objectives, at the end of the process what is it we suppose to have or be.
• Measure, typical the KPI components.
• You can apply the typical Zachman components to this.
© Henk Harms (henk<at>d-d-d<dot>com<dot>au
5

6. Organisation:
• Organisation, defines the entities across multiple organisational boundaries, as
such I believe it is better defined as a community. Community is a logical grouping
and is not restricted by enterprise and organisational boundaries.
• Location, where are entities located geographically and physically.
• Stakeholder/Roles the who based upon what they do the role realises a special
behaviour. The behaviour is controlled (restricted by) the organisation and function.
© Henk Harms (henk<at>d-d-d<dot>com<dot>au
6

7. Function:
• Business Domains, a logical view, commonly known as “helicopter view”, the
business domain is best represented as a community using the Motivation and
Organisation to group by the objectives and behaviours. You can define the
business domain representing all the role and all the services it will supply to meet
the community objectives.
• Processes (Context/Capability) specifies the events, controls.
• Activities/Steps what is done and when is it done to complete the process.
Data
• DataObjects are captured within this segment, and will be used to establish the
Information Architecture.
© Henk Harms (henk<at>d-d-d<dot>com<dot>au
7