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.