Code Quality Basics - What Is Code Complexity?

In this article, we find out what code complexity is, and how we keep track of it.

You will learn

  • What Is Code Complexity?
  • What are a few examples of Code Complexity?
  • Why Is Code Complexity important?
  • What are the tools you can use to measure Code Complexity?
  • How can ensure that Code Complexity standards are Adhered to?

Article Series

This is third article in a series of 6 articles on important code quality terminology:

What Is Code Complexity?

Code Complexity is a measure of how difficult your code is to understand.

  • Suppose you have just written a method having 15 if conditions and 3 for loops. How easy do you think it is to understand?
  • Think of a class we have written that has 25 member variables and 75 methods, where some of these methods are huge, having a lot of if conditions and for loops. Is this an easy class to understand?

Measuring Code Complexity

Measuring Cyclomatic And Cognitive Complexity

Cyclomatic complexity is a way of measuring complexity taking into account

  • The number of if else switch conditionals
  • The number of loops - for , while and do while

There is a way to measure the code complexity in SonarQube as well:

image info

You can see that the has a cyclomatic complexity measure of 366. That means this class might be a little difficult to understand.

Let’s pick up another file which has a lower complexity listed:

image info

You can see that the findMemberType() method is being highlighted. When you click on it, you get some additional info:

image info

It says that the method has a different complexity measure, the cognitive complexity, that is bad for the code here. It suggests that we refactor this method to correct the complexity.

If you look at this method: image info

It has for loops, if, conditional operator at multiple places, all in interesting combinations!

A complex method is often a sign that the developer has not thought enough about the code.

Understanding Code Complexity

Whenever we write code, we need to keep things small. Simple methods, small classes, small packages, simple components all lead to small and simple applications.

The goal of writing code is not to write large amounts of it, but to achieve a certain functionality. The aim is to achieve that functionality with as little code and complexity as possible.

PMD is also a good static analysis tool to assess code complexity, apart from Sonar.

Addressing Code Complexity

In order to address the problem of complexity, you need to identify it early and monitor it on a regular basis.

You need to include code complexity goals as a major part of your coding standards. These should be regularly tracked.

Do check out our video on the same topic:

image info


Code complexity is a measure of how difficult it is to understand your code. Generally, large method and classes are code smells. There are different measures for code complexity, and various tools to measure them as well. Keep Refactoring code to reduce complexity.

10 Step Reference Courses

Image Image Image Image Image

in28Minutes is helping 300,000 Learners across the world reach their learning goals. Click here for the complete catalogue of 30 Courses.

Related Posts

Spring Boot Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. This resources will help you learn and gain expertise at Spring Boot.

Spring and Spring Boot Video Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. Here's a list of video tutorials and courses for you

Software Design - Separation Of Concerns - with examples

Software architects and programmers love having Seperation of Concerns. What is it? Why is it important? Let's get started.

Object Oriented Software Design - Solid Principles - with examples

Software design is typically complex. Object oriented design takes it to the next level. There are a number of design patterns and other stuff to be aware of. Can we make things simple? What are the goals to aim for when you are doing object oriented design? SOLID Principles is a great starting point for Object Oriented Design.

Software Design - Open Closed Principle - with examples

Open Closed Principle is one of the SOLID Principles. You want your code to be easily extended. How do you achieve it with minimum fuss? Let's get started.

Software Design - What is Dependency Inversion Principle?

Dependency Inversion Principle is one of the important SOLID Principles. Dependency Inversion Principle is implemented by one of the most popular Java frameworks - Spring. What is it all about? How does it help you design good applications?

Introduction to Four Principles Of Simple Design

With agile and extreme programming, the focus is on keeping your design simple. How do you keep your design simple? How do you decide whether your code is good enough?

Software Design - Single Responsibility Principle - with examples

For me, Single Responsibility Principle is the most important design principle. What is Single Responsibility Principle? How do you use it? How does it help with making your software better? Let's get started.

REST API Best Practices - With Design Examples from Java and Spring Web Services

Designing Great REST API is important to have great microservices. How do you design your REST API? What are the best practices?

Designing REST API - What is Code First Approach?

Designing Great REST API is important to have great microservices. Code First approach focuses on generating the contract from code. Is it the best possible approach?