A QoS Driven Development Process Model for Component-Based Software Systems
Non-functional specifications of software components are considered an important asset in constructing dependable systems, since they enable early Quality of Service (QoS) evaluations. Several approaches for the QoS analysis of component-based software architectures have been introduced. However, most of these approaches do not consider the integration into the development process sufficiently. For example, they envision a pure bottom-up development or neglect that system architects do not have complete information for QoS analyses at their disposal. We extent an existing component-based development process model by Cheesman and Daniels to explicitly include early, model-based QoS analyses. Besides the system architect, we describe further involved roles. Exemplary for the performance domain, we analyse what information these roles can provide to construct a performance model of a software architecture.
Unable to display preview. Download preview PDF.
- 2.Cheesman, J., Daniels, J.: UML Components: A Simple Process for Specifying Component-based Software Systems. Addison-Wesley, Reading (2001)Google Scholar
- 3.Grunske, L., Kaiser, B., Papadopoulos, Y.: Model-Driven Safety Evaluation with State-Event-Based Component Failure annotations. In: Heineman, G.T., Crnković, I., Schmidt, H.W., Stafford, J.A., Szyperski, C.A., Wallnau, K. (eds.) CBSE 2005. LNCS, vol. 3489, pp. 33–48. Springer, Heidelberg (2005)CrossRefGoogle Scholar
- 4.Hamlet, D., Mason, D., Woit, D.: Properties of Software Systems Synthesized from Components. Case Studies, vol. 1, pp. 129–159. World Scientific Publishing Company, Singapore (2004)Google Scholar
- 6.Object Management Group OMG. UML Profile for Schedulability, Performance and Time (2005), http://www.omg.org/cgi-bin/doc?formal/2005-01-02
- 10.Szyperski, C., Gruntz, D., Murer, S.: Component Software: Beyond Object-Oriented Programming. Addison-Wesley, Reading (2002)Google Scholar