The difference between the software concept and software architecture

The concept is magic. If the architecture is the skeleton of a project, then the concept is its spirit. There is no concept, and the project leaves a lifeless body, from which it soon begins to stink. But when it is, the project develops, and the better the concept is executed, the healthier the project will be, and the more confident and successful the members of the project team will be.

But it is not enough to create a concept in a software development project and coordinate it with the customer. It is necessary that all development of a software system is carried out in full accordance with the accepted concept. No one should be allowed to violate it. Yes, it can and should be corrected if there are serious reasons. But the reasons must be serious. And the decision should be made at the highest level and always agreed with the customer.

Remember: if there is no concept, the project is dead. If some part of the project is not supported by the concept, this part of the project either dies or infects other parts of the project, and then the whole project dies. If the concept is there, but not fully implemented, then the project will stall every now and then and eventually go beyond the acceptable time frame and budget. If the concept of the team is different from the vision that was agreed with the customer, then you are not making the system that you were asked to do. I have never seen any compromises in these statements.