Properties, public methods, and events

Interfaces and implementation of the interfaces

JavaDoc information and manifest file contents

The source code plus supporting classes

Modify its attributes and appearance

Introspect properties, methods, and events described in a BeanInfo class

Save and restore its states

Call other beans for services

Source bean, target bean

Listener bean, target bean

Listener bean, source bean

Target bean, source bean

 Components become tightly coupled with specific implementations of their dependencies.

The control of object creation and dependency management is transferred to an external entity.

Components take direct control over the instantiation and management of their dependencies.

IoC aims to increase the complexity and dependencies between components.

Neither approach explicitly defines the dependencies of a component.

Dependency Injection makes dependencies explicit through mechanisms like constructor parameters.

Service Locator makes dependencies more explicit by listing them in a central registry.

Both Dependency Injection and Service Locator hide the dependencies of a component.

Different component technologies have the same component infrastructure

Different component technologies have different component infrastructures

Component infrastructure has not been developed yet

Software components are not associated with their component infrastructure

Component-Oriented Programming (COP)

Structured Programming (SP)

Object-Oriented Programming (OOP)

eXtreme Programming (XP)

Both reside in the same process and share memory.

Components typically operate in different environments, often requiring a runtime infrastructure.

Objects heavily rely on runtime infrastructure for basic operation.

Components primarily utilize inheritance for code reuse, unlike objects.

A component does not need many clients to be economically viable

The interplay of components is not a problem of software engineering

A component standard specifies the necessary interfacing of certain components

as is needed to allow clients and vendors to work together

With standards, we could build a general-purpose component

What a valid component is and how to create a new component under the

component infrastructure

A collection of connectors and supporting facilities for component assembling

The interface to another component

How to put components into a working environment