Software component: Difference between revisions
Content deleted Content added
SoC not a benefit per se |
new Considerations section for stuff that's better here than the more narrow CBSE article |
||
| Line 1: | Line 1: | ||
{{Short description|Modular unit of software}} |
{{Short description|Modular unit of software}} |
||
A '''software component''' is a modular unit of [[software]] that [[Encapsulation (computer programming)|encapsulates]] |
A '''software component''' is a modular unit of [[software]] that [[Encapsulation (computer programming)|encapsulates]] of ]].<ref>{{cite web |last1=Pandey |first1=Pankaj |date=11 July 2023 |title=Tutorial notes: Software Components and Connectors |url=https://medium.com/@publicapplicationcenter/tutorial-notes-software-components-and-connectors-a425bfd984df |website=medium.com |access-date=14 May 2024}}</ref> |
||
==Considerations== |
|||
| ⚫ | Different types of components can be used to construct [[software system]] |
||
| ⚫ | Different types of components can be used to construct [[software system]]<ref>{{cite web |last1=Yadav |first1=Sunny |date=16 April 2024 |title=Types of Software Components — With Examples |url=https://www.linkedin.com/pulse/types-software-components-examples-sunny-yadav-ducaf |website=[[LinkedIn]] |access-date=14 May 2024}}</ref><ref>{{cite web |last1=Spacey |first1=John |date=6 October 2023 |title=7 Examples of Software Components |url=https://simplicable.com/IT/software-components |website=simplicable.com |access-date=14 May 2024}}</ref> For large-scale systems, [[component-based software engineering|component-based development]] encourages a disciplined process to manage [[Programming complexity|complexity]] and realize the benefits.<ref>{{cite web |author=[[Douglas C. Schmidt]] |title=Why Software Reuse has Failed and How to Make It Work for You |url=http://www.dre.vanderbilt.edu/~schmidt/reuse-lessons.html |access-date=14 May 2024}}</ref> |
||
A framework can be used to build components.<ref>{{cite journal | last1 = Crnkovic | first1 = I. | last2 = Sentilles | first2 = S. | last3 = Vulgarakis | first3 = A. | last4 = Chaudron | first4 = M. R. V. | year = 2011| title = A Classification Framework for Software Component Models | journal = IEEE Transactions on Software Engineering | volume = 37 | issue = 5| pages = 593–615 | doi = 10.1109/TSE.2010.83 | s2cid = 15449138 }}</ref><ref>{{Cite journal|last1=Lau|first1=Kung-Kiu|last2=Wang|first2=Zheng|date=2007|title=Software Component Models|journal=IEEE Transactions on Software Engineering|volume=33|issue=10|pages=709–724|doi=10.1109/TSE.2007.70726|issn=0098-5589}}</ref> Notable examples are [[Enterprise JavaBeans]], the [[Component Object Model]], the [[.NET Framework]], and [[Common Object Request Broker Architecture|CORBA]]. |
|||
==History== |
==History== |
||
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]]. |
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]]. |
||
Revision as of 00:11, 15 May 2024
A software component is a modular unit of software that encapsulates specific functionality. The desired characteristics of a component are reusability and maintainability.[1]
Considerations
Different types of components can be used to construct a software system,[2][3] including third-party components. For large-scale systems, component-based development encourages a disciplined process to manage complexity and realize the benefits.[4]
A framework can be used to build components.[5][6] Notable examples are Enterprise JavaBeans, the Component Object Model, the .NET Framework, and CORBA.
History
The idea of reusable software components was promoted by Douglas McIlroy in his presentation at the NATO Software Engineering Conference of 1968.[7] (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.[8] He attempted to create an infrastructure and market for reusable third-party components by inventing the Objective-C programming language.[9]
References
- ^ Pandey, Pankaj (11 July 2023). "Tutorial notes: Software Components and Connectors". medium.com. Retrieved 14 May 2024.
- ^ Yadav, Sunny (16 April 2024). "Types of Software Components — With Examples". LinkedIn. Retrieved 14 May 2024.
- ^ Spacey, John (6 October 2023). "7 Examples of Software Components". simplicable.com. Retrieved 14 May 2024.
- ^ Douglas C. Schmidt. "Why Software Reuse has Failed and How to Make It Work for You". Retrieved 14 May 2024.
- ^ Crnkovic, I.; Sentilles, S.; Vulgarakis, A.; Chaudron, M. R. V. (2011). "A Classification Framework for Software Component Models". IEEE Transactions on Software Engineering. 37 (5): 593–615. doi:10.1109/TSE.2010.83. S2CID 15449138.
- ^ Lau, Kung-Kiu; Wang, Zheng (2007). "Software Component Models". IEEE Transactions on Software Engineering. 33 (10): 709–724. doi:10.1109/TSE.2007.70726. ISSN 0098-5589.
- ^ 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.
- ^ 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
- ^ Brad Cox (1991). Object Oriented Programming: An Evolutionary Approach. Addison Wesley. ISBN 0-201-54834-8.