Carregando...
Logo isTDMFramework

TD Identification

It provides guidelines to identify (manually or automatically) different TD types that may emerge in the software lifecycle.
Some terms are highlighted in italics. You can access definitions for these terms by clicking on them.

Activity IDT_1. : Map the possible TD items, criteria, and acceptable levels to identify them.

The occurrence of possible TD items and criteria to support their identification can be previously mapped in the early stages of the project.

Task IDT_T1

Map potential issues that can occur (intentionally and unintentionally) in the project, impacting software evolution and maintenance activities. These issues are TD items related to non-compliance with the required internal quality software, actions, and technologies. Each TD item is associated with a TD type. This mapping should consider the technical project’s context.

Status

Recommendations

R1_IDT_T1.

Project members should identify the possible issues related to non-compliance among the performed activities, artifacts, technologies, and the required quality standards. The outcome can be used as a list containing information about the potential TD items that can emerge during the project’s lifecycle.

Status

R2_IDT_T1.

This information can be registered on the proposed Artifact 2 (List of Required Actions, Artifacts, Technologies, and Potential TD items – Potential TD items Section)

Status
Task IDT_T2

Define specific criteria and/or acceptance levels to support identifying the mapped potential TD items and their types, mainly those that cannot be identified automatically. It can include defining what types of debts can be accepted and their respective acceptance percentages.

Status

Recommendations

R1_IDT_T2.

Define specific criteria to observe problems related to required standards and practices such as requirements, documentation, code, architecture, design, tests, and versioning.

Status

R2_IDT_T2.

This information can be registered on the proposed Artifact 2 (List of Required Actions, Artifacts, Technologies, and Potential TD items – Criteria Section).

Status

Activity IDT_2. : Define and use specific technologies to identify TD

Project members can define and adopt technologies to support the identification of TD items.

Task IDT_T3.

Identify and define technologies that should be used to support the identification of TD items. It should consider the different TD types that can occur in the project and the possible ways to identify such TD (e.g., semi-automatic or manual identification). These technologies refer to tools for static analysis of source code or specific strategies, practices, and checklists.

Status

Recommendations

R1_IDT_T3.

Look for specific technologies that can be used to support the identification of TD items. See here the list of some technologies to identify TD items.

Status
Task IDT_T4.

Periodically identify the TD items that emerged intentionality or unintentionality throughout the project. The identification of TD items can be performed in different project phases, according to the adopted development practices. For example, in each project’s iteration (at the beginning or the end).

Status

Recommendations

R1_IDT_T4.

Use the defined technologies to identification of TD items. The proposed Artifact 3 (Checklist to support the inspection of TD items) can be used as a guide to drive the identification of possible inconsistencies related to SE actions, practices, and technologies that are not meeting the required standards which such inconsistencies may hinder software maintenance and evolution activities.

Status

R2_IDT_T4.

If relevant, use the list containing the required actions, artifacts, technologies, and potential TD items mapped (Artifact 2) as a basis for supporting the comparison between the required standards and status of activities and software artifacts.

Status

Activity IDT_3. : Create a backlog of TD

This makes it easier and more explicit for team members to identify, measure, prioritize, report, and track TD items without making big changes to their workflow.

Task IDT_T5.

Create and maintain a backlog list of the identified TD items.

Status

Recommendations

R1_IDT_T5.

The backlog can be structured as a spreadsheet, a documentation artifact, or structured in management tools. If relevant, use the proposed Artifact 4 (TD Management Worksheet – Section of Backlog of TD) to register basic information about TD items.

Status
Task IDT_T6.

Classify and register information about each identified TD item. This involves describing the TD items, their type, related project’ iteration, and status.

Status

Recommendations

R1_IDT_T6.

Team members can register this information at specific moments of the project, such as in retrospectives meetings and at the beginning or end of each project iteration. If relevant, use the proposed Artifact 4 (TD Management Worksheet – Section of Backlog of TD) to register such information.

Status

