Project management MCQ

Which of the following is not an option to achieve reliable cost and effort estimate?

To achieve reliable cost and effort estimates, a number of options arise:1.Delay estimation until late in the project [since, we can achieve 100%accurate estimates after the project is complete!]2.Base estimates on similar projects that have already been completed.3.Use relatively simple decomposition techniques to generate project costand effort estimates.4. Use one or more empirical models for software cost and effortestimation.Unfortunately, the first option, however attractive, is not practical. Cost estimatesmust be provided “Up front”. However, we should recognize that the longer wewait, the more we know, and the more we know, the less likely we are to makeserious errors in our estimates.The second option can work reasonably well, if the current project is quitesimilar to past efforts and other project influences [e.g., the customer, businessconditions, the SEE, deadlines] are equivalent. Unfortunately past experience hasnot always been a good indicator of future results.The remaining options are viable approaches the software project estimation.Ideally, the techniques noted for each option be applied in tandem; each used ascross check for the other.Decomposition techniquestake a “divide and conquer”approach to software project estimation. By decomposing a project into majorfunctions and related software engineering activities, cost and effort estimation canbe performed in the stepwise fashion.Empirical estimationmodels can be used to complement decompositiontechniques and offer a potentially valuable estimation approach in their own right. Amodel based on experience [historical data] and takes the form

We have textbook solutions for you!

The document you are viewing contains questions related to this textbook.

Chemistry: The Molecular Science

Moore/Stanitski

Expert Verified

D = f [vi]Where d is one of a number of estimated values [e.g., effort, cost, projectduration and we are selected independent parameters [e.g., estimated LOC [line ofcode]].Each of the viable softwarecost estimationoptions is only as good as thehistorical data used to seed the estimate. If no historical data exist, costing rests on avery shaky foundation.

Chapter 4Project Monitoring System

4.1 PERT ChartProgram evaluation and review technique [PERT] and critical path method[CPM] are two project scheduling methods that can be applied to softwaredevelopment. These techniques are driven by following information:Estimates of EffortA decomposition of the product functionThe selection of the appropriate process model and task setDecomposition of tasksPERT chart for this application software is illustrated in figure 3.1. The criticalPath for this Project is Design, Code generation and Integration and testing.Aug-2008Figure 4.1 PERTcharts for “University Study CenterManagement SystemManagement System”.4.2 Gantt ChartGantt chart which is also known as Timeline chart contains the informationlike effort, duration, start date, completion date for each task. A timeline chart canbe developed for the entire project.