Process and Project Metrics:-

Metrics should be collected so that process and product indicators can be ascertained.

• Process metrics used to provide indictors that lead to long term process improvement.

• Project metrics enable project manager.

o Assess status of ongoing project

o Track potential risks

o Uncover problem are before they go critical

o Adjust work flow or tasks

o Evaluate the project team’s ability to control quality of software work products.

Process Metrics:-

• Private process metrics (e.g. defect rates by individual or module) are only known to by the individual or team concerned.

• Public process metrics enable organizations to make strategic changes to improve the software process.

• Metrics should not be used to evaluate the performance of individuals.

• Statistical software process improvement helps and organization to discover where they are strong and where are week.

Project Metrics:-

• A software team can use software project metrics to adapt project workflow and technical activities.

• Project metrics are used to avoid development schedule delays, to mitigate potential risks, and to assess product
quality on an on-going basis.

• Every project should measure its inputs (resources), outputs (deliverables), and results (effectiveness of
deliverables).

Software Measurement

• Direct process measures include cost and effort.

• Direct process measures include lines of code (LOC), execution speed, memory size, defects reported over some time period.

• Indirect product measures examine the quality of the software product itself (e.g. functionality, complexity, efficiency, reliability, maintainability).

Size-Oriented Metrics:-

• Derived by normalizing (dividing) any direct measure (e.g. defects or human effort) associated with the product or
project by LOC.

• Size oriented metrics are widely used but their validity and applicability is widely debated.

Function-Oriented Metrics:-

• Function points are computed from direct measures of the information domain of a business software application and assessment of its complexity.

• Once computed function points are used like LOC to normalize measures for software productivity, quality, and other attributes.

• The relationship of LOC and function points depends on the language used to implement the software.

Object-Oriented Metrics:-

• Number of scenario scripts (NSS)

• Number of key classes (NKC)

• Number of support classes (e.g. UI classes, database access classes, computations classes, etc.)

• Average number of support classes per key class

• Number of subsystems (NSUB)

Use Case-Oriented Metrics:-

• Describe (indirectly) user-visible functions and features in language independent manner.

• Number of use case is directly proportional to LOC size of application and number of test cases needed.

• However use cases do not come in standard sizes and use as a normalization measure is suspect.

• Use case points have been suggested as a mechanism for estimating effort.