MappIT can be helpful in many IT Strategy, Governance and Architecture real cases; just as an example we will describe some typical scenarios where you can leverage the tool to collect, correlate and analyse the data to support your suggestions and recommendations on a specific IT transformation scenario. The first, and basic, scenario is the Application architecture assessment, where you want to collect all relevant information related to your System landscape. So first of all you define your full list of IT systems (or modules), then insert these information in the IT Module screen. For each application you can provide General information like:
- who is the owner
- which is the application domain
- what are the key numbers
- what are the main technologies used and so on.
You can also describe if there are any issue on the described application, in this case the issue severity value are rolled-up in a total which represent the overall severity value of each specific application, this value will measure the risk that potentially are behind each application and can be later used to plot useful diagrams.
If you need to better understand the meaning of a specific field, you can take a look at the description in the bottom side of the main screen.
Then, for each module (or application) you can describe the Technical architecture in terms of:
- Main data entities owned by the system (master) and other entities displayed or managed as a slave.
- Inbound interface from other systems (and related data entities transferred)
- Outbound interface to other systems (and related data entities transferred)
- Main services provided (as a granular description of all atomic APIs, Web Services or GUI functionalities exposed to the external world
- Infrastructure used to run the application (this will be described in a future tutorial: IT Infrastructure architecture assessment)
You can also add or see other relevant information related to the application, like:
Spending information, like internal resource allocation and external budget allocated to activities referring to these module (we will be explained later in Spending Assessment tutorial)
Business Processes supported and Business Capabilities delivered (and declare the level of support / coverage); these information can be used here to map the current Business Architecture (we will be explained later in Business Alignment tutorial)
When you have complete the technical mapping you can generate nice diagram like the following, which provide a Module map organized by Status and coloured by Customization level.
You can also create an interface map, which describe all the relationships between modules and the name of each interface:
And you can also start analysing your system architecture using the MappIT analysis tools; in the following graph for example the system are plotted against the level of customization and maturity level:
or using more sophisticated (but always free) Visualization tools like Tableau Software.