Component-Based Software Engineering

1
Component-Based Software Engineering

• Trying to Maximize Reuse

2
Types of Reuse

• Software Libraries
• Function libraries e.g., stdlib.h, math.h
• Class Libraries e.g., string and iostream
• Class Architectures e.g., wxWidgets and OpenGL
• Distributed Architectures CORBA and .NET
• Technical Representations
• Specifications e.g., Diglog as model for Logic
  Learner
• Architectures
• Application Wide client/server, peer-to-peer,
  data-centered, data flow, main/subprogram
• Design Patterns factory, observer, blackboard,
  etc.
• Other
• Data and Databases
• Processes

3
Sources for Components

• In-House Developed by the company as part of
  their regular business.
• Commercial-off-the-Shelf (COTS) Purchased from
  the open market.
• Latent Existing in current applications, but
  not yet packaged.
• Engineered Custom components for the
  application at hand.

4
The CBSE Approach

• Two parallel tracks Domain Engineering and
  Component Dev
• Domain Engineering
• Analysis of domain to identify components (or
  structure points) for reuse
• Component-based Development
• Fitting components for the application

5
Additional Points of Emphasis

• Definitions for components general, run-time,
  software, business (pg 817)
• Activities of Domain Engineering identify,
  construct, catalog, report (pg 819)
• Definition of Structural Models and Structure
  Points (pgs 821-822)