9 software metric rules for the sm Process

The following nine Software metric guidelines for the sm (Practical Software and Systems Measurement) process:

1) Project issues and objectives drive the measurement requirements

2) The developer's process defines how the software is actually measured.

3) Collect and analyze data at a level of detail sufficient to identify and isolate software problems.

4) Implement an independent analysis capability.

5) Use a structured analysis process to trace the measures to the decisions.

6) Interpret the measurement results in the context of other project information.

7) Integrate software measurement into project management throughout the software life cycle.

8) Focus initially on single project analysis.

9) Use the measurement process as a basis for objective communications.

1) project problems and target-driven measurement requirements

2) the development process defines how the software is actually measured

3) Collect and analyze sufficient data to some extent to identify and isolate software problems

(Man-month myth help modify Translation: The detailed level of data collection and analysis should be sufficient to identify and isolate software problems)

4) independent analysis capability

5) Use structured process tracking for decision Measurement

6) Explain the measurement results based on the project context information.

7) integrate software measurement into project management during the software life cycle

8) initially focused on a single project analysis

9) use the measurement process as the basis for target communication