04-08-2012, 02:30 PM
POINT ACCUMULATION TRACKING SYSTEM
OVERVIEW OF POINT ACCUMULATION TRACKING SYSTEM.pptx (Size: 120.25 KB / Downloads: 64)
Typical Methods Of Measuring Performance:
Two methods in measuring the performance in software development
METHOD 1: By estimating the percentage of a task completed.
METHOD 2: By counting the number of predetermined milestones that have been reached.
Disadvantage of method 1:
Major fault: The measurement is Subjective.
Since the estimates are subjective ,the interpretation of the results may also be subjective.
Using the POINT system:
The point system is really an extension to the milestone system that lends itself to automation.
In its simplest form, it is assumed that each software module goes through a similar development process and that the process comprises clearly identifiable milestones.
SECOND EXTENSION:
is to add selecting and sorting options to the programs that generate the reports. Selecting options allows the user to select all entries in the file by some field, such as work package number, file name, software family tree component, or responsible analyst.
Once the entries of interest are selected, the sort option allows the user to order the entries by some key. The points earned and points defined are summed from the selected entries and the percent complete calculated.
Therefore, reports can be printed listing all modules and percent complete for a certain analyst, work package, or other selected criteria.
Rolling Baseline:
A potential problem with the point system described thus far has to do with an effect
known as a rolling baseline.
The rolling baseline occurs over the life of a program as new items are continually defined and added to the status file.
This has the effect of changing the baseline, which causes percent complete to vary independently of milestones earned.