What is Code Complexity? Why it Matters and How to Measure it?

In software development, code complexity plays a pivotal role in determining the quality, maintainability, and scalability of a program. It is important to understand the concept of code complexity and its impact on software projects. In this blog post, we will learn about code complexity, why it matters and how to measure it.

Let's get started.

What is Code Complexity?

Code complexity refers to the level of difficulty in understanding and maintaining a piece of software code. It measures how much effort is required to comprehend the code, make modifications or fix bugs. Code complexity is affected by various factors, such as the number of lines of code, the number of conditional statements, the number of loops, the number of nested structures, the number of methods/functions, the amount of data being processed, and the level of abstraction used in the code.

Code complexity is a measure of how complex a piece of code is. The factors that influence the nature of code and its complexity are plenty. Here are two pieces of code to help demonstrate code complexity:

Examples of Code Complexity:

1. Example (a):

def bar():
    x = 1
    if x == 2:
        print("Success")    

2. Example (b):

def foo():
    evens = [2, 4, 6, 8, 10]
    odds = [1, 3, 5, 7, 9]
    for x in evens:
        for y in odds:
            product = x * y
            If product % 2 == 0:
                print “Product result is even”
            If product % 5 == 0:
	        print “Product is divisible by 5”
            If product % 3 == 0:
                print “Product is divisible by 3”

Example (a) has a much simpler logic when compared to (b).

Quantifying the complexity of example (b) would have to take into account the number of iterations and the number of decisions to be made in each iteration. This means, even though (b) has only one decision statement, its complexity will be exponentially higher given its position under two loops.

Code complexity can be measured in a few different ways and hence it is to be taken into consideration with broader observations and personal experience. It is also important to understand the business critical reasons for measuring code complexity and the reasons behind higher values of the metric.

Why is Code Complexity Important?

Code complexity matters for several reasons. Let us explore some of them.

1. Reading and code maintenance

High code complexity could imply that the code is harder to read and its functionality is harder to understand even with proper documentation in place. This has significant repercussions for engineers and managers - Readable code helps avoid repetition of similar methods thus encouraging code reusability. It is less prone to errors as it is easy to discern, and is faster to improve or fix any bugs.

Additionally, complex code that’s harder to read can directly impact the review times resulting in an increase in the overall cycle time. These issues therefore make it a matter of business concern to observe and optimize code complexity.

Finally, complex code means it's harder for engineers to maintain in the long run. It demands more of the engineers’ time working on the system resulting in productive hours wasted on maintenance which could have been better used for other tasks.

2. Testing

All systems need to be tested thoroughly to help identify and fix issues before the customers get their hands on the product. Complex code tend to prolong the testing process by passing on the complexity of code over to the entire testing process, as it can:

1. Increase the number of test cases - in white box methods like “basis path testing” or “structured testing”, the number of test cases will be equal to the linearly independent paths of the method.
2. Significantly heighten the chances of missing test cases given its hard to understand nature and because the number of test cases might be high
3. Prolong the time taken by the test cases due to the nature of the complex module

Testing is considered the final seal of approval in many teams, making code complexity and its repercussions like missed test cases costly to businesses.

3. Time

Another direct effect of having systems with complex code is it can directly impact the compilation times of software which means an increase in compute resources being consumed, and a waste of productive hours for engineers.

How Does the Complexity of Code Increase?

There are a few key actions that tend to have an impact on the complexity of a code base. Lack of documentation, architectural decisions, human nature, resource allocation, and evolving project requirements generally result in increased complexity and hence it is best to first understand how these make their impact on complexity.

1. Lack of Documentation

Documentation in code carries tremendous importance. It is with documentation within code that engineers can work together to build a product - it helps engineers to not step on each others toes, not repeat or do additional work and helps put down the thought process behind the method or the next n lines of code which can give insight to others while debugging, adding new features or while tackling a problem of similar nature.

When this all-important documentation is lacking, or in extreme cases, missing, it is natural that engineers end up doing some, or all of those tasks documentation was supposed to prevent - adding to the complexity.

2. Architectural Decisions

Architectural decisions dictate the way the software is written, how it will be improved, how it can be tested against and so on. These decisions tend to be made at the beginning of the project or at key moments when large changes are required. This means that these decisions have enormous potential to influence how complex the system and the modules in it will turn out to be.

