System Application Mapposted by Anna Mar, July 04, 2011
The System Application Map illustrates your system landscape (by business capability and department). Consider the following example (telecom industry)*:
*example uses the names of Greek gods in place of system names
VariationsThe example breaks down applications by level 1 business capability and department. It is also common to break out the map by:
- level 2 business capability / department
- level 1 business capability / location
- level 1 business capability / product
ViewsIt is common to create audience-targeted views of the System Application Map. For example, focusing on the level 2 business capabilities for one department.
For this reason, it is difficult to maintain the System Application Map as a Microsoft Visio diagram. Ideally, a enterprise architecture software tool is used that allows views to be generated on the fly.
AudienceThe System Application Map is of interest to virtually everyone in the organization. Uses include:
- executive decision support
- project planning
- solution architecture
- support documentation
- training and onboarding
Drill DownIt is common to link the boxes in the application map to drill down views. This can include:
- level 2 / level 3 System Application Map
- project descriptions
- system/application roadmap documentation
ESB vs. ETL — what you need to know to make an informed choice.|
Don't worry about people stealing your ideas. If your ideas are any good, you'll have to ram them down people's throats.
~ Howard Aiken |
Extending ITIL metrics into the cloud — a concrete example.|
All systems need to be replaced with time. However, just because a system is legacy — doesn't mean it needs to be replaced immediately. |