User talk:Nikita knysh

Welcome!
Hello Nikita knysh, welcome to Wikipedia! Thank you for your contributions. I hope you like the place and decide to stay. Our intro page contains a lot of helpful material for new users—please check it out! If you need help, visit Questions, ask me on my talk page, or place   on this page, followed by your question, and someone will show up shortly to answer your questions. – Mato (talk)

Attribute Component Capability (ACC).
A method of assessing distribution of testing needs in software testing. Proposed and promoted by James A. Whittaker, Test Director at Google.

Concept
Break down the product attributes, components and capabilities. Give quantitative assessment of each capability with three numbers: complexity, frequency of use, user impact. Calculate testing needs.

Product Breakdown

 * Attribute. "Back of the box" quality of the product. Thing executives and Product Owners brag about. Examples: Functional, Efficient, Configurable, User-centric, Reliable, Compatible, Secure
 * Component. Functionality areas and / or architecture element within the product; things developers brag about.
 * Capability. A single task the software performs on user request or a supporting / infrastructure task. A capability adds value to an attribute of the system and is implemented in a component of a system. Name of capability always starts with a verb. A pair of attribute and component may have any number of capabilities.

Quantitative Assessment
For each capability, the following factors should be assessed:
 * Complexity. Indicates risk of human mistakes during code development and maintenance and therefore risk of introducing bugs.
 * Frequency of use. Shows how often the capability is called by user or automatically and therefore how often failures caused by defects in code will most likely occur.
 * User impact. Evaluates the damage dealt to user and / or system intent should the capability fail completely or severely.

Recommendations
It is recommended to use a scale of 1 to 5. Use full scale. Track average values for each quantitative factors throughout the ACC model. The closes the average to 3 - the better your assessment marks are distributed.

Complexity Factors
The following factors should be considered during quantitative assessment of complexity of a capability:
 * Logical complexity: conditions, loops, number of paths in code and/or work flow
 * How much user interface?
 * How much error handling?
 * How easy to debug?
 * Level of detail of requirements
 * Level of team expertise in technology
 * Unit test coverage
 * Auto test coverage
 * Code ownership (Who has written the code? Is author of code available?)