3. Over-optimization

Over-engineering is common. It's the process by which engineers tend to over optimize the code even when it's not warranted. Such over-optimizations lead to hard-to-read code and low reusability, both of which end up adding to the complexity of code. This is an excellent reason why clear and detailed guidelines should be added to every project and checked with every pull request.

4. Poor Resource Allocation

A common reason why code complexity can increase is improper allocation of tasks. When engineers that lack the specialization of a particular skill set are assigned tasks that require extensive experience, the complexity of code is bound to increase. Not using language-specific constructs, paradigms or patterns due to lack of experience with the language or a particular programming framework or technology is a commonly overlooked cause that impacts code complexity considerably.

5. Evolving Project

One of the earmarks of an evolving project, other than code churn, is the increase in its complexity. When a code base is worked upon constantly, to fix bugs, to add features, to extend, each edit has the potential to increase the complexity of not just the system but the existing code. These can quickly compound, leading to higher complexity scores.

How to Measure Code Complexity?

Code complexity is important to measure because it directly affects software quality and maintainability. Complex code is harder to understand, modify, and debug. Developers may spot possible issues early on and improve code readability by assessing complexity, minimizing errors and enabling future advancements. You can measure the code complexity by using various metrics, including:

1. Cyclomatic complexity or McGabe Complexity

The most popular way to measure code complexity is Cyclomatic complexity develop by Thomas J. McCabe, Sr. in 1976. In fact, it comes in-built in many code editors like VS Code, linters like jslinter, flake8 and IDEs like IntelliJ. Cyclomatic Complexity or McGabe complexity, named after its creator, is a measure of the linearly independent paths in a section/module. McGabe suggests the cyclomatic complexity be less than 10 for most cases, meaning a score above 10 is enough cause to refactor the code.

To calculate the cyclomatic complexity of a program, it's best to draw the control-flow graph and use the formula:

M = E − N + P

Where, 

M = Cyclomatic Complexity,

E = Number of edges,

N = Number of nodes, and

P = Number of connected components

2. Halstead volume

Halstead volume is part of a set of software metrics introduced by Maurice Howard Halstead in 1977. Similar to other Halstead complexity measures, Halstead volume takes into account the number of operators and operands and aims to describe the size of the implementation of the module or the algorithm. It is represented by the following formula:

V = N * log2(n)

Where, 

V = Halstead volume,

N = Program length,

And n = Program Vocabulary.

While,

Program Length = N = N1 + N2 = total number of operators + total number of operands

Program vocabulary = n = n1 + n2 = number of operators + number of operands

3. Maintainability Index

The Maintainability Index or MI is a score of how easy it is to maintain code. It is a combination of the four metrics: Cyclomatic complexity and Halstead volume, Lines of Code (LoC) and depth of inheritance. This is considered to be a metric that helps give an overall picture of complexity as it weighs Halstead volume and cyclomatic complexity against LoC and depth of inheritance. The traditional formula is defined as follows:

• Maintainability Index = 171 - 5.2 * ln(Halstead Volume) - 0.23 * (Cyclomatic Complexity) - 16.2 * ln(Lines of Code)

Since the above formula results in a range of [-∞, 171], a slightly modified formula is used to bind the range of MI to [0, 100]:

• Maintainability Index = MAX(0,(171 - 5.2 * ln(Halstead Volume) - 0.23 * (Cyclomatic Complexity) - 16.2 * ln(Lines of Code))*100 / 171)

Ideally, an MI of less than 10 is considered good, while 10 to 19 is acceptable, and scores >20 are considered a high priority for rework.

4. Cognitive Complexity

Cognitive Complexity is a way to measure how hard it is for someone to understand and work with a piece of code. It looks at things like how the code is organized and if there are complicated parts like nested loops or if statements.

The goal is to make the code easier to understand and work with by keeping things simple and organized. By reducing cognitive complexity, it becomes easier for developers to read and change the code, which leads to better-quality software.

5. Rework Ratio

As we know, code complexity is commonly measured using various metrics, one of which is the rework ratio. The rework ratio quantifies the amount of code that needs to be modified or rewritten after an initial implementation. It indicates the level of complexity and the potential for defects in the codebase.

