Hosta

by | Mar 16, 2018 | Hosta

How Can We Help?
You are here:
< Back
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Pmffl (talk | contribs)
Extended confirmed users
4,342 edits
→‎History: revise
Pmffl (talk | contribs)
Extended confirmed users
4,342 edits
revise
Line 1: Line 1:
{{Short description|Identifiable part of software system}}
{{Short description|Distinct part of software system}}


A '''software component''' is an identifiable part of a [[software system]] that provides a clear [[interface (computing)|interface]] with other parts.
A '''software component''' is a distinct part of a [[software system]] that provides a clear [[interface (computing)|interface]] with other parts.


In practice, this notion can be broad, spanning a range of [[Abstraction (computer science)|abstraction]] levels from individual [[Function (computer programming)|functions]] to a large [[subsystem]], such as a [[software engine]] or a [[web service]]. However, [[component-based software engineering]] advocates thorough planning in the design and arrangement of components.
In practice, the [[Abstraction (computer science)|abstraction]] levels of components can range from individual [[Function (computer programming)|functions]] to a large subsystem, such as an [[software engine|engine]] or a [[web service]]. To help manage [[Programming complexity|complexity]], [[component-based software engineering]] encourages thorough planning of component design.


==History==
==History==
The idea of reusable software components was promoted by [[Douglas McIlroy]] in his presentation at the [[NATO Software Engineering Conferences|NATO Software Engineering Conference]] of 1968.<ref>{{cite web |url=http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF |title=Mass produced software components |first=Malcolm Douglas |last=McIlroy |work=Software Engineering: Report of a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7-11 Oct. 1968 |publisher=Scientific Affairs Division, NATO |date=January 1969 |page=79}}</ref> (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 (Unix)|pipeline]] feature to the [[Unix]] [[operating system]].
The idea of [[reusability|reusable]] software components was promoted by [[Douglas McIlroy]] in his presentation at the [[NATO Software Engineering Conferences|NATO Software Engineering Conference]] of 1968.<ref>{{cite web |url=http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF |title=Mass produced software components |first=Malcolm Douglas |last=McIlroy |work=Software Engineering: Report of a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7-11 Oct. 1968 |publisher=Scientific Affairs Division, NATO |date=January 1969 |page=79}}</ref> (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 (Unix)|pipeline]] feature to the [[Unix]] [[operating system]].


[[Brad Cox]] refined the concept of a software component in the 1980s.<ref>{{cite web
[[Brad Cox]] refined the concept of a software component in the 1980s.<ref>{{cite web

Revision as of 03:27, 14 May 2024

A software component is a distinct part of a software system that provides a clear interface with other parts.

In practice, the abstraction levels of components can range from individual functions to a large subsystem, such as an engine or a web service. To help manage complexity, component-based software engineering encourages thorough planning of component design.

History

The idea of reusable software components was promoted by Douglas McIlroy in his presentation at the NATO Software Engineering Conference of 1968.[1] (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.[2] He attempted to create an infrastructure and market for reusable third-party components by inventing the Objective-C programming language.[3]

References

  1. ^ McIlroy, Malcolm Douglas (January 1969). "Mass produced software components" (PDF). Software Engineering: Report of a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7-11 Oct. 1968. Scientific Affairs Division, NATO. p. 79.
  2. ^ Rainer Niekamp. "Software Component Architecture" (PDF). Gestión de Congresos - CIMNE/Institute for Scientific Computing, TU Braunschweig. p. 4. Archived from the original (PDF) on 2012-03-28. Retrieved 2011-07-29. The modern concept of a software component largely defined by Brad Cox of Stepstone, => Objective-C programming language
  3. ^ Brad Cox (1991). Object Oriented Programming: An Evolutionary Approach. Addison Wesley. ISBN 0-201-54834-8.
Categories
Table of Contents