Components of software estimation ppt

Show related SlideShares at end. WordPress Shortcode. Share Email. Top clipped slide. Software Estimation Techniques Apr. Technology Business. What to Upload to SlideShare. A few thoughts on work life-balance. Is vc still a thing final.

The GaryVee Content Model. Mammalian Brain Chemistry Explains Everything. Related Books Free with a 30 day trial from Scribd. Related Audiobooks Free with a 30 day trial from Scribd. Elizabeth Howell. Software Estimation Techniques 1. What is Software Estimation? Why do we need it? How to do it? The SlideShare family just got bigger. Home Explore Login Signup. Successfully reported this slideshow. We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads.

You can change your ad preferences anytime. Next SlideShares. You are reading a preview. Create your free account to continue reading. Sign Up. Upcoming SlideShare. Software Estimation Techniques. Embed Size px. Start on. Show related SlideShares at end. WordPress Shortcode. Share Email. Top clipped slide. Download Now Download Download to read offline. Software effort estimation Jan. Software estimation techniques.

Spm software effort estimation. Activity Planning in Software Project Management. Estimation and measuring of software size within the atos gobal delivery plat Dispersed and cross border projects. Related Books Free with a 30 day trial from Scribd. Dry: A Memoir Augusten Burroughs. Related Audiobooks Free with a 30 day trial from Scribd. Software effort estimation 1. Delivering: agreed functionality on time at the agreed cost with the required quality Stages: 1.

Attempt to achieve targets BUT what if the targets are not achievable? Break project into smaller and smaller components [2. Estimate costs for the lowest level activities 4. At each higher level calculate estimate by adding estimates for lower levels 7. Thousands of lines of code This talk provides an overview of the basic steps needed to produce a project plan. Development Environment Resources. Reusable Software Resources. Estimation of Project Cost and Effort.

Factors Affecting Project Estimation. Project Estimation Options. Project Estimation Approaches. Decomposition Techniques. Approaches to Software Sizing. The results of these estimates are used to compute an optimistic low , a most likely,. Problem -Based Estimation. Problem -Based Estimation continued. Process -Based Estimation.

Process -Based Estimation continued. This is the most commonly used of the two estimation techniques problem and process. Reconciling Estimates. Empirical Estimation Models. Project planning Scope and feasibility Project resources Estimation of project cost and effort Decomposition techniques Empirical estimation models.

Software project planning encompasses five major activities Estimation, scheduling, risk analysis, quality management planning, and change management planning Estimation determines how much money, effort, resources, and time it will take to build a specific system or product The software team first estimates The work to be done The resources required The time that will elapse from start to finish Then they establish a project schedule that Defines tasks and milestones Identifies who is responsible for conducting each task Specifies the inter-task dependencies.

Planning requires technical managers and the software team to make an initial commitment Process and project metrics can provide a historical perspective and valuable input for generation of quantitative estimates Past experience can aid greatly Estimation carries inherent risk , and this risk leads to uncertainty The availability of historical information has a strong influence on estimation risk.

When software metrics are available from past projects Estimates can be made with greater assurance Schedules can be established to avoid past difficulties Overall risk is reduced Estimation risk is measured by the degree of uncertainty in the quantitative estimates for cost, schedule, and resources Nevertheless, a project manager should not become obsessive about estimation Plans should be iterative and allow adjustments as time passes and more is made certain. Establish project scope Determine feasibility Analyze risks Define required resources Determine human resources required Define reusable software resources Identify environmental resources Estimate cost and effort Decompose the problem Develop two or more estimates using different approaches Reconcile the estimates Develop a project schedule Establish a meaningful task set Define a task network Use scheduling tools to develop a timeline chart Define schedule tracking mechanisms.

After the scope has been identified, two questions are asked Can we build software to meet this scope?