Scribd Logo
Upload

Welcome to Scribd!

  • 185 views

    COCOMO II A Parametric Productivity Model: Software Project Management (KOE-068)

    Uploaded by

    pemom29928
    COCOMO is a software cost estimation model developed by Barry Boehm. It classifies projects as organic, semidetached, or embedded based on complexity. There are basic, intermediate, and complete COCOMO models. The basic model uses lines of code and complexity type to estimate effort and schedule. The intermediate model adds cost drivers. The complete model estimates subsystems separately then sums them. COCOMO II was developed in 1994 and emphasizes quick development processes, reuse, and object orientation. It includes application composition, early design, and post-architecture models.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    COCOMO II A Parametric Productivity Model: Software Project Management (KOE-068)

    Uploaded by

    pemom29928
    185 views2 pages
    COCOMO is a software cost estimation model developed by Barry Boehm. It classifies projects as organic, semidetached, or embedded based on complexity. There are basic, intermediate, and complete COCOMO models. The basic model uses lines of code and complexity type to estimate effort and schedule. The intermediate model adds cost drivers. The complete model estimates subsystems separately then sums them. COCOMO II was developed in 1994 and emphasizes quick development processes, reuse, and object orientation. It includes application composition, early design, and post-architecture models.

    Original Title

    Software+Project+Management+Unit 2 7

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    COCOMO is a software cost estimation model developed by Barry Boehm. It classifies projects as organic, semidetached, or embedded based on complexity. There are basic, intermediate, and complete COCOMO models. The basic model uses lines of code and complexity type to estimate effort and schedule. The intermediate model adds cost drivers. The complete model estimates subsystems separately then sums them. COCOMO II was developed in 1994 and emphasizes quick development processes, reuse, and object orientation. It includes application composition, early design, and post-architecture models.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    185 views2 pages

    COCOMO II A Parametric Productivity Model: Software Project Management (KOE-068)

    Uploaded by

    pemom29928
    COCOMO is a software cost estimation model developed by Barry Boehm. It classifies projects as organic, semidetached, or embedded based on complexity. There are basic, intermediate, and complete COCOMO models. The basic model uses lines of code and complexity type to estimate effort and schedule. The intermediate model adds cost drivers. The complete model estimates subsystems separately then sums them. COCOMO II was developed in 1994 and emphasizes quick development processes, reuse, and object orientation. It includes application composition, early design, and post-architecture models.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 2

    Software Project Management (KOE-068)

    UNIT-2 (Lecture-7)

    COCOMO II a parametric productivity model

    COCOMO a parametric model


    COCOMO (Constructive Cost Estimation Model) was proposed by Boehm. According to him,
    any software development project can be classified into one of the following three categories
    based on the development complexity: organic, semidetached, and embedded.
    According to Boehm, software cost estimation should be done through three stages:
    Basic COCOMO, Intermediate COCOMO, and Complete COCOMO.

    Basic COCOMO Model


    The term COCOMO stands for Constructive Cost Model. Barry Boehm's book Software
    Engineering Economics was initially published in 1981. Due to the model's ease of transparency,
    it provides the magnitude of the project's expense. It is designed for small projects since it has a
    limited number of cost drivers. When the team size is small, i.e. when the staff is tiny, it is
    helpful.
    It's useful for getting a quick, early, rough estimate of software costs, but its accuracy is limited
    due to the lack of factors to account for differences in hardware constraints, personnel quality
    and experience, use of modern tools and techniques, and other project attributes that are known
    to have a significant impact on s/w costs.
    EFFORT = a* (KDSI)b EFFORT = a* (KDSI)
    Constants a and b have different values depending on the project type. The KLOC is the
    projected number of delivered lines of code for the project.
    The following are the three kinds of modes available in COCOMO −
    Organic Mode − A modest, basic software project involving a small group of people with
    prior application knowledge. Efforts, E, and Development, D are the following −
    o E = 2.4*(KLOC)^1.05
    o D=2.5*(E)^0.38
    Semi-detached Mode − An intermediate software project in which teams with varying
    levels of expertise collaborate.
    o E= 3.0*(KLOC)^1.12
    o D=2.5*(E)^0.35
    Embedded Mode − A software project that must be built under strict hardware, software,
    and operational limitations.
    o E= 3.6*(KLOC)^1.20
    o D= 2.5*(E)^0.32

    RAVIKANT NIRALA Page 1


    Software Project Management (KOE-068)

    COCOMO Intermediate
    It assesses software development effort as a function of program size and a set of cost drivers,
    which include a subjective assessment of goods, hardware, employees, and project
    characteristics.
    It's appropriate for medium-sized tasks. Intermediate to basic and advanced COCOMO are the
    cost drivers. Cost factors influence product dependability, database size, execution, and storage.
    The team has a modest size. The COCOMO intermediate model looks like this −
    EFFORT = a*(KLOC)b*EAF
    Here, effort is measured in person-months, and KLOC is the project's projected amount of
    delivered lines of code.
    Complete COCOMO Model
    Both the basic and intermediate COCOMO models consider a software product as a single
    homogeneous entity. However, most large systems are made up several smaller sub-systems,
    each of them in turn could be of organic type, some semidetached, or embedded. The complete
    COCOMO model takes into account these differences in characteristics of the subsystems and
    estimates the effort and development time as the sum of the estimates for the individual
    subsystems. This approach reduces the percentage of error in the final estimate.

    COCOMO-II
    COCOMO II is a research project that began in 1994 at USC. It places a strong emphasis on non-
    sequential and quick development process models, reengineering, reuse-driven methodologies,
    object-oriented approaches, and so on. It is the outcome of a combination of three models:
    application composition, early design, and post architecture.
    • On projects that employ Integrated Computer Aided Software Engineering technologies
    for fast application development, the Application Composition model is used to estimate
    effort and schedule.
    • The Early Design Model entails looking at alternative system designs and operational
    approaches.
    • The Post-Architecture Model is utilized when the apex level design is complete and
    detailed information about the project is available, and the software architecture is well-
    defined and well-known, as the name implies. It is a comprehensive expansion of the
    Early-Design paradigm, accounting for the whole development life-cycle. This is a
    COCOMO model that ranges from lean to intermediate and is defined as follows −
    EFFORT = 2.9(KLOC)^1.10

    RAVIKANT NIRALA Page 2

    You might also like