SOFTWARE METRICS 
VietSoftware International collects and analyzes software metrics in three domains: product, process and project. Through collecting objective information, VietSoftware International can understand the status of its projects and improve for the future. We strongly believe that metrics help improve software quality, performance, features and time-to-market.
Our measurements enable us to better manage our projects and timelines. In our evaluations, VietSoftware International analyzes and manages a project’s quality, feature set and timeline. Based on our past experience and data, these metrics assist us to accurately forecast future projects’ requirements and schedules.
The key metrics used by VietSoftware International are:
- Product Size
- Size Deviation
- Effort Deviation
- Requirements Completeness
- Requirements Stability
- Defect Rate and leakage
- Quality Cost
- Customer Satisfaction
- Test Efficiency
Metric: Product size
Objective: To provide tracking over the size of software products against estimated. This metric is also the base for other metrics, for example productivity, or quality of the product.
Person in charge: Project manager
Frequency: Measure product size when project/milestone/iteration is started, SRS is completed, and at the end of the project/milestone/iteration
Return to top
Metric: Size deviation
Objective: To provide information about how well the estimation is performed.
Person in charge: Project manager
Frequency: At the end of the project/milestones/iteration
Return to top
Metric: Effort deviation
Objective: To measure the project planning and managing capability.
Person in charge: Project manager
Frequency: When the project/iteration is completed
Return to top
Metric: Requirements completeness
Objective: To measure the completeness of requirements and how far to reach the destination.
Person in charge: Project manager
Frequency: Weekly, at the end of iterations, milestones and project
Return to top
Metric: Requirements stability
Objective: Provides the visibility into whether requirement changes are responsible for cost overruns, schedule delays, and decreased product quality.
Person in charge: Project manager
Frequency: At the end of iterations, milestones, and project
Return to top
Metric: Defect rate and leakage
Objective: Provides the trend and the measurement of product quality.
Person in charge: Test leader is responsible for collecting and calculating the number of defects defected by test. Project manager is responsible for calculating defect rate and leakage.
Frequency: Depend on project; number of defects and defect rate are calculated daily, or weekly. Defect rate and leakage will be calculated when the iteration/milestone/project is completed.
Return to top
Metric: Quality cost
Objective: To provide the cost that project pays for quality
Person in charge: Project manager
Frequency: At the end of project or each half year for maintenance projects
Return to top
Metric: Customer satisfaction
Objective: To provide customer satisfaction and to measure the success of project
Person in charge: QA
Frequency: At the end of the project, when the acceptance test is completed or customer accepts the products.
Return to top
Metric: Test efficiency
Objective: To provide the efficiency of test activities
Person in charge: Project manager
Frequency: When the iteration/milestone/project is completed
Return to top
|
