rect rect rect rect rect rect 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
white space
engineering
Welcome
Architecture Tradeoff Analysis
CERT Coordination Center
COTS-Based Systems
Overview
Activity Areas
Products and Services
CBS Team
References
Events
TIDE
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
Performance - Critical Systems
Information Repositories
Team & Personal Software Process
Product Line Practice
Software Engineering Measurement & Analysis (SEMA)
Complete Technical Project List
Common Acronyms
Technical Initiatives
Conferences
Education & Training
white space
About SEI|Mgt|Eng|Acq|Collaboration|Prod.& Services|Pubs
pixel
Rollover Popup Hints for Topic Navigation Buttons above
pixel
Strawman Outline for a CBSE Handbook


Second International Workshop on
Component-Based Software Engineering

A Proposed Outline for a Handbook of CBSE

  1. Principles of CBSE
    • Definition
      • What are components?
      • What is CBSE?
      • Central ideas, principles, features
      • Terminology
    • How does CBSE differ (and relate to) similar fields?
      • Conventional OO development
      • Software reuse
      • Patterns and frameworks
      • Software/domain-specific architectures
      • Distributed object architectures
      • COTS
  2. Practices of Adopting CBSE
    • CBSE Processes/Methodologies
      • Typical CBSE life-cycle phases and activities
      • How do/should CBSE processes differ from conventional development processes?
      • Component market issues
      • Economic and pricing models
      • Metrics for CBSE projects
    • Organizational Issues
      • Transition from conventional to component-based development
      • Human factors, issues, and barriers related to CBSE adoption
      • Project management
      • Education and training
      • Legal issues
    • State-of-the-Practice
      • Market analysis
        • # and % of companies adopting CBSE
        • # and sizes of CBSE projects
        • Technologies used
        • Reasons/barriers for not using
        • Market trends
      • Case studies
        • Success stories
        • Failures/lessons learned
  3. Technology for Supporting CBSE
    • Development Support
      • Models, languages, and notations
        • ADLs (Architecture description languages)
        • CDLs (Component specification languages)
        • IDLs (Interface definition languages)
        • UML
        • Other modeling and design notations
      • Reusable components
        • Component libraries; search engines
        • Domain architectures
        • Repositories of common system templates/patterns
      • Tools and environments
        • Component fabrication/generation tools
        • Component assembly tools
        • Component testing and evaluation technologies
        • CBSE project management and estimating tools and techniques
    • Run Time Support
      • Run-time architectures/frameworks
        • CORBA, DCOM, Javabeans, BOFs, etc.
      • Integration technologies/tools
        • Wrappers, mediators, interfaces to legacy systems, etc.
    • Maintenance and Reengineering Support
  4. Research Issues and Directions
    • Subjects in this section will intersect with topics above
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 2004 by Carnegie Mellon University
URL: http://www.sei.cmu.edu/strawman.html
Last Modified: 3 February 2003