Diferencia entre revisiones de «Operation Contract»

De productpatterns_wiki
Saltar a: navegación, buscar
m (Protegió «Operation Contract» ([Editar=Solo permitir usuarios autoconfirmados] (indefinido) [Pueden trasladar=Solo permitir usuarios autoconfirmados] (indefinido)))
Línea 36: Línea 36:
 
<ul style= "margin-left:130px;">  
 
<ul style= "margin-left:130px;">  
 
*To acquire the necessary knowledge to develop the software product: 2 hours
 
*To acquire the necessary knowledge to develop the software product: 2 hours
*To create the pattern of Product: 2 hours
+
*To create the Product Pattern : 2 hours
*To apply the pattern of Product: 2 days
+
*To apply the Product Pattern: 2 days
 
</ul></div>
 
</ul></div>
  
Línea 79: Línea 79:
 
<div id="section_12">
 
<div id="section_12">
 
<span id="Contexto_Inicial"></span><h2 class="editable">[[Archivo:start-flag.png|left|24px|start-flag.png]]Initial Context</h2>
 
<span id="Contexto_Inicial"></span><h2 class="editable">[[Archivo:start-flag.png|left|24px|start-flag.png]]Initial Context</h2>
A Craig Larman method is carried out  to develop a software system, and it has been created a sequence diagrams of system use cases.
+
A [[Craig Larman Method]] is carried out  to develop a software system, and it has been created a sequence diagrams of system use cases.
 
</div>
 
</div>
  
Línea 89: Línea 89:
 
<div id="section_14">
 
<div id="section_14">
 
<span id="Problema"></span><h2 class="editable" style=padding-top:15px>[[Archivo:cloud.png|left|24px|cloud.png]]Issue</h2>
 
<span id="Problema"></span><h2 class="editable" style=padding-top:15px>[[Archivo:cloud.png|left|24px|cloud.png]]Issue</h2>
It has been generated the sequence diagrams system of the use case of a software system that is being developed using the Craig Larman Method, however, it wanted to be detailed each of the activities represented on it sequence diagrams system to prevent ambiguities in implementation.
+
It has been generated the sequence diagrams system of the use case of a software system that is being developed using the [[Craig Larman Method]], however, it wanted to be detailed each of the activities represented on it sequence diagrams system to prevent ambiguities in implementation.
 
</div>
 
</div>
  

Revisión de 12:38 22 feb 2015

Spanish.jpg Español

Box-In.png
Inputs

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

Box-Out.png
Output

  • Operating Contracts
    • Can it be used configuration management ?: Yes

Star.png
Solution

process-descending-24px.png
Process

Contrato de Operación.png

time-24px.png
Development time

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

video-24px.png
Explanation video


Search-32px.png
Quality Controllers

  • None

start-flag.png
Initial Context

A Craig Larman Method is carried out to develop a software system, and it has been created a sequence diagrams of system use cases.

end-flag.png
Resulting context

It has been created a detailed description of each of the activities represented in the system sequence diagram.

cloud.png
Issue

It has been generated the sequence diagrams system of the use case of a software system that is being developed using the Craig Larman Method, however, it wanted to be detailed each of the activities represented on it sequence diagrams system to prevent ambiguities in implementation.

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
  • Customer
  • Project Manager
  • System Users

lightbulb.png
Lessons Learned

  • None

award.png
Maturity level

  • Maturity Level 2 CMMI.

Options.png
Basic Knowledge and Skills

board-24px.png
Knowledge

  • Definition of software requirements (functional and non-functional).
  • Craig Larman Method
  • Notions of UML, especially the technique of modeling of use cases.

help-24px.png
Abilities

  • Capacity of abstraction.
  • Capacity of Analysis.

Information-Sources.png
Information Resources.

  • 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.
  • Larman, C. (2001). Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process (2da. ed.). Prentice Hall.
  • 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.