Cocomo81

De productpatterns_wiki
Saltar a: navegación, buscar

Spanish.jpg Español

Box-In.png
Entries

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

Box-Out.png
Exit

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

Star.png
Solution

process-descending-24px.png
Process

Cocomo81ingles.png

time-24px.png
Development time

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

video-24px.png
Explanation video

    • Not applicable.

Search-32px.png
Quality Controllers

  • None

tool.png
Support Tools

start-flag.png
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.

end-flag.png
Result 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.

cloud.png
Problem

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.

forces.png
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.

roles.png
Roles

  • Project Leader

lightbulb.png
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).

award.png
Capability Level

    • Not applicable.

Options.png
Basic Knowledge and Skills

board-24px.png
Knowledge

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

help-24px.png
Abilities

  • Capacity of Abstraction.
  • Capacity of Analysis.

Information-Sources.png
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.