Take your architectural consulting skills to the next level with our intensive "Architecture in Consulting Workshop," led by renowned expert Dmytro Ovcharenko.
This hands-on training is designed to provide you with practical experience in key aspects of architectural consulting, including Project Pre-sale Technical Support, Project Discovery – Solution Architecture Design, and Solution Architecture Assessment. The workshop is based on the architectural methodology developed by the Software Engineering Institute at Carnegie Mellon University and revolves around a practical consulting simulation of an imaginary project with average complexity.
Date and time: 30.11-02.12, 10:00 - 18:00, (Kyiv time, GMT+3).
The training will be held online in Ukrainian, the number of participants is limited: 24 places.
The online event will be broadcast on the Zoom platform, we will send you the link to the meeting on the eve of the workshop, and you will also find it on this page.
The workshop consists of theory and practice, participants will work in three teams. Each block of theory is supported by practice in the Workbook. The teams will have a limited time for each task, and after each practice, team representatives will present the obtained result in turn.
Senior Software Engineer
Consulting Preparation. Learn how to plan and prepare for a successful Discovery phase, ensuring efficient execution of your consulting engagements.
Business Case Elicitation. Develop your ability to collect vital information about the Business Case, including business goals, constraints, primary Use Cases, and solution context.
Quality Attribute Workshop. Practice techniques for collecting, prioritizing, and refining system quality requirements through Quality Attribute Scenarios, while uncovering technical issues, risks, and constraints related to system quality attributes (*-bilities).
Attribute-Driven Design. Discover the power of attribute-driven design to define solution architecture driven by significant architectural drivers.
Analysis, Planning, Presenting. Enhance your skills in tradeoff and risk analysis, implementation planning, and vision presentation to effectively communicate your architectural solutions.
Who is an Architect?
An Architect is a technical expert who makes high-level design choices. He communicates these decisions, agrees with stakeholders, documents them, governs, and ensures that they are implemented correctly. You may see him as the CIO/CTO of a project. The Architect is the person who is responsible for the quality of the technical solution. Architects have a holistic view and see the bigger picture to understand how the whole system works as a whole. What is architecture, architecture lifecycle, type of architects, etc
SAR - significant architecture requirements/Architecture Drivers We will discuss the quality attribute workshop (QAW) and quality attributes scenarios. Quality Attribute scenarios define what Scalability, Performance, Deployability, Maintainability, Testability, and other system quality requirements mean for the specific system and what to test or measure (fitness functions) to determine whether the system complies with these requirements or not.
ADD - attribute-driven design
There are a few concepts core to attribute-driven architectural design. These concepts define the building blocks an architect operates to design a software solution architecture. Those concepts are:
1. Reference Architecture (along with the architecture type or archetype)
2. Architectural Patterns and Styles, as well as Design Patterns
3. Design Tactics
4. Technologies in the broad sense of the word (standards, frameworks, languages, tools, external services)
Solutions architecture documentation Architectural Documentation is a primary persistent deliverable expected from a software architect. An architect can write code and configure software, talk to the stakeholders, make whiteboard sketches, and perform code inspections. However, all these activities are either not directly relevant to the core architectural duties or do not generate long-living outputs the development team, business stakeholders, future architects, and others can rely on to make their decisions, guide their development process, and assess and improve the existing architecture.
The Architecture Trade-Off Analysis Method (ATAM) is a structured approach to evaluating software architecture that helps to identify and prioritize the trade-offs among different quality attributes of a software system.
ATAM was developed by the Software Engineering Institute (SEI) at Carnegie Mellon University and has been widely used in industry for evaluating software architecture. The method involves a series of steps that help to identify and analyze the different quality attributes of a software system, such as performance, scalability, reliability, and security.
— Dima has got over 15-year experience in IT.
— For the last decade, Dima has lead System Architecture Group, crucial technology directions and consulting services in one of the biggest Ukrainian service companies.
— As a technology leader, Dima continues growing architecture and consulting experience in the N-iX company.
— As an architecture trainer and speaker Dima tries to share his experience with the community via custom training, conferences, and architecture meetups.
The course is being held again, we are sharing real reviews from the last time (with the permission of the participants)
Access to the workshop
Access to the workshop recording by year
Additional workshop materials from the speaker
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.