Common Quality Enumeration

This pattern identifies situations where a memory resource is explicitly allocated via the ManagesResource action to the storable or member data element, which is used throughout the application, along the sequence composed of ActionElements with DataRelations relations, some of which being part of named callable and method control elements, none of which being a memory release statement.

This pattern identifies situations where the model of the architectural layers contains too many or too few horizontal layers, based on its number of horizontal layers (that is, excluding the vertical utility layers) that is smaller than the threshold value or greater than the threshold value. The default minimal value is 4 and the default max value is 8.

This pattern identifies situations where the inheritance level of the class element is considered as too large, based on its number of parent class units which exceeds the default threshold value of 7.

This pattern identifies situations where the number of children of the class element is considered as too large, based on its number of child classes which exceeds the default threshold value of 10.

This pattern identifies situations where the named callable control element or method control element creates immutable text data elements via the string concatenation statement, which could be avoided by using text buffer data elements.

This pattern identifies situations where the named callable control element or method control element executes the data action although it is not part of the central data manager identified as one of the dedicated data access components from the data access components list. The component can be either client-side either server-side, which means that not all server-side components are allowed to handle data accesses. The data access component can be either client-side either server-side, which means that data access components can be developed using non-SQL languages. The pattern simply identifies situations where the implementation does not follow the intended design, regardless of the design.

This pattern identifies situations where the data type of the storable data element aggregates storable data elements with non-primitive data types, which is considered too large because it exceeds the threshold value, which defaults to 5.

This pattern identifies situations where the storable data element or member data element is declared as public through the Create action.

This pattern identifies situations where the named callable control element or method control element executes the data resource management action not using connection pooling capability. The usage of connection pooling capability is technology dependent. As examples, connection pooling is disabled with the addition of 'Pooling=false' to the connection string with ADO.NET and the value of 'com.sun.jndi.ldap.connect.pool' environment parameter in Java.

This pattern identifies situations where the exception handling block (such as a Catch and Finally block) of the named callable and method control elements does not contain any other control element.

Originating from software security, an "attack surface" measure typically reflects the number of input points and outpoints that can be utilized by an untrusted party, i.e. a potential attacker. In some cases, this measure may reflect other aspects of quality besides security; e.g., a product with many inputs and outputs may require a large number of tests in order to improve code coverage.

This pattern identifies situations where the named callable control element or method control element has a control flow with a Cyclomatic Complexity which is greater than the default threshold value of 20.

This pattern identifies situations where the data table is considered very large, based on its number of rows which exceeds the threshold value, and where it is accessed by the data actions which is considered to be too complex, based on its number of joins between tables which exceeds the threshold value, and its number of sub-queries which exceeds the threshold value. The default value for number of rows is 1000000. The default value for number of joins is 5. The default value for number of sub-queries is 3.

This pattern identifies situations where the syntax of the ReadsColumnSet action and the index configuration of the SQL table or SQL view causes the DBMS to run sequential searches.

A variety of Halstead complexity measures exist, such as program vocabulary size or volume.

This pattern identifies situations where the data table is considered as very large, based on its number of rows which exceeds the threshold value, and where its index is considered as too large, based on its range value which exceeds the threshold value. The default value for number of rows is 1000000 and the default value for index range is 10.

This pattern identifies situations where the server-side non-stored callable control elements in the data manager resource, embeds number of data resource access, which is considered too large because it exceeds the default threshold value of 5.

This pattern identifies situations where the data table is considered as very large, based on its number of rows which exceeds the threshold value, and is considered to have too many indices, based on its number of indices which exceeds the threshold value. The default value for number of rows is 1000000. The default value for number of indices is 3.

This pattern identifies situations where the control element, whose nature is known to cause platform resource consumption, is directly or indirectly called via the execution path, starting from within the loop body block or within the loop condition.

This pattern identifies situations where the literal value element is used to initialize the storable data element or member data element via the Write action; exceptions are simple integers and static of constant storable or member data elements.

This pattern identifies situations where the named callable control element or method control element contains too much commented-out code items, based on the percentage of instructions in the callable or method control element that are in comments which exceeds the default threshold value of 2%.

This includes environmental variables, configuration files, registry keys, command-line switches or options, or system settings.