Diferencia entre revisiones de «Cocomo81»

De productpatterns_wiki
Saltar a: navegación, buscar
(Página creada con «__NOTOC__ {{#seo: |title=Cocomo 81 |keywords=Cocomo, estimación, gestión, esfuerzo, tiempo, coste }} <p style="text-align: right;"><span style="font-size: x-small;">Ar...»)
m (Protegió «Cocomo81» ([Editar=Solo permitir usuarios autoconfirmados] (indefinido) [Pueden trasladar=Solo permitir usuarios autoconfirmados] (indefinido)))
(Sin diferencias)

Revisión de 23:39 11 feb 2015

Spanish.jpg Español


  • Document requirements specification or description of problem
  • Size software to perform (lines of code)
  • Albrecht Function Point


  • Direct measures:
    • Team development Effort
    • Project duration
  • Indirect measures:
    • Productivity
    • Quality
    • Cost
    • Documentation
    • Code lines



Diagrama Cocomo 81.PNG

Development time

    • To acquire the necessary software to develop product knowledge: 4 hours.
    • To create the pattern of Product: 2 days.
    • To apply the pattern of Product: 2 hours.

Explanation video

    • Not applicable.

Quality Controllers

  • None

Support Tools

Initial Context

This product can be used on any type of project during the phases of Planning and Requirements Definition, Product Design, Detailed Design, Coding and Unit Testing, Integration and Testing, Implementation, Operation and Maintenance. Is used for estimating software costs.

Resulting context

The project manager will get a prediction of personnel, the efforts of the development team, costs and project duration to perform all activities and build all products associated with a project.


The project manager wants to create a document detailing precisely the estimation of the project being developed. Personnel involved in this task must be able to identify what type of project is about and what is the environment or restrictions in which it is performed. It will also be able to identify and give value to product attributes, computer, personal, and the project in general.

Restrictions (Forces)

  • Characteristics of organizations: This pattern can be used in existing projects in any company.
  • Type of system to be developed: This product can be used in projects in which user requirements are changing.
  • Type of customer: It must exist or be achieved, the target business area of development gets involved in the achievement.
  • Heuristics for use: If is needed a urgent application or dispose of some of its functionality.


  • Project Leader

Lessons Learned

  • To avoid errors when estimating must always be considered first the estimation model and then the development mode is selected.
  • The effort is the first thing that must be calculated and is measured in PM (person months).

Maturity level

    • Not applicable.

Basic Knowledge and Skills


  • Definition of software requirements
  • Background information on Logic Programming and Software Engineering I
  • Knowledge in Databases Design
  • Getting used to using a particular paradigm


  • Capacity of abstraction.
  • Capacity of Analysis.

Information Resources

  • Barry w. Boehm. Software Engineering Economics. http://www.amazon.com/Software-Engineering-Economics-Barry-Boehm/dp/0138221227#reader_0138221227
  • 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.