Scribd
Upload
47 views

7 B Project Scheduling Estimation and COCOMO Model

The document discusses software project scheduling, task and project planning, and estimation techniques. It provides details on scheduling software engineering tasks across a project duration, defining task sets to complete projects, and outlining project plans. Estimation techniques are used to approximate values like project size, effort, schedule, and cost when input data is uncertain. The COCOMO II model is then introduced as an evolution of the original COCOMO model for software cost estimation.

Uploaded by

zunair ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
47 views

7 B Project Scheduling Estimation and COCOMO Model

The document discusses software project scheduling, task and project planning, and estimation techniques. It provides details on scheduling software engineering tasks across a project duration, defining task sets to complete projects, and outlining project plans. Estimation techniques are used to approximate values like project size, effort, schedule, and cost when input data is uncertain. The COCOMO II model is then introduced as an evolution of the original COCOMO model for software cost estimation.

Uploaded by

zunair ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Project Scheduling, Task and Project Plan

• Software project scheduling is an activity that distributes estimated effort across the planned
project duration by allocating the effort to specific software engineering tasks.
• Task set is a collection of software engineering work tasks, milestones, and deliverables that must
be accomplished to complete a particular project. The task set to be chosen must provide enough
discipline to achieve high software quality.
• Software project plan is a relatively brief document that is addressed to a diverse audience. It
must (1) communicate scope and resources to software management, technical staff, and the
customer; (2) define risks and suggest risk avoidance techniques; (3) define cost and schedule for
management review (4) provide an overall approach to software development for all people
associated with the project and (5) outline how quality will be ensured and change will be
managed.
• Algorithmic cost modeling uses a mathematical formula to predict project costs based on
estimates of the project size, the number of software engineers, and other process and product
factors. An algorithmic cost model can be built by analyzing the costs and attributes of completed
projects and finding the closest fit formula to actual experience.
Estimation Techniques

Estimation technique is used for finding an estimate, or approximation, which is a value that can be
used for some purpose even if input data may be incomplete, uncertain, or unstable. The four basic
steps in Software Project Estimation are:
• Estimate the size of the development product.
• Estimate the effort in person-months or person-hours.
• Estimate the schedule in calendar months.
• Estimate the project cost in agreed currency.
Software Pricing:
Software pricing is setting a final cost for your end product. You must balance this number to
ensure that you see a steady flow of customers while ensuring profitability.
The COCOMO II Model

The original COCOMO (COnstructive COst MOdel) model became one of the most widely used and discussed
software cost estimation models in the industry.
It has evolved into a more comprehensive estimation model, called COCOMO II. Like its predecessor,
COCOMO II is actually a hierarchy of estimation models that address different “stages” of the software process.
Like its predecessor, COCOMO II is actually a hierarchy of estimation models that address the following areas:
Application composition model. Used during the early stages of software engineering, when prototyping of
user interfaces, consideration of software and system interaction, assessment of performance, and evaluation of
technology maturity are paramount.
Early design stage model. Used once requirements have been stabilized and basic software architecture has
been established.
Post-architecture-stage model. Used during the construction of the software. Like all estimation models for
software, the COCOMO II models require sizing information. Three different sizing options are available as part
of the model hierarchy: object points, function points, and lines of source code.
• Object point is an indirect software measure that is computed using counts of the number of (1)
screens (at the user interface), (2) reports, and (3) components likely to be required to build the
application.
• Function points are derived using an empirical relationship based on countable (direct) measures
of software's information domain and assessments of software complexity.

You might also like