Software measurement lecture 7

Software measurement lecture 7

• 1.
  Software Measurement By Mr.Fazal Wahab
• 2.
  Why Measure?  Ifwe 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.
• 3.
  Identifying Issues  Howdo 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.
• 4.
  Issues That CanBe 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.
• 5.
  Issues 1. Schedule
• 6.
  Issues 2. Cost
• 7.
  Issues 3. Size
• 8.
  Issues 4. Quality
• 9.
  Issues 5. Ability
• 10.
  Issues 6. Performance