Next: Foundations
Up: Introduction
Previous: Motivation
Contents
Index
This report is structured as follows:
- Chapter 2: lays the foundation to understand the concepts of the PCM. First, the QoS-driven development process model targeted by the PCM is introduced (2.1). Interfaces and entities are ... (2.2). Parametric contracts enable adapting the pre-/postconditions of components (2.4). As QoS of component depends on the context a component is executed in, the PCM introduces a special context concept (2.4). To specify resource demands, random variables can be used in the PCM (2.5).
- Chapter 3: presents the concepts of the PCM and is structured after the roles involved in modeling. Component developers specify interfaces, services, components, and QoS properties (3.1). Software architects use the specifications of component developers to build architectures (3.2). Deployers model the resource environment of an architecture (3.3). Domain experts provide information about the user behaviour (3.4). QoS experts collect the information from the different roles, use prediction tools and pre-interpret the results (3.5).
- Chapter 4: contains the technical reference of the PCM.
- Chapter 5: discusses the PCM, describes related work, open issues, as well as limitations and assumptions present in the PCM.
Next: Foundations
Up: Introduction
Previous: Motivation
Contents
Index
Snowball
2007-03-16