Software measurement lecture 7
Upcoming SlideShare
Loading in...5
×
 

Software measurement lecture 7

on

  • 137 views

 

Statistics

Views

Total Views
137
Views on SlideShare
137
Embed Views
0

Actions

Likes
0
Downloads
4
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Software measurement lecture 7 Software measurement lecture 7 Presentation Transcript

  • Software Measurement By Mr. Fazal Wahab
  • Why Measure?  If we want to make reasonable decisions about projects, we have to measure some sort of data on which to base those decisions.  However, making such measurements is extremely time consuming, which is expensive. It is also extremely difficult (impossible?) to get unambiguous data.  Thus it is crucial to decide what to measure about your projects, and what you will do with that information.
  • Identifying Issues  How do you figure out what to measure? Some are obviously things that you must measure to have any idea what you are doing: – Project constraints (e.g. you need to know if you are going over budget) – External requirements/Product acceptance criteria (you need to demonstrate that requirements are met)  Others are based on analysis of what risks you face in this project, what has gone wrong in previous projects, etc.
  • Issues That Can Be Measured 1. Schedule : Can we expect it to be done on time? 2. Cost : Can we afford to finish this project, or will it end up costing more than it is worth? 3. Size : How big is the product so far? Is the scope stable? 4. Quality : Is the product being made well, with few bugs? 5. Ability : How much design/coding/debugging/etc. can this team do per month? 6. Performance : Is the program fast enough, using reasonable resources?  Most of these interact strongly with the others.
  • Issues 1. Schedule
  • Issues 2. Cost
  • Issues 3. Size
  • Issues 4. Quality
  • Issues 5. Ability
  • Issues 6. Performance