Software component

A software component is a modular unit of software that encapsulates specific functionality.

Uses your system voice; voice and rate in settings.

≈ 2 min read

Cite, export and learn8 citation formats · 8 exports · lesson and quiz

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

A software component is a modular unit of software that encapsulates specific functionality. The desired characteristics of a component are reusability and maintainability.

Value

Components allow software developers to assemble software with reliable parts rather than writing code for every aspect. This makes implementation more like factory assembly than custom building.

Attributes

Desirable attributes of a component include but are not limited to: Cohesive encapsulates related functionality Reusable Robust Substitutable can be replaced by another component with the same interface Documented Tested

Third-party

Some components are built in-house by the same organization or team building the software system. Some are third-party, developed elsewhere and assembled into the software system.

Component-based software engineering

For large-scale systems, component-based development encourages a disciplined process to manage complexity.

Framework

Some components conform to a framework technology that allows them to be consumed in a well-known way. Examples include: CORBA, COM, Enterprise JavaBeans, and the .NET Framework.

Modeling

]] Component design is often modeled visually. In Unified Modeling Language (UML) 2.0 a component is shown as a rectangle, and an interface is shown as a lollipop to indicate a provided interface and as a socket to indicate consumption of an interface.

History

The idea of reusable software components was promoted by Douglas McIlroy in his presentation at the NATO Software Engineering Conference of 1968. (One goal of that conference was to resolve the so-called software crisis of the time.) In the 1970s, McIlroy put this idea into practice with the addition of the pipeline feature to the Unix operating system.

Brad Cox refined the concept of a software component in the 1980s. He attempted to create an infrastructure and market for reusable third-party components by inventing the Objective-C programming language. IBM introduced System Object Model (SOM) in the early 1990s.

Microsoft introduced Component Object Model (COM) in the early 1990s. Microsoft built many domain-specific component technologies on COM, including Distributed Component Object Model (DCOM), Object Linking and Embedding (OLE), and ActiveX.

Text derived from https://en.wikipedia.org/w/index.php?oldid=1376560280 under CC BY-SA 4.0; modifications have been made.

Words in each sectionHistoryHistoryHistory: 150 words150ModelingModelingModeling: 43 words43AttributesAttributesAttributes: 30 words30ValueValueValue: 27 words27FrameworkFrameworkFramework: 27 words27Third-partyThird-partyThird-party: 26 words26Component-based softwar…Component-based software engineeringComponent-based software engineering: 12 words12
Words in each section. Measured from the stored article body; sections below the minimum are not plotted.

Provenance

snapshot enwiki-001376560280 · captured 2026-09-24 · ledger · version history

Cite this page as: encyclopegia.org, “Software component”, snapshot enwiki-001376560280. https://encyclopegia.org/a/software-component

Sources cited in this revision

6 named source(s) extracted from the cited revision. A source with no author is shown by its publication; nothing is invented.