Example · Device or platform developer
Which assumptions need another look when our software changes?
A developer connects an update to the evidence and user arrangements it could affect
The situation
Updating a decoding model
Your team has an assessed BCI prototype in a supervised pilot. You plan to replace its decoding model and alter calibration in the next version. The intended activity remains the same, but you need to decide which evidence and change questions belong in the release review
What this example starts with
- The existing basis
- The project record describes the earlier software version, calibration process and supervised pilot setting, retaining its limitations
- The proposed change
- The new version changes decoding and calibration, while an internal test report has not yet been checked against the pilot’s users and conditions
- The dependency
- Training material, support instructions and the handling of interrupted sessions were written for the earlier version and may depend on its behaviour
Working through the question
Identify what the old evidence covered
You read the original claims together with the version and conditions under which they were examined. Keeping the activity name unchanged does not establish that all earlier evidence transfers. You mark which claims depend on the components and interactions being modified
Examine changes outside the model
Changed calibration could also change assistance, expectations and troubleshooting. You consider the complete session as well as the model’s internal comparison. In the assessment record, proposed improvements remain claims until relevant evidence is reviewed, including any implications for the people providing support
Make continuity a release question
You ask what the pilot team and participants would need to understand about the change, and how a problematic update would be handled. These questions reveal dependencies to resolve. Recording a fallback idea does not demonstrate that it has been tested or agreed
An illustrative take-away
A change-focused review note
You prepare affected claims, evidence requests and operational questions for the pilot’s release review
- Which earlier claims depend on the old model or calibration process?
- What evidence examines the new version in the intended session conditions?
- What communication, support and recovery arrangements need review before a change?
Written for this example to show what the reader could take into their next conversation
The assessment does not test the update or authorize deployment to participants
Try this with your own question
Your guide explains the steps, access requirements and limits for your role