Project Quality quantitative assessment suggestions

1,Demand coverage rate not covered: Calculate the unimplemented functional points divided by all functional points in the demand;

Formula: functions not implemented by sigma (items)/Total functions required by sigma (items)

Reference indicators: 0%. If none of the functional indicators can meet the requirements of 100% coverage, at least the requirement analysis is insufficient. This indicator is difficult to collect, mainly because of the definition of function points;

2,Module Rate:CodeTotal Quantity divided by the number of modules;

Formula: Σ code quantity (rows)/Σ module quantity (pieces)

Reference indicators: no reference indicators. Software design is towards modular production, and SOA architecture design is becoming increasingly popular. This indicator mainly measures the Reuse Rate of modules. The smaller the module size, the smaller the coupling of functions, the higher the reuse rate;

3,Progress Deviation: Check the progress of the planned time and the actual time by comparing the difference between the planned time and the actual time, except for the total number of actual working hours. This method is used to check the progress of the project and monitor whether the project is performed according to the schedule, whether the project progress requirements are met.

Formula: Σ (planned start time-actual start time) + Σ (planned end time-actual End Time)/total working hours

Reference indicator: 15% progress deviation is a relative indicator, which may deviate from 20 working days. However, for a project that lasts for six months, the deviation from the number of days is less than 15% compared with the overall number of days, the deviation may be 3 working days, but a test with only one week has exceeded 60% of the number of days required for the entire test phase.

4,Defect rate: Total number of defects divided by the total number of codes, multiplied by 1000, that is, the number of defects per thousand lines

Formula: Total number of Sigma defects/total number of Sigma codes * 1000

Reference indicators: 0%; the number of defects per thousand rows is a common measurement method. However, the levels, types, properties, and impacts of defects are different. It cannot be said that the number of defects per thousand rows is small, it must be of better quality than the large number of software;

5,System Efficiency: Measure the amount of physical resources required for normal software operation. For Java projects, the amount of CPU and memory used can be used as a measure;

Formula: Σ target users/Σ (CPU + 0.5 * Memory)

Reference indicator: This indicator must be measured by referring to projects in the same industry. The complexity of each project varies with the business logic, you need to obtain a type of project indicators based on experience;

6,Maintainability: Measure the effort required to adjust completed software;

Formula: Σ workload of Function Point modification/Σ total workload of project development

Reference indicator: This indicator is a hypothetical indicator. After the project is built, the project team will evaluate the workload of modifying or revising some functions.

7,Investigation Method: After the project is launched, the questionnaire form is issued, and the user evaluates the availability, reliability, and stability (functional) of the system;

Formula: None;

Reference indicators: You can consider establishing a unified Investigation Sub-system embedded in various new systems to obtain the user's final evaluation of the system, relevant quality management departments should evaluate the project to further improve the project quality;

This is a project assessment proposal I wrote last year. It seems quite meaningful now. Ah, it was once a sea of water ......