Skip to content
#Architecture

Experience of using the "Architecture as a Code" approach in Airplane Group - Roman Piontic, Valentin Kozlov - ArchDays 2023 (Category Architecture)

#Architecture #Software #SoftwareArchitecture #Management #Processes

Interesting. report Roman and Valentine's description of architecture on the latest ArchDays. The essence of the report is to show how this documentation is arranged in the construction company "Airplane", where so much is tied to information modeling. BIM (Building Information Model) to display the architecture of buildings built and built by the company "Airplane". The company decided to go further and become a truly development company and, as a result, it turned out a heterogeneous architecture of the enterprise associated with the autonomy of teams, the lack of a common understanding of the strategic goal. Then there were architects who tackled these problems with the help of architectural documentation, and it seems that they did quite well. Speaking of the report itself, First there was an attempt to use plantuml to build diagrams. Then there was an attempt to use structurizr to do the same.

  • Then everything came into use. DochubIt is said that it is not just pictures and documentation, but a whole "digital twin". Next comes the story of what Dochub can do: extensible metamodel, visualizations. (plantuml), connected plug-ins Then comes the introduction of the tool and the description of the first two levels of the C4 Model. (system and container levels) In general, in the "Airplane" tool took root and it is used to manage the architecture and further there are plans from this tool to move towards code and infra - conditionally issue access or resources only if everything is well documented in Dochub. By the way, this is a good motivation for teams to keep this documentation up to date, especially if it can be automated:)

The second half of the report is devoted to the story of plans to expand the tool and about the architect. 2.0about which there is a separate philosophy Quebec, whose main point is that

  • Architect. 2.0 It is human architecture and machine-readable data, unlike an architect. 1.0It uses visual diagrams and diagrams.
  • Architect. 2.0 It is about using the language of production, not inventing your own language.
  • Architect. 2.0 You must be able to influence the development of your tool and be able to refine it to meet the needs of business and developers.
  • Architect. 2.0 You should also be able to create new frameworks for the accumulation and development of architectural practices.

And this architect. 2.0 framework SEAF (Sber Enterprise Architecture Framework)which Roman briefly presented in the last 10 minutes of this talk. I will tell about him in a separate post, which will be based on another performance of Roman, where he almost an hour talks only about SEAF.

P.S. On the subject of architecture management, there have recently been several posts that are also interesting to read.

#Architecture #Software #SoftwareArchitecture #Management #Processes