Applications Inventory and Attributes - Assessment and Health attributes for the Applications Inventory
Applications Inventory and Attributes
Chapter 15. Assessment and Health attributes for the Applications Inventory
Executive Summary: Chapter Overview
IF4ITThe Bottom Line
Core Concepts
| Concept | Definition & Strategic Role |
|---|---|
| Composite health | Rolls technical, functional, operational, and risk signals into one comparable health score. |
| Fitness dimensions | Separates technical fitness from business/functional fitness so both are visible. |
| Assessment currency | Records when health was last assessed so scores can be trusted. |
Quick Q&A
Question: Why is Overall Application Health Score derived rather than entered?
Read More Below
Assessment and Health attributes summarize the assessed condition of each application.
| Attribute Name | Maturity | Description and Notes |
|---|---|---|
| Overall Application Health Score | Walk | Description — A composite, derived roll-up of technical fitness, functional/business fitness, operational condition, and risk into a single health indicator. Benefit(s) — Gives leadership one comparable health signal per application for portfolio triage. Source — Derived. Notes — Rolls up technical fitness, functional/business fitness, operational condition, and risk into a single indicator. Examples — Green (82/100); Amber (61/100) — aging technology, stable usage; Red (34/100) — end-of-life platform, high risk, low satisfaction |
| Technical Fitness Score | Walk | Description — A composite assessment of the application's technical quality, currency, maintainability, security posture, and alignment with current architecture standards — expressed as a tiered rating: High Fitness, Adequate Fitness, Low Fitness, or Poor Fitness. Benefit(s) — The technical fitness dimension of the rationalization assessment matrix. Combined with Business Value Rating, Technical Fitness Score determines which Rationalization Posture is appropriate for each application. Source — Manually Entered — assessed by the IT Application Owner or Enterprise Architecture function using a defined technical fitness assessment methodology. Notes — Valid values: High Fitness, Adequate Fitness, Low Fitness, Poor Fitness. |
| Functional / Business Fitness Score | Walk | Description — A 1–5 rating of how well the application still meets the business need it serves. Benefit(s) — Complements Technical Fitness by capturing business relevance, so a technically sound but functionally obsolete application is visible. Source — Manual (business/product assessment). Examples — 5 — Fully meets current business requirements; 3 — Meets core needs with notable gaps and workarounds; 1 — No longer fits the business process; replacement needed |
| User Satisfaction Score | Run | Description — A measure of user satisfaction with the application — expressed as a Net Promoter Score (NPS), a satisfaction rating scale, or the result of a structured periodic user survey. Benefit(s) — Adds the user perspective to the portfolio assessment alongside technical fitness and financial data. An application with high business value, adequate technical fitness, and very low user satisfaction may represent a higher investment risk than its technical metrics suggest. Source — Manually Entered — collected through periodic user surveys or in-application feedback mechanisms. |
| Technical Debt Level | Walk | Description — An assessment of the accumulated technical shortcuts, outdated technology, deferred maintenance, and architectural compromises in the application — expressed as Low, Medium, High, or Critical — accompanied by a brief description of the primary debt categories. Benefit(s) — Technical debt has a quantifiable financial cost that manifests as slower delivery velocity, higher incident rates, increasing maintenance costs, and difficulty attracting engineering talent. Without explicit tracking, technical debt is invisible in portfolio financial analysis and excluded from rationalization decisions where it is often the most important factor. Source — Manually Entered. Notes — Valid values: Low, Medium, High, Critical. Include a brief description of the primary debt categories in the Notes / Additional Context attribute when High or Critical. |
| Last Health Assessment Date | Walk | Description — The date of the most recent formal health assessment for this application. Benefit(s) — Signals how current the health scores are and supports a review cadence. Source — Manual. Examples — 2026-03-15; 2026-Q1; March 2026 |
How to cite this page
When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.
Example (informal web citation):
The International Foundation for Information Technology (IF4IT), LLC. Assessment and Health attributes for the Applications Inventory | Applications Inventory and Attributes. https://if4it.org/best-practices/applications-inventory-and-attributes/assessment-and-health-attributes-for-the-applications-inventory/ (accessed 2026-07-20).
See About Us for content governance and site-wide citation guidance.
Copyright for The International Foundation for Information Technology (IF4IT), LLC: 2008 - Present
Legal Disclaimers