To calculate the rework ratio, the number of code changes required in subsequent iterations or bug fixes is divided by the total lines of code.

For example, if the total time spent on rework is 100 hours and the total development time is 500 hours, the rework ratio would be (100 / 500) x 100 = 20%.

This metric provides insight into the maintainability and stability of the software.

Note that a high rework ratio suggests that the codebase is complex and prone to errors, requiring significant effort to fix or enhance. It highlights the need for better design and refactoring to improve code quality and reduce future rework.

6. Lines of Source Code or Lines of Executable Code

Code complexity is typically measured using various metrics, and neither "Lines of Source Code" nor "Lines of Executable Code" alone provide a comprehensive measure of complexity. Instead, a combination of different metrics is used to evaluate complexity accurately. These metrics include cyclomatic complexity, which quantifies the number of possible execution paths; Halstead complexity measures, which consider the number of operators and operands; and maintainability index, which incorporates factors like code size, complexity, and coupling.

Furthermore, other metrics like nesting depth, coupling between objects or modules, and code duplication can also be considered.

Analyzing different metrics, developers may better comprehend the codebase's complexity and make informed decisions about its readability, maintainability, and mistake likelihood.

7. Coupling/ Depth of Inheritance

Coupling refers to the interdependence between different modules or components in a codebase. It measures how closely one module is connected to another. High coupling indicates strong dependencies and makes the code more difficult to maintain and modify.

Instead, depth of inheritance measures the class hierarchy's levels. It represents the level of complexity in the inheritance structure. Deep inheritance hierarchies can lead to code that is harder to understand, test, and maintain.

These metrics are important because they provide insights into the complexity and maintainability of the code. Lower coupling and shallower inheritance hierarchies are desirable as they promote code reusability, modularity, and easier maintenance.

Let us talk about the benefits of measuring the code complexity.

Benefits of Measuring Code Complexity:

Measuring code complexity is an important aspect of software development that offers several benefits. Here are some key benefits of measuring code complexity:

1. Better Code Quality: Measuring code complexity allows developers to identify potential problems early in development. This, in turn, helps to improve code quality by ensuring that issues are addressed before the code is deployed in production. Code complexity metrics can also be used to set targets for code quality, which can help developers focus on writing cleaner, more maintainable code.
2. Improved Maintainability: Code complexity directly relates to the ease with which code can be maintained and updated. By measuring code complexity, developers can identify areas of the code that are difficult to maintain and improve. This can help reduce the cost of maintaining the code over time.
3. Reduced Bugs: Complex code is more prone to errors and bugs. By measuring code complexity, developers can identify areas of the code that are likely to cause problems and focus their testing efforts accordingly. This can reduce the number of bugs and improve the overall reliability of the code.
4. Faster Development: Measuring code complexity can also help to speed up development. By identifying areas of the code that are particularly complex, developers can focus on simplifying these areas, which can reduce the amount of time required to write, test and deploy the code.
5. Improved Collaboration: Code complexity metrics can identify areas of the code that are particularly complex and require additional expertise. This can help improve collaboration between team members, as developers with specific skills can be brought in to help with particularly complex code areas.
6. Better Code Documentation: By measuring code complexity, developers can identify areas of the code that are particularly complex and require additional documentation. This can help ensure the code is well-documented and easier to understand for other developers needing to work with it in the future.

Measuring code complexity is an important part of software development that can help to improve code quality, reduce bugs, improve maintainability, speed up development, and improve collaboration between team members.

What to do about Code Complexity?

Code complexity is an indicator of code quality and its ease of maintenance. Complexity directly impacts delivery times and the quality of products shipped by a team. Since products are usually maintained over a long time period, teams should strive to optimize complexity in order to allow long-term ease of use, readability, and maintenance of code.

Optimizing for complexity involves a careful study of the current patterns and setting of baselines and acceptable standards based on the observed patterns and industry standards. Metrics such as cycle time, throughput, review practice, focus time, communication patterns, etc., help engineering leaders measure and optimize code quality.

Simplify Your Code Complexity with Hatica

Hatica equips engineering leaders with granular visibility into dev team productivity alongside 60-plus other metrics enabling them to reduce bottlenecks to accelerated delivery and achieve a better developer experience. Learn how Hatica can help you build better engineering teams.

Request a demo →