Motivation View
Why, not what. Drivers, goals, principles, requirements.
- Format.puml
- Length35 lines
- LibraryArchiMate
The source
35 lines of PlantUML, and pulls in ArchiMate. Copy it, or open the template inside Gnomon and render it as it is.
@startuml
!include <archimate/Archimate>
title ArchiMate Motivation View
Motivation_Stakeholder(management, "Management")
Motivation_Stakeholder(customers, "Customers")
Motivation_Driver(efficiency, "Operational Efficiency")
Motivation_Driver(satisfaction, "Customer Satisfaction")
Motivation_Assessment(currentState, "Current manual processes are slow")
Motivation_Goal(reduceTime, "Reduce Processing Time by 50%")
Motivation_Goal(improveExp, "Improve Customer Experience")
Motivation_Outcome(fasterService, "Faster Service Delivery")
Motivation_Principle(automation, "Automate where possible")
Motivation_Requirement(selfService, "Self-service Portal")
Motivation_Requirement(integration, "System Integration")
Rel_Association(management, efficiency)
Rel_Association(customers, satisfaction)
Rel_Association(efficiency, currentState)
Rel_Influence(currentState, reduceTime)
Rel_Influence(satisfaction, improveExp)
Rel_Realization(fasterService, reduceTime)
Rel_Realization(fasterService, improveExp)
Rel_Realization(automation, fasterService)
Rel_Realization(selfService, automation)
Rel_Realization(integration, automation)
@endumlRender this offline
This template ships in Gnomon and renders on your machine, with no account and nothing sent to a server. The browser editor is free and needs no install.
Others in ArchiMate diagrams
- Layered ViewThe classic view: business over application over technology.
- Business LayerProcesses, actors, services at the business layer.
- Application LayerComponents and the services they expose.
- Technology LayerNodes, devices, system software.
- Implementation & MigrationWork packages, deliverables, plateaus: for migration.