Course: Software Architecture Design in practice
Mentor - Oleksandr Savchenko, Solutioning Director at Ciklum, practicing architect, speaker at global conferences and course author
During this course, you will go through all stages of software architecture development: from the design of a new solution to aspects of evaluating and improving the architecture of an existing product.
✔️9 online sessions
✔️10+ hours of theory
✔️10+ hours of practice
✔️8 practical online exercises
✔️8 homework assignments
Mentor - Oleksandr Savchenko, Solutioning Director at Ciklum, a practicing architect, speaker at global conferences, and course author.
About the course:
Architecture is the foundation of any software product. It defines the main components, their relationships, and the rules that ensure the correct and efficient operation of the entire system.
That is why it is important for engineers not only to understand what architecture is, but also to know in detail the process of its development. All developers in one way or another encounter either the architecture of individual programs/services (Application Architecture), or the architecture of an entire product (Solution Architecture), or even the architecture of the entire company (Enterprise Architecture).
The software architecture development process is a structured approach to creating a plan for a system that ensures its compliance with all business requirements and quality indicators.
It begins with an analysis of requirements: functional and non-functional, which determine what the system should do and how, and the identification of Architecturally Significant Requirements (ASR). At the same time, non-functional requirements (for example: performance, security, reliability) often influence architectural solutions more than functional ones, since they determine the boundaries and direction of the design.
Next comes design (analysis of alternative solutions and selection of the most suitable ones), which includes the choice of architectural style, architectural patterns, development of infrastructure aspects, detailed technical aspects of each of the components and all aspects of development. A parallel stage is documentation of architectural solutions, which includes the creation of diagrams and descriptions (ADRs) that demonstrate the structure of the system, the relationships between components, interaction protocols and rules for distributing responsibilities.
Transparent and understandable documentation helps all team members understand and follow a single architectural vision during implementation - the development of components according to the chosen architecture. The Architect's work does not end here and it is very important to continuously improve the architecture while focusing on an evolutionary approach, rather than on technologies that change very rapidly.
Another important stage is verifying the architecture and implementation for compliance with requirements and constraints. This may include modeling, prototyping, or conducting architectural reviews, during which possible risks and ways to minimize them are analyzed.
Audience:
- Architects, CTO
- Tech / Team leads
- Business and system analysts
- DevOps
- Senior / Middle developers
- Engineering managers
- Project managers
Required knowledge:
- 3+ years of IT experience
- experience with online whiteboards (preferably Miro)
- intermediate level of engineering English (all training and template materials in English).
Why should people who have participated in previous courses/workshops come?
- Course modules are more focused on giving practical skills that can be used as soon as possible
- Revised and improved modules of previous courses with a focus on practical use at work (for example, the module on Requirements Analysis (identifying ASRs) gives a clear picture of how to describe all ASRs and how to link them together based on templates, as identify risks and describe assumptions)
- Removed descriptions of legacy methodologies and frameworks, with a focus only on actual methods that should be implemented now
- New Architectural Kata, which will include design development and integration of AI components, Data integration patterns
- A new approach to doing online exercises in Architectural Kata
New topics:
- The process of introducing the Architectural Department (Design Committee)
- AI Reference Architectures and Architectural Styles/Patterns
- ADR implementation process
- Preparation for implementation and creation of a development strategy
- Building a detailed test strategy
- Preparation for release
- Specifics of architecture design/improvement for the existing project (architecture design for Brownfield)
Format:
How it will happen: Lecture, Q&A, group practice.
Platform: Zoom. We will send you a link to the broadcast on the eve of the course, and it will also be available on this page. In addition, all materials and recordings of the lectures will be available on the learning platform.
Language of the event and presentation: Ukrainian
The number of participants is limited: 30 places
Course Schedule
Week 1 (Fundamentals & ASRs)
Week 2 (Architectural Design)
Week 3 (Architectural Implementation & Evaluation)
Mentor: Oleksandr Savchenko
— More than 16 years in IT (inc. 8+ years in enterprise and software architecture)
— Hands-on Software Architect, Solutioning Director.
— Speaker at global conferences, author of software architecture courses and workshops, has taught more than 500 people in the last year, which helped them delve into Architecture
— Went from developer to delivery director, head of departments
— Managed departments with 300+ people, led big programs (150+ engineers) from different business domains, modern technology stacks and complexity
— SEI/TOGAF/ITIL trained specialist, ICAgile Certified Professional, AWS accredited specialist
— For the past 2.5 years, he has been actively volunteering and participating in various projects that help the Armed Forces and civilians throughout Ukraine
Feedback:
The course is being repeated, we share real feedback from the last time (with the permission of the participants)
"I spent a long time coming up with the ASR/ADR concept, inventing my own bicycles. In this course you will be able to get the theory and practice of how to describe what solutions you had in the project and why they are like that. In my opinion, this course is a must-watch for all developers from product companies."
"The course helped me structure my knowledge, as well as learn a lot of new things, get acquainted with different methodologies and approaches to architecture development. Almost half of the course is practical tasks that require even greater involvement in studying the material. I also really like the presentation of the material itself, additional resources, recommendations, homework. After the course you get all the presentations, templates and a bunch of useful material."
"The course is useful to take to understand what architecture is, how it is built (chosen). What are the existing practices. It will be useful for those who have just started doing architecture or have little experience."
"The course provides a holistic understanding of both the architecture development process and the artifacts that are generated . Very useful for developers who are already involved in architecture development or planning to."
Ticket price
Access to 9 2-hour online course sessions
Access to course recording (1 year)
Access to the TG chat, where the speaker will answer questions
Presentations
Additional materials from the mentor
Certificate of workshop participant
Course participants receive a 10% discount on participation in Fwdays conferences
Available payment in installments from Monobank and purchase in installments from Privatbank
If after the first module you realize that the expectations are not met, we will give you a full refund.
Fwdays is Ukrainian company, that is why payment for services is made in the national currency of Hryvnia. You can see the approximate price in Euros at blocks with the price.