I have been working in development since 2011. Since the end of 2012, I have been developing for iOS. I wrote my first technical article in Russian about a localization approach for the mobile apps on Habr in early 2017. Then I published several more articles on iOS development on Habr, and at the end of 2017, I moved to a new company and decided to write about solution architecture, where I began to describe general concepts, architect’s responsibilities, and skill-set, etc. By the summer of 2020, the number of views of my articles exceeded 800k, and the total time…


Solution Architect position becomes more and more popular nowadays. If ten years ago, there were almost no such roles in IT companies, then today those specialists can be seen in a lot of projects.

However, there are just a few sources and books which can help with Solution Architecture definition, Roles&Responsibilities, and required skills.

The goal of this Road Map is to help in understanding what the Solution Architect role is and how to grow in that direction. For such purposes, there is a plan to interview people who already play the Solution Architect role in different companies.

For me…


Image 1. Monument Valley Game

You can use it for interviews or assessments, pre-sales, or estimations.

1. Understand Problem and Scope

  • Recognize stakeholders and prioritize them. Create a RACI matrix
  • Understand business drivers of the project
  • Recognize end-users of the project and understand how they use that system
  • Check functional requirements
  • Define external dependencies
  • Suggest additional features
  • Remove items that interviewer considers out of scope

2. Think about constraints and non-functional requirements

  • (use PASS ME if you do not remember all of NFRs)
  • Recognize the number of users
  • Estimate users growth rate (for the next year/next five years)
  • Define average response time
  • Understand database size (current / for the next year/ for the next five years)
  • Understand…


Image 1. Monument valley game

Let’s continue to consider software architecture. After we recognized stakeholders, functional and non-functional requirements, it is time to document the results. That is why, in this article in the series, we consider the principles of working with architectural documentation.

However, before to dive deeper with individual cases, I would first like to note what we consider as architectural documentation. Unfortunately, there are no standards in software architecture that need to be followed when creating documentation, such as, for example, in the architecture of buildings. Also, each company may have its own rules for writing documentation, which you also need to…


Image 1. Monument Valley game

It is necessary to have much practical experience and an excellent theoretical background to be successful in any field of activity. The area of software architecture is no exception. If one can get their practical experience only from participating in real-life projects, the theoretical knowledge can be improved at home.

One of the main differences between the development theory and theory of software architecture is that knowledge is becoming obsolete more slowly for the latter. So, if you have found a resource of the 2000s, it is likely to be still relevant.

I would recommend you to start your acquaintance…


Image 1. Monument Valley game

Let’s continue investigating Software Architecture. We considered who is a Software Architect, what types of Software Architects exist, and what the architect should do at the beginning of a project. When stakeholders are identified, and requirements are collected, the question arises what to do next. After functional requirements are formulated — or the answer to the question “WHAT the system should do” is found, the software architect starts searching for the answer to the question “HOW the system should work.” Non-functional requirements help in that case.

Article series

  1. The Path to Becoming a Software Architect
  2. Stakeholders in Software Architecture
  3. Types of Software…


Image 1. Monument Valley game

Let’s continue investigating Software Architecture. In this article, we will consider the certification of architects. We will analyze issues related to the types of certificates and methods of obtaining them. Also, we will become aware of the need for certificates for a Software Architect.

Article series

  1. The Path to Becoming a Software Architect
  2. Stakeholders in Software Architecture
  3. Types of Software Architects
  4. Quality attributes in Software Architecture
  5. Documentation in Software Architecture
  6. Certificates in Software Architecture
  7. Books in Software Architecture
  8. System Design Cheat Sheet

Why does Software Architect need certificates

Certificates are an official and documented way to show your skills. According to Microsoft, 86% of recruiters track the existence…


Image 1. Monument Valley game

Let’s continue investigating Software Architecture. In every field of professional activity, there are various specializations. For example, in medicine, we have surgery, cardiology, ophthalmology, and many other areas. Or, for instance, management unites resource managers, PR managers, even cleaning managers!

Specialization is necessary when the amount of knowledge in the field exceeds a rational limit. And since the software architecture is a massive amount of knowledge, it is essential to reduce the duties of a person for better productivity. Therefore, the types of software architects will be discussed in this article.

Article series

  1. The Path to Becoming a Software Architect
  2. Stakeholders in…


Image 1. Monument valley game

Let’s continue investigating Software Architecture. Before reading, I recommend that you read the previous article from the series.

This time we will talk about the purpose of the development of projects, construction of architectural solutions, and programming of algorithms. Let’s talk about the people for whom this is done and who can influence the project.

Article series

  1. The Path to Becoming a Software Architect
  2. Stakeholders in Software Architecture
  3. Types of Software Architects
  4. Quality attributes in Software Architecture
  5. Documentation in Software Architecture
  6. Certificates in Software Architecture
  7. Books in Software Architecture
  8. System Design Cheat Sheet

Who is a stakeholder

There’s always one more System Stakeholder than you know…


Image source: monument valley game

Have you ever wondered what career opportunities a developer has? What directions are open, beyond what horizons to grow. And most importantly, where are developers beyond the age of 45? Is there a developer among your friends who is over 45? I know several developers beyond this age, and many of them are hardcore programmers who even saw punch cards back in the day.

There are several career paths a developer might take:

● The first and obvious one is to grow in the area in which you are working. …

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store