1 / 25

Effort , Duration and Cost

Dr. M. Shamim Hossain. SWE 211. 5-2. Software Project Estimation. You can't manage something which you can't measure.We need some sort of measurement for:Size of the projectEffort and costEstimating software projects is notoriously poor.If performance doesn't meet estimates then eitherthe perf

roland
Download Presentation

Effort , Duration and Cost

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Dr. M. Shamim Hossain SWE 211 Effort , Duration and Cost Lec 3 1

    2. Dr. M. Shamim Hossain SWE 211 5-2 Software Project Estimation You can’t manage something which you can’t measure. We need some sort of measurement for: Size of the project Effort and cost Estimating software projects is notoriously poor. If performance doesn’t meet estimates then either the performance was poor; or the estimate was poor

    3. Dr. M. Shamim Hossain SWE 211 3-3 The Estimation Process: In general, the Software Cost estimation process consist of the following four main steps: Estimate the size of the development product Estimate the effort in staff-months Estimate the schedule in calendar months Estimate the project cost in dollars (or reals)

    4. Dr. M. Shamim Hossain SWE 211 5-4 Size Measurement or Complexity of Software Size matters! Direct impact on staffing, duration, and budget. Size indicators: size Lines of Code (KSLOC) Function Points estimated during the requirements analysis. It takes into account the inputs and outputs of the system Feature Points number of algorithms used in the application Object Points Number of boxes on a data flow diagram Number of classes in a design diagram

    5. Dr. M. Shamim Hossain SWE 211 5-5 Lines of Code Calculation The most commonly used size indicator. Not the best one! Prerequisite for LOC calculations: WBS Line = statement Line = data definition Line ? comments Line ? debug code Line ? test cases Different languages? Convert all to assembly Use tables: C=2.5, Fortran=3, Java=6, …

    6. Dr. M. Shamim Hossain SWE 211 5-6 Function Points Uses the functionality of the software as a measure of its complexity. Analogy: For a given house, we can say how many square meters it has (LOC) or we can say how many bedrooms and bathrooms it has (FP). A measure of the functionality of a given software.

    7. Dr. M. Shamim Hossain SWE 211 6-7 Effort and Duration Estimation Now that we have an idea about the size of the software, we can estimate the effort and duration required to complete the development. Effort: staff-months (staff-weeks, staff-days, …) Duration: months (days, years, …)

    8. Steps in Sizing and Estimating Dr. M. Shamim Hossain SWE 211 8

More Related