Abstract
SOFTWARE has since its inception been packaged in self-contained pieces, for the obvious reason that only such pieces can be exchanged and used by others. Indeed, the original IBM user group whose purpose was to exchange code is called SHARE (Society to Help Avoid Redundant Effort according to one source); it was at first concerned with assembly-language subroutines for the 701/704 mainframes. A collection of subroutines is called a ‘library,’ and includes not only code but documentation.With the advent of FORTRAN, subroutine sources became far easier to read and understand—this goes by the misnomer of ‘self-documenting code.’
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 2010 Springer Science+Business Media, LLC
About this chapter
Cite this chapter
Hamlet, D. (2010). Software Components and Component-based Development. In: Composing Software Components. Springer, Boston, MA. https://doi.org/10.1007/978-1-4419-7148-7_3
Download citation
DOI: https://doi.org/10.1007/978-1-4419-7148-7_3
Published:
Publisher Name: Springer, Boston, MA
Print ISBN: 978-1-4419-7147-0
Online ISBN: 978-1-4419-7148-7
eBook Packages: Computer ScienceComputer Science (R0)