Setting a Baseline which creates TODOs
Setting a Baseline
After obtaining an architectural design that represents the Domains for the Application, you should select the Measurement to be the Baseline Measurement of the Application:
Method 1: From the Analysis tab
- Log into the vFunction Server UI
- Select Analysis in the top, center menu bar
- Hover over the Measurement in the top of the left-hand sidebar
- Select Set as Baseline to set the current Measurement as the Baseline Measurement
Method 2: From the Observation Tab for future Scheduled Measurements
- Log into the vFunction Server UI
- Select Observation in the top, center menu bar
- Click the Pencil icon in the left-hand sidebar next to Configuration
- Select Configure Plan in the left-hand sidebar of the dialog box
- Click the text field below Select Baseline Measurement to select the appropriate Measurement as the baseline
Backlog TODOs from the Baseline
A key motivation for setting a Baseline Measurement is to start using Architectural Observability (AO) for monitoring and remediating architectural technical debt and creating TODO items reflecting the existing gaps in the architecture that need to be addressed by changing the application code.
Once the Baseline Measurement is selected, you will get some automatic Backlog TODOs, for example TODOs regarding high-debt classes (reduce their high debt score). Also, you will be able to create some manual TODOs, for example, you will be able to create TODO for non-exclusive resources and classes (make them exclusive) or for dead-code classes (remove references to them) as tasks that need to be done in the code itself.
Performing the tasks associated with these TODOs will cause an automatic change in the TODOs status following an automatic learning as we will see in the Continuous Modernization using AO section.