Workshop: Software Architecture design process

If you have ever asked yourself the following questions in your life:

• What will be my role and what will be expected of me as an architect?
• Why architecture for a product if you can go to code right away?
• How to start developing architecture, what standards, methods and practices exist?
• What should be included in the architectural documentation?
• How to properly justify my chosen components, technologies and approaches?

Then this workshop is for you.

In the workshop you will be able to gain knowledge in the field of software architecture development; structure the already acquired knowledge; see where architecture begins, what approaches, standards and practices exist; gain practical skills from defining business goals of products and architectural drivers to developing architecture and architectural documentation.

Common Information

Day 1: 24 of July 2021 (10 am — 5 pm).

Day 2: 25 of July 2021 (10 am — 5 pm).

Number of participants: 50.

The workshop will start at 10:00 EEST and will be held online in Russian in Zoom. Please install Zoom on your device. You won't need to pre-install special software before the course, practictical part will be using Google services (e.g. Google Drive, Google Document, Draw.IO), so you need an account which supports these Google services.

For ticket holders, videos from the workshop will be available for 2 weeks, until August 8.

Required knowledges:

• Experience on software development or architecture;
• Basic knowledge on architecture patterns (e.g. microservices, SOA);
• Basic knowledge on UML;
• Engineering English.

Level of audience

This workshop is for:

• software developers who want to understand software architecture design methods and principles;
• architects who want to find new approaches and structure their knowledge;
• Business and system analytics;
• DevOps;
• PM’s;
• anyone who wants to know what software architecture development is.

Program

Day 1

Introduction

Theoretical Section — Software Architecture Fundamentals

First look into Software Architecture;

What is Software Architecture and why it’s important?

System and Software Engineering — Architecture description - ISO/IEC/IEEE 42010;

Architect roles & responsibilities;

Architect’s skill set.

Q&A session.

Break

Theoretical Section — Architecture development lifecycle and reusable methods

Architecture development lifecycle fundamentals;

Architecture frameworks & reusable methods (e.g. Trade-offs, TOGAF, ADD).

Q&A session.

Break

Theoretical Section — Analysis of Architectural Requirements

Architectural Drivers overview;

Process of analysis and collection of information;

Quality Attributes.

Q&A session.

Break

Practical Section

Introduction to Architectural Kata;

Architectural Drivers clarification. Common goal: to define architectural drivers for software architecture design (e.g. Stakeholders overview, Business Goals, Quality Attribute Scenarios, Constraints, Architectural Concerns).

Summary and Q&A session

Day 2

Introduction

Theoretical Section — Architectural Design

Architectural Design concepts;

Reference Architectures;

Deployment Patterns;

Architecture Patterns/Styles;

Architecture Tactics.

Q&A session.

Break

Theoretical Section — Creation of Architectural Documentation

Architecture Documentation fundamentals;

UML;

SEI Views & Beyond;

Kruchten’s 4+1 View Model;

C4 model;

ADR’s;

Architecture documents templates.

Q&A session

Break

Practical Section

Architectural Design and Views creation. Common goals: to create architectural decisions (choosing reference architectures, deployment patterns, architectural patterns, architectural tactics, mapping decisions to ASR’s), creation of common diagrams (e.g. component diagram, deployment, sequence, ERD, etc.), get acquainted with the structure of architectural documentation and views templates.

Theoretical Section — Architectural Evaluation & Implementation

Architecture Evaluation reusable methods (e.g. ATAM, CMMI, Cloud solution evaluation tools);

Architectural Implementation.

Summary

What we learned;

Architect’s toolset;

Resources for Practice;

Learning materials.

Q&A session.