Description
Equip your architects and senior engineers to design systems that survive contact with reality — including the new reality of AI as both a tool that supports the architect and a component that runs inside the systems we design. The course goes from architectural fundamentals (quality attributes, tactics, views, ADRs, evaluation) to architecting in the AI era (agentic patterns, fitness functions, cost, non-determinism, prompt injection).
What the course covers
- The main concepts and context of software architecture — essential requirements identification, architectural design, architectural documentation, and architecture analysis.
- A clear understanding of what it means to be a software architect, as well as the different types of architects (e.g. enterprise, solution, software, and system).
- A structured way of collecting and documenting business requirements with an architectural impact (i.e. non-functional requirements) so they are quantifiable, measurable, and testable.
- Design techniques driven by Quality Attributes (availability, performance, scalability, security, modifiability, testability, usability).
- How to create proper and structured architectural documentation aligned to its purpose and beneficiaries (i.e. its users).
- Techniques to evaluate software architecture and mitigate architectural risk before it becomes an incident.
- A practical recipe to evaluate competing frameworks and libraries and pick the most suitable for the project’s context.
- How the architect’s role evolves in the AI era — AI both as a tool that supports the architect (gap analysis, fitness functions, diagrams from code) and as a component that runs inside the systems we design (non-determinism, cost, hallucinations, prompt injection, agentic patterns).
- A blend of lectures, individual and team exercises, and interactive workshops.
What You Will Learn
By the end of this course, your architects and senior engineers will be able to:
- Translate business goals and stakeholder concerns into measurable Architecturally Significant Requirements (ASRs).
- Apply proven architectural tactics for availability, performance, scalability, security, modifiability, testability, and usability.
- Document architecture for the right audience using established frameworks (Kruchten 4+1, C4, Rozanski & Woods) and a docs-as-code approach.
- Write Architectural Decision Records that act as active guardrails — including for AI-assisted development.
- Evaluate competing technologies and frameworks with a structured evaluation matrix instead of preference and hype.
- Design systems that embed AI components, explicitly accounting for non-determinism, cost, hallucinations, prompt injection, and agentic patterns.
- Evaluate an existing architecture and surface architectural risk early, not after the incident.
Agenda
Architecture Context Diagram
Software architect role and responsibilities
Essential architect’s skills
Architectural activities
- Reference architecture
- Architectural decision record
- Technology radar
- Prototype/skeleton
- Code and review
The software architect in Agile projects
What kind of project needs an architect?
Architect/Architecture in agile environments
Stakeholders. Business Goals. Quality Attributes
- Architecturally Significant Requirements
- Quality Attributes vs. Functional Requirements
- Quality Attribute Scenario
Basic tactics for designing the software architecture
- Availability
- Performance
- Scalability
- Security
- Modifiability
- Testability
- Usability
Documenting the software architecture
- Architectural Description
- Views & Viewpoints
- Kruchten’s 4+1 View Set
- Rozanski & Woods Viewpoint Set
- Simon Brown C4 Model
- Hierarchical Documentation Model
- Docs as Code
Technologies and frameworks from an architectural perspective
- Evaluation matrix
Evaluating the software architecture
Architecture in the AI Era
- What changes and what does not change
- Governing Architecture using AI
- Ways Architecture and AI Intersect
Duration
- 16 hours
Target Audience
- software developers
- technical leaders
- software/solution architects
- test engineers
- business analysts with a technical background or passionate about technology
Attendees’ Feedback
“I liked the structure of the course, the fact that we applied the concepts we learned by following a methodology creating an architecture starting from the requirements.”
“The course helped me understand the architectural concepts and the role of an architect.”
“The course helped me to learn the terminology better, by doing exercises, also with book recommendations, describing architectural tactics and generic patterns.”
“I was clarified regarding the diagrams (views and viewpoints) and regarding the applicability of some quality attributes.”
“The trainer is a true professional. He explained everything in detail as best as he could.”
“I think that diagrams are most useful. I think that they should be implemented for every project and presented to developers when they see a project for the first time, as it is easier to imagine and understand how a project works.”
Delivery Format
- Available online (live, instructor-led) and on-site at your company location.
- Delivered exclusively for companies, teams, or organized groups.
- Hands-on workshops and exercises are adapted to your team’s real-world scenarios.
- Individual (single-person) enrolment is not available at this time.
People from the following companies attended my courses:
Enroll
Note: At the moment this course is available only for companies, teams, or groups of students. The individual subscription (i.e. single person) is not an option at the moment.