Task: Estimate influence from future functionality
The task Estimate influence from future functionality compares the solution and its time budget properties with the product plan to identify which functionality is still to be added to the system.
Relationships
Main Description

When making a time budget, not only the current solution (regardless of abstraction level) needs to be considered, but also the influence of future functionality. Future functionality refers to both functionality that is planned but not yet implemented, and to still unknown functionality that potentially is to be included in future generations of the system. The task Estimate influence from future functionality compares the solution and its time budget properties with the product plan to identify which functionality is still to be added to the system, and also makes an assessment of the influence of unknown functionality. Based on this information, the developer needs to assess how much the still missing functionality affects the end-to-end event chain currently under investigation. This will eventually lead to introducing slack in the final time budget. Typical properties that are affected are communication delay (increased congestion) and task execution periods (increased competition for computation power), which both lead to a longer end-to-end delay. Unknown functionality that will be included into the system in future generations of the system may also be considered in this task.