next up previous contents index
Next: Requirements Up: Component-based Development Process Previous: Roles in Component-based Development   Contents   Index


Development Process Model

In the following, the roles described in the former section are integrated into a development process model featuring QoS analysis. We focus on the development process that is concerned with creating a working system from requirements and neglect the concurrent management process that is concerned with time planning and controlling. We base our model on the UML-centric development process model described by Cheeseman and Daniels [5], which is itself based on the Rational Unified Process (RUP).

Figure 2.4: QoS Driven Process Model: Overview
Image process-model1

The main process is illustrated in Figure 2.4. Each box represents a workflow. The thick arrows between boxes represent a change of activity, while the thin arrows characterise the flow of artifacts between the workflows. The workflows do not have to be traversed linearly (i.e., no waterfall model). Backward steps into former workflows are allowed. The model also allows an incremental or iterative development based on prototypes.

The workflows requirements, provisioning, assembly, test, and deployment have mainly been inherited from the original model and will briefly be described in the following. The workflow ''specification'' has been slightly modified to explicitly include the interaction between component developer and software architect and the specification of extra-functional properties. The workflow ''QoS Analysis'' has been added to the model and will be described in detail below.



Subsections
next up previous contents index
Next: Requirements Up: Component-based Development Process Previous: Roles in Component-based Development   Contents   Index
Snowball 2007-03-16