It has the description of the system from the user perspective (eg in a use cases diagram) and it is desired to create a diagram that describes the structure of a software system, showing the components or pieces of software that is responsible for the operation of the system.
A diagram, that shows through classes, the logical components that are responsible for the operation of the system, is obtained.
It is needed to create a representation of components (classes and objects) that implement the system operation. This representation should show what the system can do and how to be built.
- Type of Organization: SMEs, Large Companies.
- System Type: It applies to all types of systems.
- Programming Paradigm: OO (Object Oriented).
- Benefits of using this pattern [Fuensanta Medina-Dominguez, 2008]
- The static view of the software you get when you use this pattern system is based on UML, which facilitates the description of objects or real world entities that interact with the system.
- Amescua A., et al. (2003). Análisis y Diseño Estructurado y Orientado a Objetos del Sistema Informáticos. McGraw Hill/Interamericana de España, S.A.U.
- Ferré Grau, X & Sanchez-Segura, M. (2004). Desarrollo Orientado a Objetos con UML. Recuperado el 2009-11-26 de http://www.clikear.com/manuales/uml/index.aspx.
- Fowler, M. (2004). UML distilled: a brief guide to the standard object modelling language. Addison-Wesley.
- Jacobson, I. & Booch, G.(1999). The unified software development process. Addison-Wesley.
- Rumbaugh, J. & Jacobson, I. (2005). The unified modeling language reference manual. Addison-Wesley.
- Rumbaugh, J. (2005). Object-Oriented Modelling and Design. Prentice Hall.