Diferencia entre revisiones de «PBS (English)»
De productpatterns_wiki
| Línea 47: | Línea 47: | ||
<div id="section_7"> | <div id="section_7"> | ||
<span id="Patrones_Relacionados"></span><h2 class="editable" style=padding-top:15px>[[Archivo:bricks.png|left|24px|bricks.png]]Related Patterns</h2> | <span id="Patrones_Relacionados"></span><h2 class="editable" style=padding-top:15px>[[Archivo:bricks.png|left|24px|bricks.png]]Related Patterns</h2> | ||
| − | *[[ | + | *[[RBS (English) | RBS]] |
| − | *[[ | + | *[[WBS (English) | WBS]] |
</div> | </div> | ||
Última revisión de 00:41 15 abr 2015
Inputs
- WBS chart
Outputs
- Products obtained in each task.
- Graphical representation of the different ordered tasks.
- Significant achieving goals.
- Identification of work packages belonging to the task.
Solution
Process
Development time
- To acquire the necessary knowledge to develop the software product: 4 hours.
- To create the Product Pattern: 1 day.
- To apply the Product Pattern: 2 hours.
Explanatory Video
Quality Controllers
- None
Templates
- None
Examples
Support Tools
- Word processor(Microsoft Word, OpenOffice Writer)
Initial Context
This product can be used in any project and used as a tool for organizing, monitoring and estimation. It is a prerequisite to planning the same project, in which starting from the definition of project objectives, you come to the structuring of the different activities and products obtained.
Resulting context
The project manager will initially have a graphical representation of the different activities that must be carried out for the realization of a project, where such activities will be grouped by work packages, each task will have associated the products obtained.
Issue
The project manager will be able to know that products obtained during each task.
Restrictions (Forces)
- 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.
Roles
- Project Leader
Lessons Learned
- None
Maturity level
- Not applicable
Basic Knowledge and Skills
Knowledge
- Software requirements definition
- Background information on Logic Programming and Software Engineering I
- Accustomed to using a particular paradigm
Abilities
- Capacity of Abstraction.
- Capacity of Analysis.
Information Resources
- 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.
