Sofware Estimation includes Size,Effort,Schedule and Cost.

Software-Testing-Checklist
Software-Checklist

Sofware Estimation includes Size,Effort,Schedule and Cost.

Welcome to CodeSpread!

Estimation is a per-development  activity which bows the first seed and proves to be a real foundation of a successful project delivery. It initiates the the beginning of project planning activities.

Wikipedia says ‘Estimation is the process of finding an estimate, or approximation, which is a value that is usable for some purpose even if input data may be incomplete, uncertain, or unstable.

We can say that its a raw predictive technique established to ease out the processes followed after it. These options may include

  • Estimate the size
  • Estimate the effort
  • Estimate the schedule
  • Estimate the project cost

Estimate the size:

Though it is difficult to measure size in advance, but we may use conditions like best case and worst case scenario to reach an acceptable level of agreement.

There are activities like approximate man-hours, budget/cost, duration, etc. of the project are dependent on the size. For example:

Sizing will help

  • To allocate budget
  • To get the Manpower requirement
  • To get the hardware resource requirement
  • To quote the price for the project
  • To compare the other project
  • To Select the best & valuable project.

ref: http://pm.stackexchange.com/questions/5811/is-it-important-to-estimate-the-product-size-for-software-project

Approaches to Estimating size:

Wideband-Delphi
Fuzzy logic
Component estimating
Function points

Estimate the effort:

Now we have estimated the size and if we know the project team/programmer productivity then we can provide an estimate of efforts.

For example: Effort estimation= estimated size × productivity

Estimate the schedule:

We know the productivity, efforts /man-hours required to accomplish the tasks in hand. We have to come up with a schedule to allocate resources as per the task and also attach a timeline with each one of it. All this can be estimated if we have all the prior information in hand.

We can use past experience or popular scheduling methods like COCOMO II. As we follow SDLC so we just have to organize total duration given time into the lifecycle-phases.

For example: Work Breakdown Structure (WBS)

Estimate the project cost:

The cost of developing the software is deduced by multiplying the estimated effort to rate per hour for each resources.

For example: Cost estimation= estimated effort × rate per hour × no. of resources + overheads.

Conclusion:

Through the sizing and costing methods discussed above,A fairly acceptable estimation could be achieved but as they, “No size estimation method is foolproof or particularly accurate”.

Author: hershey

A passion for knowledge drives me to do programming, A passion for programming drives me to create something different, A passion for creation drives me to spread the knowledge.

Share This Post On

0 Comments

  1. nice superb explaination

    Post a Reply
  2. thanks for the tutorial
    I am having a problem.
    The feature “Create SQL server database” isn’t available , I can’t select it.
    Can you help, please ?

    Post a Reply

Submit a Comment

Your email address will not be published. Required fields are marked *

More from CodeSpread:

  • Agile Encounters UnpredictabilityAgile Encounters UnpredictabilityWhat is Agile? Wikipedia says “Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through...
  • Software Testing Life Cycle (STLC)Software Testing Life Cycle (STLC)Software Testing Life Cycle (STLC) is a process which consists of a number of phases to improve the quality of the product. Each phase involves various testing activities like Requirement An...
  • Functional and Non-Functional RequirementsFunctional and Non-Functional RequirementsBefore we begin a project, we are always required to document the requirements and classify them between functional requirements and non-functional requirements. This activity is beneficial wheneve...
  • NetBiscuits: How fascinating can it be to create a mobile website?NetBiscuits: How fascinating can it be to create a mobile website?My very first impression was like why do I need it, who wants to see a site on a mobile? How would a website be able to fit into my mobile without destroying the look and feel of a desktop site? ...
  • SQL:My first SSIS PackageSQL:My first SSIS PackageI would like to share my experience about a situation, where I was given a task to export a file(say XML) from FTP location and get the data from this file populated into our database tables. Moreo...
  • Risk Management in IT: Another step for QualityRisk Management in IT: Another step for QualityWhat is Risk? Risk is an uncertainty. Here, this pertains to a situation where It is difficult to decide that whether a particular event will occur or not. But if it occurs then what impact it wil...
  • SDLC: Importance of Requirement Analysis.SDLC: Importance of Requirement Analysis.What is SDLC? SDLC is the acronym for Software Development Life Cycle or System Development Life Cycle.It is a conceptual model that describes the stages involved in development of a software or a...
  • Decision Analysis and Resolution (DAR)Decision Analysis and Resolution (DAR)We divide the terms to understand them better. Decision Analysis is related to analyze possible decisions. So we need a process to perform decision analysis. Resolution is related to a propos...