Another very important artifact is a database containing basic information about the current state of Components. Collected in 3 basic categories: business, technical, financial. This information is gathered to determine what the future of the Component should be.
In the business perspective, the Component is assessed for its importance in business processes. The technical category assesses the quality of the code, the quality of delivery processes and the timeliness of technology with standards.
The financial perspective is an assessment of the cost of Components in the areas of licenses, infrastructure, maintenance, development costs. The financial context of the assessment should be based on the average values of the organization. When calculating the rating, the result can be based on, for example, a 5-point scale, not necessarily based on real values. The lower the costs are the better the app is.
In the end, each Application should reach to a specific of 4 groups of destination:
- Investment – Applications rated technically high and having great business significance are intended for further development and investments.
- Tolerance – Applications rated technically high but with little business significance, due to their low cost and good technical condition, should remain in the environment until their business significance and technical rate is maintained. They could be potentially good base for further development and investments
- Migration – Applications rated technically low but with high business significance are intended for a transfer of capabilities to Applications form a previous groups
- Elimination – Applications in a poor technical condition with functionalities that are irrelevant or other Applications cover them should be intended for termination
Diagram showing how to allocate Components to portfolios. The point size illustrates the financial perspective of each Component.(The larger the point is the better the Component is)
The assignment to the category is important when comparing which of the two Components development should occur if the two Components have redundant Capability.
Completing the database should be a cyclical event, it is recommended that one of the Application assessment component is an input from the end-users perspective made through surveys regarding the Application. A good way is to use the Net Promoter Score (NPS)
The final assessment of business-critical Components should be discussed in detail, agreed and approved by the business unit. Technical features of the Component should be updated on a regular basis by the development team
The steps should be performed:
- technical evaluation of the Component by the architect
- Application user rating
- financial evaluation
- business Component rating by the business owner
- Component categorization
- category change communication, if applies