Many people believe that the task of architects is to create diagrams and diagrams, and among the broad masses this activity generally has the informal name “draw squares”. To some extent, this is true, and the architect spends part of the time on this. Indeed, the main result of the architect’s work is a document, and not a piece of code or a ready-made software module, like a developer’s, or tuned equipment, like an engineer’s. In a number of cases, the attitude to this “drawing of squares” is condescending, but in practice, very often, what is drawn in them will later be realized in life.
Therefore, despite this condescension, it is necessary to relate to the created diagrams with all responsibility. In this regard, it is logical to think about how to create architectural artifacts correctly: documents with descriptions, diagrams, models? How to make architectural documents as useful as possible and used by other technical specialists in the project? How to avoid mistakes? Are there already described processes, special tools, and just recommendations? If the project is complex and several architects participate in it in different roles (for example, from infrastructure, from application modules and corporate), then how to properly distribute responsibilities, who does what and in what format?
We give a definition and make analogies
. ? — , - . , . , -. , , , . (user manual) – , , , .
vs – ?
. , – . : , , , , , . , — . , ( – ) .
, , . , -, . , . IBM, , Unified Method Framework, , , , . The Open Group Architecture Framework (TOGAF) Architecture Development Method (ADM) .
, , ? -, (, Architecture Quickstart, Agile with Discipline). , , , ( ) . , , , . , .
: . , : , , . , . , , Agile , DevOps .
(work products). 2 : deliverables ( ). – . , gap- , (use cases). , cloud-native data reservoir.
deliverables , . , deliverable . 10 , -, , , , : , , .
, , . test-driven , – . , .
, . , ( , ), ( , , ), . — , , – , .
, – , , . , . IBM, , IBM MethodWeb, . , , ( Rational System/Software Architect . , , xml .
–
, , . – , (IBM Garage Method – cloud-native ) - (Enterprise Design Thinking). , .
, . IBM, , . , : , ( pre-sale, , ( delivery). , , (enterprise architecture). , Agile , – waterfall. , cloud-native . , , SAP Oracle, .
. , , , . , , service mesh . , .
IBM , - ( , .) , , . , , , ., . , .
?
– , . , . , . . IBM (Architecture Quickstart), (Team Solution Design), – (IBM Garage Method).
, , – , , , . , , , - . , , – . 100%, , , . , - , - , - . , , , .