Activity Information Select Static Analysis Rules and Guidelines
DescriptionA static analysis tool is used to evaluate the quality of the code prior to integration. Rules and guidelines for the tool are selected to establish the level of code quality expected. The rules govern what the tool looks for, and the guidelines dictate what is done when a rule is broken. Attributes| Element Categories | [CMMI Track 2] Planning, [CMMI Level 5] CAR SP 2.1, [CMMI Level 3] VER SP 2.3 | | When | Prior to coding, once per project. | | Entry Criteria | Product Vision Statement Complete:
The product vision statement is complete.
Quality of Service Requirements Complete:
The quality of service requirements are complete.
Organization Coding Guidelines Established:
The organization has established coding guidelines for languages used in production.
Peer Review Data Available:
Peer review data is available.
Root Cause Analysis Available:
Any root cause analysis is available. | | Exit Criteria | Static Analysis Rules Selected:
The static analysis rules are selected.
Static Analysis Guidelines Selected:
The static analysis guidelines are selected. | | Is Required | Yes |
StepsAnalyze Inputs:
Analyze the product vision statement and quality of service requirements for quality policy or requirements that pertain to code quality. Select Static Analysis Rules:
Select static analysis rules to establish the appropriate level of code quality for the project. Update the tool to reflect the selections. Select Static Analysis Guidelines:
Select static analysis guidelines to dictate what the tool will do when a rule is broken. For example, if a rule is broken, guidelines could be set up to automatically fix the problem, prompt the user if the tool should fix the problem, add the instance to a problem report, etc. Update the tool to reflect the selections. Review Static Analysis Rules and Guidelines:
Review, revise, and approve the static analysis rules and guidelines.
|
Last modified at 12/19/2007 10:37 AM by Administrator
|
|