rect
You are viewing an archived version of CBSE 1999. This page has been archived via the Internet Archive Wayback Machine for the ICSA conference series history. Some links on this page might not work.
← return to the ICSA homepage.
General Navigation Buttons - Home | Search | Contact Us | Site Map | Whats New
engineering graphic
Engineering Practices
Welcome
Architecture Tradeoff Analysis
CERT Coordination Center
COTS-Based Systems
Overview
Activity Areas
Products and Services
CBS Team
References
Events
What's New
Opportunities to work with us
Briefings, Courses, and Workshops
Spiral Development Workshops
CURE (COTS Usage Risk Evaluation)
COTS-Based Systems Monographs
COTS_Spot Column
Little Red Book
Dependable System Upgrade
Information Repositories
Personal & Team Software Process
Product Line Practice
Software Engineering Measurement & Analysis (SEMA)
Complete Technical Project List
Common Acronyms
Featured Publications
Technical Initiatives
Courses
Conferences
About SEI|Mgt|Eng|Acq|Collaboration|Prod.& Services|Pubs
Rollover Popup Hints for Topic Navigation Buttons above
Conclusion and Further Work


Next: References Up: Componentware - Methodology and Process Previous: Component Developer Issues

Conclusion and Further Work

In this paper, we have outlined an overall methodology for componentware consisting of four essential building blocks: a Formal System Model , Description Techniques , a Process Model , and Tools . We have presented a modular and adaptable process model suited for componentware based on an overall result resp. task structure and a set of new roles and tasks performing process patterns to fill the result structure.

We think that this work could be part of the CBSE handbook--Chapter 2.1 and 2.2 [CBS99]. We know that we still need to provide further work, especially with respect to refining and elaborating a more detailed result structure. The final result structure will be a combination of the result structures in existing process models, like the RUP [Iva99] or the V-Model [IAB98], tailored to the specific needs of componentware. It will also be elaborated and enhanced with additional aspects, especially with respect to economical and management-related aspects. Based on this result structure, we have to work out the life-cycle and typical activities in componentware projects. Then we have to elaborate a clear understanding about the different roles and responsibilities in component-based development projects.

Finally, the proposed process model and its accompanying pattern language (cf. [BRSV98a,ABD+99]) are far from being complete--both structure and content of the pattern catalog are not sufficiently elaborated. For the CBSE handbook we have to expand and improve the patterns. Furthermore, we have to present existing process models as process patterns, as we already did in [ABD+99]. Thus, the CBSE handbook will contain a set of process patterns which can be tailored individually to the specific needs of the current project.

=


Next: References Up: Componentware - Methodology and Process Previous: Component Developer Issues
Andreas Rausch
3/22/1999
 

 

 

 

contact the organizers
download the PDF file


The Software Engineering Institute (SEI) is a federally funded research and development center sponsored by the U.S. Department of Defense and operated by Carnegie Mellon University.

Copyright 2001 by Carnegie Mellon University
URL: http://www.sei.cmu.edu/papers/41/node11.html
Last Modified: 27 September 2000