От идеи до архитектуры: как создаются IT-системы

Telegram channel with a 32,000 audience - https://t.me/+qsHFsNDHcaMwZjUy Kirill Egorkin's Telegram channel (guest of this episode): https://t.me/fake_arch Course "Architecture for an Analyst" - https://systemanalyst.life/architectu... In this episode, we talk with Kirill Egorkin, a solutions architect, about how IT systems are actually created: from the first business idea to design, development, MVP, and pilot. It often seems that a system begins with a development task. But in practice, everything begins much earlier: with a business idea, a Vision, high-level requirements, a scope assessment, the choice of an architectural approach, and constant compromises between business, deadlines, budget, and technical constraints. In this episode, we discussed: — who comes up with the idea for a new system; — how a project's Vision is formed; — When to involve a systems analyst; — What is the difference between solution, enterprise, and enterprise architects; — How to study business processes before design; — What to do if the business itself cannot formulate requirements; — Where is the architect's responsibility, and where is the systems analyst's; — What artifacts does an architect create, and which does an analyst create; — How does business influence design decisions and how to work around this; — When to choose a monolith, and when microservices; — How to define microservice boundaries; — Why MVPs are often misunderstood; — What does an architect do during development and piloting; — How can a systems analyst develop architectural thinking. This issue will be useful for systems analysts, business analysts, aspiring architects, developers, and anyone who wants to understand how IT systems are designed not at the level of "drawing a diagram," but at the level of real decisions, tradeoffs, and responsibilities. Subscribe to the channel—new episodes on systems analysis, architecture, requirements, design, and real-life IT cases are coming soon. Timecodes: 00:00 — Preview 01:20 — Who is Kirill Egorkin and what does he do? 02:20 — Who comes up with the idea of ​​creating a system? 11:00 — How do you estimate the system's scope? 12:30 — What needs to be specified to limit the system's context? 16:45 — How to study processes? 20:10 — What to do if the owner doesn't know what they want? 27:00 — How to assess risks at the initial stage? 31:22 — Where are the responsibilities of the architect and analyst? 37:10 — Strong or weak analyst? 44:15 — Monolith or microservice? 48:55 — Microservice boundaries? 53:25 — How do you know when it's time to stop designing and start developing? 58:20 — What does an architect do when a system is being developed or is ready? 01:02:20 — How can a systems analyst think like an architect?