All ISCs know the importance of making a good design before starting the development of a system due to the complexity it can have and the increase in the cost of making changes at late stages.
The architecture of a system goes beyond how it is going to be programmed, rather it focuses on the way in which its components are going to be related, to communicate and interact with each other. The importance of this is that programmers need to have a clear understanding of how the system will work because, obviously, they do not develop everything, but they are divided into teams that will be working independent modules that, at some point, must come together to comply with to system functionality.
Personally, it has happened to me that I have had to participate in large systems development projects in which the architecture design is not done and it is a complete headache that, during the whole development stage we have to ask some with others how we need the output or input of some module, how the connection of some modules will be made, if the system can work asynchronously or if the computer (or server in the cloud) we have will be able to handle all the requests that arrive .
Personally, I didn't know the 4 most recognized views of the software architecture, which are: the conceptual, implementation, process and deployment view. However, I think it is quite understandable that, like the architecture of a construction, there are different points of view to better understand the functionality of the system, how the connections will be made and, in general, the way in which the parts of the system will interact, to program them more accurately.
I believe that a good software architect can greatly facilitate the development of a project and significantly reduce rework costs or errors in the system if it is dedicated to making a clear, understandable and available architecture for everyone at all times.