The basic, underlying framework and facilities for components construction

and management

The interface between components

The standard used to develop components

The communication between components

Encapsulation for information hiding

Divide and conquer for managing complexity

Interface specification

Unification of data and function

To promote the development of software through the assembly of pre-built, independent units.

To tightly couple software modules for enhanced performance.

To increase the complexity of software systems for better functionality.

To eliminate the need for software maintenance and upgrades.

SOAP

REST

WSDL

UDDI

Ball and socket symbols, where a ball represents a provided interface and a socket represents a required interface.

Use case diagrams showing system functionalities.

Activity diagrams illustrating the component's behavior.

Class diagrams with inheritance arrows.

Development with reuse, in which a new application is constructed by assembling

existing reusable components

Service-oriented computing, where nonfunctional requirements plays a critical

role

Enterprise computing, where server-side programming plays a critical role

Development for reuse, in which a new component is developed and stored

in a reusable library for future reuse

Reusable components have less overhead at run-time

Component-based software has simpler architecture

Reusable components have usually been tested through the validation process

and real usage for a long time

Component-based software was developed using Java

It primarily focuses on the internal implementation details of individual components.

It defines the structure of the system, including components, connectors, their properties, and relationships.

It is concerned with the specific programming language used to develop the components.

It mainly deals with the user interface design of the application.