Jump to content

Software component: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
don't need that
→‎History: revise
Line 6: Line 6:


==History==
==History==
The idea that [[software]] should be componentized, built from reusable components, first became prominent with [[Douglas McIlroy]]'s address at the [[NATO]] conference on [[software engineering]] in [[Garmisch-Partenkirchen|Garmisch]], [[Germany]], 1968,<!-- The practice of modular programming existed before 1968 I am certain --> titled ''Mass Produced Software Components''.<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> The conference set out to counter the so-called [[software crisis]]. McIlroy's subsequent inclusion of [[Pipeline (Unix)|pipes and filters]] into the [[Unix]] [[operating system]] was the first implementation of an infrastructure for this idea.
The idea software components [[Douglas McIlroy]] at the [[NATO ]] 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> to the so-called [[software crisis]]. McIlroy of [[Pipeline (Unix)|]] 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 00:23, 14 May 2024

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

In practice, this notion can be broad, spanning a range of abstraction levels from individual 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.

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.