Data requirements for "What is our technical debt?"
This business question allows you to understand the dependence of the applications on components based on component and application lifecycles so that you can act on your technical debt before the application or component goes out of service.
To have meaningful data for the business question What is our technical debt?, you must capture the following information about the applications and components in your company.
| Class | Attribute | Mandatory | Explanation |
|---|---|---|---|
|
Application |
|||
|
Name |
|||
|
Version |
|||
|
Start Date |
The start date is the date when the application is actively used. |
||
|
End Date |
x |
The end date is the date when the application is no longer used. |
|
|
Strategic Application |
Indicates whether the application is strategic for the business. |
||
|
Lifecycle |
Application lifecycle phases may include: Plan, Pilot, Production, Sunset, Retired | ||
|
Local Component |
|||
|
Application |
x |
The local component is used by the application it belongs to. |
|
|
Component |
The local component is derived from a component. |
||
|
Component |
|||
|
Name |
|||
|
Version |
|||
|
Object State |
Indicates whether the component is planned, currently active, or retired. Retired components are not displayed in the report. |
||
|
Start Date |
x |
The start date is the date when the component is actively used. |
|
|
End Date |
x |
The end date is the date when the component is no longer supported. |
|
|
Strategic Component |
Indicates whether the component is strategic for the business. |
||
|
Lifecycle |
Component lifecycle phases include Manufacturer Supported and Manufacturer Extended Support. | ||