• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

Card Range To Study

through

image

Play button

image

Play button

image

Progress

1/11

Click to flip

Use LEFT and RIGHT arrow keys to navigate between flashcards;

Use UP and DOWN arrow keys to flip the card;

H to show hint;

A reads text to speech;

11 Cards in this Set

  • Front
  • Back
CBSE
Component-based software engineering (CBSE) is an approach to software development that relies on reuse.
CBSE emerged from the _______
emerged from the failure of object-oriented development to support effective reuse. Single object classes are too detailed and specific.
Components vs. object classes
Components are more abstract than object classes and can be considered to be stand-alone service providers.
Component in CBSE
A component is an independent executable entity that can be made up of one or more executable objects.
CBSE Essentials (4)
1) Independent components specified by their interfaces.

2) Component standards to facilitate component
integration.

3) Middleware that provides support for component interoperability.

4) A development process that is geared to reuse.
CBSE & SE Design Principles
 Components are independent so that they do not interfere with each other
 Component implementations are hidden
 Communication is through well-defined interfaces
 Component platforms are shared and dev. costs are reduced
CBSE Challenges
1) Component Trustworthiness
2) Component Certification
3) Emergent Property Prediction
4) Requirements Trade-offs
----how do we do trade-off analysis b/t the features of 1 component and another
Component Characteristics (5)
1) Standardized
2) Independent
3) Composable
---all external interactions must take place through publicly defined interfaces
4) Deployable
---stand-alone, binary executable (no compilation req'd)
5) Documented

DISCD
Component Interfaces: "Provides" interface
Defines the services that are provided by the
component to other components

Ex: the methods
Print
GetQueue
Remove
etc.
Component Interfaces: "Requires" interface
Defines what services must be made available for the component to execute as specified.

Ex:
GetPDfile
PrinterInt

where 'PrinterInt' is a service that transfers commands to a specified printer
Component Models (defn)
A component model is a definition of standards for component implementation, documentation, and deployment.