Scribd Logo
Upload

Welcome to Scribd!

  • 271 views

    SLIM Estimation

    Uploaded by

    ambivert
    - SLIM is an early algorithmic cost modeling methodology founded by Larry Putnam in 1978 to estimate effort for software projects exceeding 70,000 lines of code. - The SLIM model is based on the Norden-Rayleigh function and assumes effort rises smoothly during a project before sharply dropping during acceptance testing. - Key inputs to the SLIM model include project size measured in lines of code, development time, and a technology constant representing productivity factors. The model outputs the estimated total effort in staff-years required to complete the project.

    Copyright:

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

    SLIM Estimation

    Uploaded by

    ambivert
    271 views3 pages
    - SLIM is an early algorithmic cost modeling methodology founded by Larry Putnam in 1978 to estimate effort for software projects exceeding 70,000 lines of code. - The SLIM model is based on the Norden-Rayleigh function and assumes effort rises smoothly during a project before sharply dropping during acceptance testing. - Key inputs to the SLIM model include project size measured in lines of code, development time, and a technology constant representing productivity factors. The model outputs the estimated total effort in staff-years required to complete the project.

    Original Description:

    Software Development Effort Estimation

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    - SLIM is an early algorithmic cost modeling methodology founded by Larry Putnam in 1978 to estimate effort for software projects exceeding 70,000 lines of code. - The SLIM model is based on the Norden-Rayleigh function and assumes effort rises smoothly during a project before sharply dropping during acceptance testing. - Key inputs to the SLIM model include project size measured in lines of code, development time, and a technology constant representing productivity factors. The model outputs the estimated total effort in staff-years required to complete the project.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    271 views3 pages

    SLIM Estimation

    Uploaded by

    ambivert
    - SLIM is an early algorithmic cost modeling methodology founded by Larry Putnam in 1978 to estimate effort for software projects exceeding 70,000 lines of code. - The SLIM model is based on the Norden-Rayleigh function and assumes effort rises smoothly during a project before sharply dropping during acceptance testing. - Key inputs to the SLIM model include project size measured in lines of code, development time, and a technology constant representing productivity factors. The model outputs the estimated total effort in staff-years required to complete the project.

    Copyright:

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

     SLIM methodology were founded in 1978 by Larry Putnam.

     Putnam’s SLIM is one of the first algorithmic cost model.

     Putman’s SLIM model is applied to project exceeding 70,000 lines of code.


    Putman's model assumes that effort for software projects is distributed similarly
    to a collection of Rayleigh curves. Putman suggests that staffing rises smoothly
    during the project and then drops sharply during acceptance testing.

     It is based on the Norden-Rayleigh function generaly known as macro


    estimation model(it is for large projects).

     Based on Norden-Rayleigh equation D=E/t3 or E=D* t3.


     D is a constant called manpower acceleration.
     The manpower acceleration is 12.3 for new software with many interfaces and
    interaction with other systems, 15 for standalone systems, and 27 for
    reimplementation of existing systems.
     It is also based on Larry putnam’s software equation E~(Size / C)3 * t(-4) or
    Size =CE1/3(t)4/3 and known as Manpower – Buildup Equation.
     E is the total life cycle effort in working years, t is development time and the C
    is the technology constant/productivity combining the effect of using tools,
    language , methodology and quality assurance (QA) time in year.
     The value of technology constant varies from 2,000 to 12,000 For
    easy,xperienced project technology constant is high.
     Using the software and manpower – buildup equations, we can solve for effort
    E=(S/C) ^9/7(d^4/7).
     In above equation C is technology factor.
     The technology factor is a composite cost driver involving 14 components. It
    primarily reflects :-
    1. Overall process maturity and management practices.
    2. The extent to which good software engineering practices are used.
    3. The level of programming languages used.
    4. The state of the software environment.
    5. The skills and experience of the software team.
    6. The complexity of the application.
     We can calculate effort at peak time and this effort is development effort
    Development Effort=0.3935 * E
     0.3935 is constant value derived from norden reyleigh curve.
     SLIM is not widespreadly used but there is SLIM tool.
     SLIM enbles a software cost estimator to perform the following functions:
     Calibration:Fine tuning the model to represent the local software
    development enivornment by interpreting a historical database of past
    project.
     Bulid an information model of the software system,collecting software
    characteristics,personal attributes etc.
     Software sizing SLIM uses an automated version of the line of
    codes (LOC) costing technique.

    Advantages of SLIM
    I. Uses linear programming to consider development constraints on both
    cost and effort.
    II. SLIM has fewer parameters needed to generate an estimate over
    COCOMO’81 and COCOMO’II.
    III. A commercial tool is available(www.qsm.org).
    IV. The SLIM model is a good guide to estimate the requirements and
    maintenance of software.

    Drawbacks of SLIM
    I. Estimates are extremely sensitive to the technology factor.
    II. Not suitable for small projects.

    Example:
    Rating: C = 2000 -- poor, C = 8000 -- good, C = 12000 it is excellent.

    Assume C=4000

    E=(size/C)3 /t4

    Targeted Development Time t= 2years

    Size=200000 LOC

    E=(200000/4000)3/(2)4

    E=7812.5 staff/year

    Development Effort=0.3935*E
    Development Effort=0.3935*7812.5

    You might also like