Note: If you think that you have eaten at least half a spoon on building architecture, then this article is not for you.
A model is an abstract representation of reality in any form.
We assume that the architect has already finished with the collection of requirements for the future system and their analysis.
')
The development of architecture needs to begin only with the concept and acceptance of the fundamental concept of working with information (data): transfer, storage and processing. Moreover, the information input / output forms, processing schemes, abstract structures of arrays and data elements are also information (as well as the entire application) and obey the same fundamental concept.

The fundamental concept leads to the emergence of the first ideas and the creation of the first data processing models.

Models of working with data may be called differently due to the difference of the concepts invested. One of the names of the data stream, where elements are usually future large modules that implement specific tasks of data manipulation.
The basis of the architecture (the main model) will be the basic data flow business process model (what the application will be intended for). This stage is very dangerous: a lot of original ideas can flood the architect. Need to keep this flow of ideas. Suppress the desire to dream or draw a bunch of unnecessary schemes. Now you need to create only one scheme of sequential acquisition of basic data, storage and processing. Nothing extra. There is no need for decomposition. Such a scheme is the basis, is the main representation of the architecture and should always be in sight. As a business process may act technological map.
The second major model will be with the addition of secondary business processes and data. For example, user models, access control (ACL), logging models, monitoring models, event model, etc. are added. On the basis of the second model, it is already possible to develop the first database schema and / or data storage, and an application prototype. At this stage, an understanding can come about whether to make a monolithic application, a component one, apply a microservice approach or some other. At the same time, the fact is interesting: between the monolith and each microservice (in microservice architecture) there are no differences from the point of view of the fundamental concept. From this point on, it is necessary to begin the development of a document on the substantiation of the architecture. The architecture justification document is a registrar of reasoning about the reasons for architecture decisions and clarifications.
Creating the first prototype of an application based on the second model can show the direct benefit of the application. The prototype will certainly be a formalized layout of the application. For example, instead of detailed forms, you can use conditional buttons that create a finished element based on random data generators.
After creating the second main model and the first prototype, you can start decomposition, consolidation, development of other architectural views and models. But the first main model and the second main model will be basic. In the process of further development, the first and second models can be improved, refined and refined.