Prepare for your exams
Get points
Guidelines and tips
Sell on Docsity
Docsity AI

Prepare for your exams

Study with the several resources on Docsity

Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips

Sell on Docsity

Docsity AI

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents

20 Points

For each uploaded document

Answer questions

5 Points

For each given answer (max 1 per day)

All the ways to get free points

Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Introduction to Software Engineering: Project Planning, Estimation, and Management, Study Guides, Projects, Research of Software Engineering

West Virginia University (WVU)Software Engineering

An overview of software project planning, estimation, and management. Topics include fundamentals of project planning and estimating, metrics for software productivity assessment, different estimation techniques, and the use of the cocomo algorithmic cost estimation method. The document also covers project scheduling and tracking, and provides a framework for a software project management plan (spmp).

Typology: Study Guides, Projects, Research

Pre 2010

Uploaded on 07/30/2009

koofers-user-zlg 🇺🇸

4.5

(2)

9 documents

1 / 50

This page cannot be seen from the preview

Don't miss anything!

SOFTWARE PROJECT

PLANNING

Discover Study Guides, Projects, Research of Software Engineering West Virginia University (WVU)

Partial preview of the text

Download Introduction to Software Engineering: Project Planning, Estimation, and Management and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity!

SOFTWARE PROJECT

PLANNING

Overview

Fundamentals of project planning and estimating - Metrics for software productivity assessment - Different techniques that can be used for estimation - Algorithmic cost estimation method - COCOMO - Project scheduling and tracking - Framework for Software Project Management Plan(SPMP)

Planning and estimating

Ideally, we would like to plan the entire softwareproject at the very beginning of the process - The earliest possible detailed planning is after thespecification phase - Accuracy of estimation increases as the processproceeds - Accurate duration estimation is critical - Accurate cost estimation is critical - Internal cost • External cost - There are too many variables for accurate estimate ofcost or duration

Software pricing factors Factor

Description Market opportunity A development organisation may quote a low price because it wishes to move into a new segment of thesoftware market. Accepting a low profit on one project may give the opportunity of more profit later.The experience gained may allow new products to bedeveloped. Cost estimate uncertainty If an organisation is unsure of its cost estimate, itmay increase its price by some contingency over andabove its normal profit. Contractual terms A customer may be willing to allow the developer toretain ownership of the source code and reuse it in other projects. The price charged may then be less than if the software source code is handed over to thecustomer. Requirements volatility If the requirements are likely to change, an organisation may lower its price to win a contract.After the contract is awarded, high prices may becharged for changes to the requirements. Financial health Developers in financial difficulty may lower their price to gain a contract. It is better to make a small profit or break even than to go out of business. There is not a simple relationship between the development cost and the price charged to the customer

Programmer productivity

A measure of the rate at which individual engineersinvolved in software development produce softwareand associated documentation - Not quality-oriented although quality assurance is a factor in productivity assessment - Essentially, we want to measure useful functionalityproduced per time unit

Productivity measures

Size related measures based on some output fromthe software process. This may be lines of deliveredsource code, object code instructions, etc. - Function-related measures based on an estimate ofthe functionality of the delivered software. Function-points are the best known of this type of measure

Function points (FP)

Based on a combination of program characteristics - external inputs and outputs • user interactions • external interfaces • files used by the system - A weight is associated with each of these - The function point count is computed by multiplyingeach raw count by the weight and summing allvalues

Function points (contd)

For example FP = 4

×

Inp + 5

×

Out + 4

×

Inq + 10

×

Maf + 7

×

Inf

Inp

number of inputs
Out
- number of outputs
  Inq
  - inquiries
    Maf
    - master files
      Inf
      - interfaces
        FPs may be subjective

Object point estimation

Object points are easier to estimate from aspecification than function points as they are simplyconcerned with screens, reports and 3GL modules - They can therefore be estimated at an early point inthe development process. At this stage, it is verydifficult to estimate the number of lines of code in asystem - Object points are used in the COCOMO II estimationmodel

Productivity estimates

Real-time embedded systems, 40-160 LOC/month - Systems programs, 150-400 LOC/month - Commercial applications, 200-800 LOC/month - In object points, productivity has been measuredbetween 4 and 50 object points/month depending ontool support and developer capability

Overview

Estimation techniques

Expert judgement - Estimation by analogy - Pricing to win - Algorithmic cost modelling

Estimation by analogy

The cost of a project is computed by comparing theproject to a similar project in the same applicationdomain - Advantages - Accurate if project data available - Disadvantages - Impossible if no comparable project has been tackled • Needs systematically maintained cost database

Pricing to win

The project costs whatever the customer has tospend on it - This approach may seem unethical and un-businesslike. However, when detailed informationis lacking it may be the only appropriate strategy - Advantages - You get the contract - Disadvantages - The probability that the customer gets the system he or she wants is small - Costs do not accurately reflect the work required

Introduction to Software Engineering: Project Planning, Estimation, and Management, Study Guides, Projects, Research of Software Engineering

Related documents

Partial preview of the text

Download Introduction to Software Engineering: Project Planning, Estimation, and Management and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity!

SOFTWARE PROJECT

PLANNING

Overview

Planning and estimating

Software pricing factors Factor

Programmer productivity

Productivity measures

Function points (FP)

Function points (contd)

×

×

×

×

×

number of inputs

number of outputs

inquiries

master files

interfaces

Object point estimation

Productivity estimates

Overview

Estimation techniques

Estimation by analogy

Pricing to win