WBS (English)

De productpatterns_wiki
Revisión a fecha de 15:47 22 feb 2015; PfcEsther (Discusión | contribuciones)

(dif) ← Revisión anterior | Revisión actual (dif) | Revisión siguiente → (dif)
Saltar a: navegación, buscar

Spanish.jpg Español

Spanish.jpg Español

Box-In.png
Inputs

  • Tasks.

Box-Out.png
Outputs

  • Graphical representation of the different ordered tasks.
  • Significant goals to achieve.
  • Identification of work packages belonging to the task.

Star.png
Solution

process-descending-24px.png
Process

Diagrama WBS.PNG

time-24px.png
Development timeo

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

bricks.png
Related Patterns

  • None

Search-32px.png
Quality Controllers

  • None

template.png
Templates
  • None

</div>

<h2 class="editable" style=padding-top:15px>
stuff.png
Examples</h2>
<h2 class="editable" style=padding-top:15px>
tool.png
Support Tools</h2>
</div>
<h2 class="editable">
start-flag.png
Initial Context</h2> This product can be used in any project and used as a tool for organizing, monitoring and estimation. It is a prerequisite to plan the project itself, in which starting from the definition of the project objectives, you come to the structuring of the various constituent activities.
<h2 class="editable" style=padding-top:15px>
end-flag.png
Resulting context</h2>

The project manager will get a graphical representation of the different activities that must be carried out for the realization of a project. These activities will be grouped by work packages.

<h2 class="editable" style=padding-top:15px>
cloud.png
Issue>

The project manager will be able to divide the project into portions that are subsequently easy to plan in time, cost, resources ... and serve to organize projects efficiently.

<h2 class="editable" style=padding-top:15px>
forces.png
Restrictions (Forces)</h2>
  • Characteristics of organizations: This pattern can be used in existing projects in any company.
  • System Type to develop: This product can be used in projects in which user requirements are changing.
  • Type of customer: It must exist or be achieved, the target area development business being involved in achieving it.
  • Heuristics for use: If you need urgent application or dispose of some of its functionality.
<h2 class="editable" style=padding-top:15px>
roles.png
Roles</h2>
  • Project Manager
<h2 class="editable" style=padding-top:15px>
lightbulb.png
Lessons Learned</h2>
  • None
<h2 class="editable" style=padding-top:15px>
award.png
Maturity level</h2>
  • Not applicable
<h2 class="editable" style=padding-top:15px>
Options.png
Basic Knowledge and Skills</h2>

board-24px.png
Knowledge

  • Software requirements definition.
  • Background information on Logic Programming and Software Engineering I.
  • Accustomed to using a particular paradigm.

help-24px.png
Abilities

  • Capacity of Abstraction.
  • Capacity of Analysis.
<h2 class="editable" style=padding-top:15px>
Information-Sources.png
Information Resources</h2>
  • Gonzalo, Agustín y de Amescua Antonio.Gestión del proceso software. Ed. Centro de Estudios Ramón Areces. 2002.
  • DeMarco, Tom. Controlling software projects. Ed Yourdon Press. 1982.
  • Sommerville, Ian. Ingeniería del software. Ed. Addison-Wesley. 2002.
  • Dolado, J.L. y Fernández, L. Medición para la gestión en la ingeniería del software. Ed. RAMA. 2000.
  • McConell, Steve. Desarrollo y gestión de proyectos informáticos. Ed. Mc Graw Hill. 1997.
  • Pressman, R. Ingeniería del Software, Un enfoque práctico, 6ª edición. Ed. Mc Graw Hill. 2005.
  • López-Cortijo y Amescua. Ingeniería del Software: Aspectos de Gestión. Ed. Instituto Ibérico de la Industria del Software. 1998.
  • Garmus, David y Herron, David. Measuring the software process: a practical guide to functional measurements. Ed. Yourdon Press computing series. 1995.