Business footprint diagrams

A business footprint diagram describes the links between business goals, organizational units, business functions and services, and maps these functions to the technical components delivering the required capability.

A business footprint diagram provides clear traceability between a technical component and the business goal that it satisfies, whilst also demonstrating ownership of the services identified.

A business footprint diagram demonstrates only the key facts linking organization unit functions to delivery services, and is utilized as a communication platform for senior-level (CxO) stakeholders. It must be focused on the current business interest: depending on the focus, it can concentrate on one or several application components (that need evolution) or on one or more business functions.

business-footprint-diagram
Business footprint diagram focused on the "sales" function

business-service-32Business service: Represents a service provided by the business, which may then be realized by one or more IS services.

entity-componentEntity application component: An entity component is frequently derived from business entities, and is responsible for managing the access to the entity, and its integrity.

functionFunction: Describes one function of the organization.

process-componentProcess application component: A process application component is responsible for a business process execution. It orchestrates the tasks of the process.

organization-unitOrganization unit: Describes one unit that breaks down the organization of the enterprise. This can be, for example, a department.

togaf-process-32Business process: As presented in process maps (event diagrams). The business process is detailed in flow diagrams.

support-linkSupports link: Determines that a service or process is supported by finer-grained elements such as other services or processes, or application elements.

participates-linkParticipates in link: Describes in which part or activity of the enterprise a participant intervenes.

trace-linkTrace link: General purpose tracebility link. Determines that the origin of the trace has been founded on the trace destination during its definition.

component-realizationComponent realization: An application component realizes the designated element, for example a business process.

Comments   

Pravin
0 # Pravin 2012-01-22 09:51
Very good explanation of business Foot print Diagram
:-)
Reply | Reply with quote | Quote
Joe Anthony
0 # Joe Anthony 2012-12-19 19:31
Very descriptive, thanks!
Reply | Reply with quote | Quote
nicesmile
0 # nicesmile 2013-05-03 18:08
I'm trying to build an architecture and as for the business fottprint diagram, I'm having a hard time understanding what Process application component are? are they modules in the existing IS ? same for Entity application component, are they document? outcome of a business process?
Thanks
Reply | Reply with quote | Quote
nicesmile
0 # nicesmile 2013-05-03 19:46
I have another question: what is the difference between a process and a business service ? how can I differentiate between them in a case where a service requires a process?
Reply | Reply with quote | Quote
uniqueName
+1 # uniqueName 2013-05-06 08:37
@nicesmile
It is common practice to layer an SOA based architecture into (at least) four layers :
Presentation (GUI)
Process
Function
Entities

Therefore we add a category to application components to distinguish layers.

A Process component is in charge of managing one business process : Tasks scheduling, connecting to lower lever services to execute tasks, event management, process state management. This involves frequently specific technologies such as BPEL or other BPMS.

Entity Application components are responsible of managing one or several (consistent set) Entities. They maintain their integrity, by centralizing their access instructions.

A business service is a service (like in the SOA sense) at the business level. It supports business capacities.
A business process is a coordinated set of activities that serve a specific business purpose.
Reply | Reply with quote | Quote
graham
+1 # graham 2013-07-26 12:51
Don't get bogged down in particular architecture domains.

Generally, a service (defined by a service contract) is delivered as the outcome of one or more processes (definable as a sequence of activities. Note that both services and processes may be decomposed to several levels.

See the "generic meta model" at http://avancier.co.uk
Reply | Reply with quote | Quote
phil
-4 # phil 2013-07-26 13:21
@graham,

THis is not a place for a commercial pitch. At least, could you point the place where your information is instead of letting us dive in a commercial site. If you bring real material and comments, you are welcome.
Reply | Reply with quote | Quote
phil
0 # phil 2013-07-26 13:23
@graham,

THis is not a place for a commercial pitch. At least, could you point the place where your information is instead of letting us dive in a commercial site. If you bring real material and comments, you are welcome.
Reply | Reply with quote | Quote
graham
0 # graham 2013-07-26 14:20
Phil

The comment (not visible) was genuine answer to the question (not a commercial pitch) with a reference to back it up.

The generic meta model is at the top of the second avancier.co.uk page - click on any landing page link to get there.

On the same page, in the Avancier Methods sections, you can find several presentations, illustrating about 90 artefacts, including all the TOGAF ones.
Reply | Reply with quote | Quote

Add comment

Leave this empty:


Security code
Refresh

Login

Sign in to use the forum and be informed of the latest news.

Latest comments