Next: Future Work
Up: Discussion
Previous: Performance Meta-Models
Contents
Index
unstable
- ignore (dynamics, runtime)
- State of Component Protocols: Parametric contracts model dependencies between component interfaces with protocols which, therefore, have a state. In some cases, this leads to difficulties when analysing the interoperability of components communicating via an interface. Assume an interface provided by component A is accessed by components B and C. If B changes the state of the interfaces by calling a service, does component C see the changes or does it have its own view on A? This question cannot be answered in general. In some cases, components share the state, e.g. when using the Singleton pattern, in other cases they don't. To solve this issue, additional information in the component model is required. Ports and interfaces with cardinalities seem to be a promising concept.
- Identification of the Relevant QoS Parameters: To achieve accurate QoS predictions, the parameters influencing the attributes of interest need to be identified. A lot of work has already been done in this context, in UML for example by the definition of the UML SPT profile [47]. However, the existing work needs to be reviewed, to be extended and the identified parameters needed to be specified within our component model. Furthermore, means to analyse and derive the desired performance metrics from the input values have to be found and/or developed.
Next: Future Work
Up: Discussion
Previous: Performance Meta-Models
Contents
Index
Snowball
2007-03-16