Diferencia entre revisiones de «Class Diagram»

De productpatterns_wiki
Saltar a: navegación, buscar
m (Protegió «Class Diagram» ([Editar=Solo permitir usuarios autoconfirmados] (indefinido) [Pueden trasladar=Solo permitir usuarios autoconfirmados] (indefinido)))
Línea 34: Línea 34:
 
<ul style= "margin-left:130px;">  
 
<ul style= "margin-left:130px;">  
 
*To acquire the necessary knowledge to develop the software product:
 
*To acquire the necessary knowledge to develop the software product:
*To create the pattern Product:  
+
*To create the Product Pattern:  
*To apply the pattern of Product:  
+
*To apply the Product Pattern:  
 
</ul></div>
 
</ul></div>
  

Revisión de 12:53 22 feb 2015

Spanish.jpg Español

Box-In.png
Inputs

  • Use Case Diagram (using UML)
    • Can it be used configuration management ?: Yes
  • Requirements Specification Document
    • Can it be used configuration management ?: Yes

Box-Out.png
Outputs

  • Class Diagram (using UML)
    • Can it be used configuration management ?: Yes

Star.png
Solution

time-24px.png
Development time

    • To acquire the necessary knowledge to develop the software product:
    • To create the Product Pattern:
    • To apply the Product Pattern:

video-24px.png
Explanatory video

    • Not applicable

Search-32px.png
Quality Controllers

  • None

template.png
Templates

  • Elements of a class diagram

start-flag.png
Initial Context

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.

end-flag.png
Resulting context

A diagram, that shows through classes, the logical components that are responsible for the operation of the system, is obtained.

cloud.png
Issue

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.

forces.png
Restrictions (Forces)

  • Type of Organization: SMEs, Large Companies.
  • System Type: It applies to all types of systems.
  • Programming Paradigm: OO (Object Oriented).

roles.png
Roles

  • Analyst
  • Project Manager

lightbulb.png
Lessons Learned

  • 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.

award.png
Maturity level

  • This pattern Product is not related to any level of maturity.

Options.png
Basic Knowledge and Skills

board-24px.png
Knowledge

  • Intermediate knowledge of UML.
  • Interpretation of use case diagrams.

help-24px.png
Abilities

  • Capacity of abstraction.
  • Capacity of Analysis.
  • Holistic or systemic view of problems.

Information-Sources.png
Information Resources

  • 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.