- Idea of budgets: that there is some amount of resource to be shared
among a number of components (parts of the system)
- the problem to solve: use resource efficiently but not
oversubscribed (not too heavy or too power hungry)
- Examples: simple
- Power, constant source
- Mass
- Bandwidth or time
- Examples: complex
- Power with variable generation (show powerstrip output)
- Screen real estate, especially when modal
- Fuel/Delta-v
- Techniques
- Tracking
- Tracking with modality or variability
- Interaction with specifications: system-level requirement not to
oversubscribe, but not on subcomponents. can say “mass must be
under X” but that doesn’t work as expected
- The difficulty: give everyone a target and they will work to that
target but not past it; when some component can’t go down to target
the system ends up oversubscribed
- the example about asymmetric incentives
- Estimation — initial and improving
- Reserves that decrease over time
- Negotiation
- Example: shared cable routing
- Each (complex) component is given a target for what they can use
- Each subteam works to that
- Separate team manages the shared resource, such as cable raceway
space
- Stability of solutions and how to avoid constantly bouncing around
- Need: give incentives for teams to go under a target or use a shared
target
- Leadership effect
- Marketplace mechanism?
- Need for team to manage a complex shared resource, like screen
space, variable bandwidth usage, cable raceway volume