Next: Assembly
Up: Development Process Model
Previous: QoS Analysis
Contents
Index
Compared to classical development processes the provisioning workflow resembles the classical implementation workflow. However, one of the assets of component-based development is reuse, i.e. the incorporation of components developed by third parties. During the provisioning workflow 'make-or-buy' decisions are made for individual components. Components that cannot be purchased from third-parties have to be implemented according to the specifications from the corresponding workflow. Consequently, the provisioning workflow receives the component specifications and architecture as well as technical constraints as inputs. The output of this workflow are implemented software components.
Snowball
2007-03-16