The v/h journal / Document
Decide what the device should remember
A device should have a reason to remember the last task.
Imagine a local agent using an image to work out where an object is. It may need that image to act and check the result. Keeping the image after the job is a separate decision.
For v/h, we want to distinguish the inputs needed for a task from preferences that help with the next use. Remembering a chosen setting could save repeated setup. Saving a record of every task needs its own justification.
We would want to specify what is stored, why it is needed and when it is cleared. The owner should have an understandable way to clear personal task data without losing the device's core capability.
A development check would be to complete a task, clear the saved personal data, and try the core job again. We would inspect what remains on the device as well as what the interface says was cleared.
The document uses an imagined example to explain requirements for our first utility, which is still in development.
Read the remaining 2 pages
Keep reading
Choose the computing budget around the job