5 Qualities of a Great Software Architect


In this article, we look at some of the important qualities of a great software architect. Although we chiefly focus on application architects, most of these also hold true for enterprise architects as well.

Five Qualities Of Architects that we look at are

  • Great Communication
  • Great Technical Skills
  • Forward Thinker
  • Super Diagnostic Skills
  • Hands-on

This is the third article in the following series of articles on Software Architecture :

Great Communication

Architecture is all about conveying your vision to every member of the team. There are multiple stakeholders who are interested in knowing how we achieve business needs. Within a business, there are architects at multiple levels:

  • Enterprise Architects
  • Application Architects
  • Core Architects

Apart from them, there are other stakeholders such as:

  • Development Team
  • QA Team
  • Operations Team

It is vital that all these stakeholders have a clear view of the future direction of the business and technology.

Great Technical Skills

You being an architect, it is but natural for us to expect a great understanding of technology from you. You need to have a good grasp of concepts such as tools, languages, frameworks and tools used in the application.

This is something taken as a given!

Forward Thinker

As an architect, you need to be forward thinking and proactive. You need to understand where technology is heading, what kinds of architectures are trending, what programming languages are becoming popular, in what direction is the business headed, and what could be the business needs of the future.

You need to be able to have a plan of how to evolve the application to meet future business needs.

In the modern world of Agile practices, you should be able to break down these future expectations into manageable chunks, in order to evolve the application.

Super Diagnostic Skills

You need to be able to resolve real world problems the application might face. This is not just about handling exceptions. If the application has a security, scalability or performance issue, then the architect needs to get involved and work out a solution. This requires the ability to look at the big picture, and at the same time understand the minor details.

Hands-On

When needed, architects should be able to get the system up and running, checking out code from the repository, and start fixing bugs.

I loved working in organizations where even Enterprise Architects could get their hands dirty when needed. At a minimum, atleast the application architects should be able to write production code.

Do check out our video on this:

image info

Summary

In this article, we looked at the top 5 qualities of a great software architect has. Those are great communication, great technical skills, forward thinking, great diagnostic skills, and being hands-on.

10 Step Quick Introductions to Frameworks

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

Creating Spring Boot and Vue JS CRUD Full Stack Application with Maven

This guide helps you create a full stack application with all the CRUD (Create, Read, Update and Delete) features using Vue JS as Frontend framework and Spring Boot as the backend REST API. We use Maven as the build tool.

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.

What is an In Memory Database?

In this article, we understand what the term "In-Memory Database" actually means. We see what scenarios they can be used, and why they are important.