000			02107nam a22001937a 4500
005			20250702104102.0
008			250702b |||||||| |||| 00| 0 eng d
020			_a9783540626954 _qhbk
041			_aeng
082			_a005 _bSAM
100			_aSametinger J.
245			_a Software Engineering With Reusable Components _cSametinger
260			_aBerlin _b Springer, _c1997
300			_axvi; 272 p. _c24 cm.
504			_aBib and Ref
520			_aSoftware is rarely built completely from scratch. To a great extent, existing software documents (source code, design documents, etc.) are copied and adapted to fit new requirements. Yet we are far from the goal of making reuse the standard approach to software development. Software reuse is the process of creating software systems from existing software rather than building them from scratch. Software reuse is still an emerging discipline. It appears in many different forms from ad-hoc reuse to systematic reuse, and from white-box reuse to black-box reuse. Many different products for reuse range from ideas and algorithms to any documents that are created during the software life cycle. Source code is most commonly reused; thus many people misconceive software reuse as the reuse of source code alone. Recently source code and design reuse have become popular with (object-oriented) class libraries, application frameworks, and design patterns. Software components provide a vehicle for planned and systematic reuse. The software community does not yet agree on what a software component is exactly. Nowadays, the term component is used as a synonym for object most of the time, but it also stands for module or function. Recently the term component-based or component-oriented software development has be­ come popular. In this context components are defined as objects plus some­ thing. What something is exactly, or has to be for effective software develop­ ment, remains yet to be seen. However, systems and models are emerging to support that notion
650			_aSoftware Engineering Software Reuse Software Engineering
942			_cREF
999			_c574614 _d574614