Expected Outcomes

Documenting expected outcomes is arguably one of the most important parts of creating and documenting the task work that needs to be completed. The expected outcomes are used to articulate our understanding of what should be accomplished once the task has been completed. If expected outcomes are trivial and straightforward, this shouldn’t take too much time to document and still should be completed. If they are more complex or sophisticated, it’s even more important they be documented so that they may be completed.

Some Examples

• Sensor Threshold Detection - When a level is above a threshold generate an error condition.

• Chart on Sensor Report - When a report is generated it will contain a chart of sensor values.

• Move Devices - Allows the user to move devices and related data between device repositories.