"This may surprise some people. Many think the primary objective of components is reuse. They want to design something once and use it over and over again in different contexts, thereby realizing large productivity gains, taking advantage of best-in-class solutions, the consequent improved quality, and so forth. These are admirable objectives, but the main driver today is that things keep changing, and often—as with business-to-business electronic commerce—there is no longer any hope that centralized control can be exerted. In such an environment one of the primary objectives of a component is that it must be easily replaceable—either by a completely different implementation of the same functions or by an upgraded version of the current implementation. This places the emphasis on the architecture of the system, on being able to manage the total system, as its various components evolve and its requirements change, rather than seeking to ensure that individual components are reusable by multiple component systems (p. 2)" (Cheesman).
Português:
requisitos em mudança,
John Cheesman
Cheesman, John; Daniels, John.
UML Components A Simple Process for Specifying Component-Based Software. Addison-Wesley.
Francisco S. Marcondes. Disponível em <
http://orcid.org/0000-0002-2221-2261 >. Acesso em 2 jun.
2020.
--
GregorioIvanoff - 18 Jan 2022
to top