Next: Deployment of Requirements
Up: Requirements
Previous: Interaction between Core and
One of the advantages of adaptation is
the potentially reduced size of code which must be shipped over the network.
This gain of bandwidth and loading time must not be wasted by an
expensive adaptation mechanism.
- R11
- Therefore a fundamental requirement is to demand
that the size of the binary resources of the core
and of an adaptable part (worst case: the biggest)
including the adaptation mechanism is smaller than
the binaries of a comparable monolithic application.
Obviously, this needs to be considered in relation
to the overall size and to the execution time of the code.
This requirement supports the argument of
saved bandwidth when using adaptation.
- R12
- The second requirement enforcing minimal overhead
is fast loading of adaptable parts
and re-configuration of the mobile code.
- R13
- Considerations on runtime overhead must also include the time needed
for the invocation of adaptable methods. If this is noticeably high,
e.g. in relation to the runtime of the method,
the adaptation mechanism has a negative impact on
the performance of the mobile code.
Copyright Munich Network Management Team