What are top priority views of your Application Landscape

Friday, May 1, 2015 | Likes: 0 | Comments: 0

Mark Paauwe

VP Product Development

Dragon1 Inc

A lot of people are asking me now what views they should create of their Application Landscape.

The How To Create an Application Landscape Diagram page gets you going, but leaves some questions.

In my opinion you can create/generate an endless list of useful (management report) views of your application landscape, but here is a list of top views to you can consider to create/generate:

  • Management Overview
  • Application Modules Functions View
  • Replacable Modules View
  • Loosely Coupling View
  • Dependency View (of Applications, Objects, Interfaces and Databases)
  • Applications Reuse View
  • Deduplication options of Applications, Modules and Functions View (Duplicate Applications View)
  • Obselete and Outdated Applications View (I often call this the dead tree view)
  • Single Software Suppliers / Products Dependency View (where are we depend of one supplier for solutions)
  • Too Expensive Applications View
  • Single Point of Failure (SPOF) View
  • TCO View
  • Ownership View
  • Software Update Maintenance View
  • Users vs Licenses View
  • Roles Access View
  • Security Leaks View
  • Architecture Principles View
  • Open Standards vs Proprietary View
  • Industry Standards Compliancy View
  • Reference Architecture Compliancy View
  • Applications Lifecycle View
  • Project Impact View (With processes, applications and technical systems)
  • Business functions View per domain
  • Applications functions view per domain
  • Technical details view vs Functional details view
  • Impact of change view (insert or remove information systems, application groups/suites, applications, modules or application functions)
  • Date time filter
  • Organization specific AS-IS, Plateaus & TO-BE Views
  • Single source of truth view of data & applications (overview of sources for certain business/information objects)
  • Vendors / Supplier view
  • Data dictionary view
  • Application Service Management View *** - cases available on how to save costs


The Application Landscape focuses mainly around applications (and their databases, dataobjects and interfaces), processes and servers are often excluded.
Views where processes and servers are included with applications are not so much applications landscape views but rather IT-landscape views, Business landscape views and enterprise landscape views.

We will give examples of some of these views on the How To page soon, based on the input we get here.

So I am very much interested what views you need or already work with on your Application Landscape. What do you consider to be top priority application landscape views to create for your management to take decisions with?

Read also

Read more about Dragon1 as EA Tool, to start creating your own Dragon1 Appplication Landscape Diagram.

Read more about Dragon1 as ArchiMate Tool, to start creating your own ArchiMate Application Landscape Diagram.

ArchiMate Diagram Application Landscape

This Archimate Diagram is an example application landscape pattern on Dragon1, available as editable template.

 

We are the digital platform for Enterprise Architecture. It is the best option a CIO has for Technology Innovation and Digital Transformation.

© 2019 Dragon1