Resumen
When a business unit is looking for a software solution to a problem there are several technical solutions to which they can look, including: turnkey solutions, component-based framework solutions and custom development solutions. Turnkey solutions are ready to go "out of the box," often requiring configuration work. Custom development solutions typically involve building most of the major system functionality from scratch. Whereas component-based framework solutions elevate abstractions software engineers use to identify, discuss, solve and implement systems. This section focuses on component-based frameworks; what they look like, how to identify them, model them, build them, extend them, use them and how to apply to e-business solutions. Component-based framework solutions are partial implementations, specifying the nature and way to extend the framework with pluggable components. Designing, building and testing component-based frameworks require considering several things including static models that illustrate component structure, dynamic models that illustrate component collaboration, as well as the technology to implement the component framework

Resumen
The article presents information on designing component-based framework solutions. Designing systems using proven solutions such as patterns and frameworks improves the productivity of software engineers. Achieving productivity and artifact improvement affects several stakeholders in the organization, directly and indirectly. The list of stakeholders tends to include, software architects, developers, IT managers, business managers, and ultimately the customer. Within the software industry several pundits have articulated and presented initial reusable artifacts and patterns. Some of the early pattern work, mostly concerning human interface patterns, was done by Ward Cunningham and Kent Beck in 1987. Several years later more discussions at conferences such as OOPSLA were held with individuals such as Erich Gamma and Richard Helm. Architectural patterns or frameworks provide descriptions of the software architecture. Typically frameworks provide key decision points in the software to help comprise the architecture. In the Unified Modeling Language (UML) there are several ways to view software architecture, often referred to as the five views of software architecture. The article illustrates only the logical view of the architecture for the Observable Party Account framework. The article presents several examples which illustrates the process of using the UML to design a component-based framework using existing patterns.