Activity IDT_1. : Map the possible TD items, criteria, and acceptable levels to identify them.

The occurrence of possible TD items and criteria to support their identification can be previously mapped in the early stages of the project.

Task IDT_T1

Map potential issues that can occur (intentionally and unintentionally) in the project, impacting software evolution and maintenance activities. These issues are TD items related to non-compliance with the required internal quality software, actions, and technologies. Each TD item is associated with a TD type. This mapping should consider the technical project’s context.

Status

Recommendations

R1_IDT_T1.

Project members should identify the possible issues related to non-compliance among the performed activities, artifacts, technologies, and the required quality standards. The outcome can be used as a list containing information about the potential TD items that can emerge during the project’s lifecycle.

Status

R2_IDT_T1.

This information can be registered on the proposed Artifact 2 (List of Required Actions, Artifacts, Technologies, and Potential TD items – Potential TD items Section)

Status
Task IDT_T2

Define specific criteria and/or acceptance levels to support identifying the mapped potential TD items and their types, mainly those that cannot be identified automatically. It can include defining what types of debts can be accepted and their respective acceptance percentages.

Status

Recommendations

R1_IDT_T2.

Define specific criteria to observe problems related to required standards and practices such as requirements, documentation, code, architecture, design, tests, and versioning.

Status

R2_IDT_T2.

This information can be registered on the proposed Artifact 2 (List of Required Actions, Artifacts, Technologies, and Potential TD items – Criteria Section).

Status

Activity IDT_2. : Define and use specific technologies to identify TD

Project members can define and adopt technologies to support the identification of TD items.

Task IDT_T3.

Identify and define technologies that should be used to support the identification of TD items. It should consider the different TD types that can occur in the project and the possible ways to identify such TD (e.g., semi-automatic or manual identification). These technologies refer to tools for static analysis of source code or specific strategies, practices, and checklists.

Status

Recommendations

R1_IDT_T3.

Look for specific technologies that can be used to support the identification of TD items. See here the list of some technologies to identify TD items.

Status

Activity IDT_3. : Create a backlog of TD

This makes it easier and more explicit for team members to identify, measure, prioritize, report, and track TD items without making big changes to their workflow.

Task IDT_T5.

Create and maintain a backlog list of the identified TD items.

Status

Recommendations

R1_IDT_T5.

The backlog can be structured as a spreadsheet, a documentation artifact, or structured in management tools. If relevant, use the proposed Artifact 4 (TD Management Worksheet – Section of Backlog of TD) to register basic information about TD items.

Status

Activity IDT_2. : Define and use specific technologies to identify TD

Project members can define and adopt technologies to support the identification of TD items.

Task IDT_T4.

Periodically identify the TD items that emerged intentionality or unintentionality throughout the project. The identification of TD items can be performed in different project phases, according to the adopted development practices. For example, in each project’s iteration (at the beginning or the end).

Status

Recommendations

R1_IDT_T4.

Use the defined technologies to identification of TD items. The proposed Artifact 3 (Checklist to support the inspection of TD items) can be used as a guide to drive the identification of possible inconsistencies related to SE actions, practices, and technologies that are not meeting the required standards which such inconsistencies may hinder software maintenance and evolution activities.

Status

R2_IDT_T4.

If relevant, use the list containing the required actions, artifacts, technologies, and potential TD items mapped (Artifact 2) as a basis for supporting the comparison between the required standards and status of activities and software artifacts.

Status

Activity IDT_3. : Create a backlog of TD

This makes it easier and more explicit for team members to identify, measure, prioritize, report, and track TD items without making big changes to their workflow.

Task IDT_T6.

Classify and register information about each identified TD item. This involves describing the TD items, their type, related project’ iteration, and status.

Status

Recommendations

R1_IDT_T6.

Team members can register this information at specific moments of the project, such as in retrospectives meetings and at the beginning or end of each project iteration. If relevant, use the proposed Artifact 4 (TD Management Worksheet – Section of Backlog of TD) to register such information.

Status

TDM Guidelines