Workshop: Software Architecture design process #6

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.

Target Audience:

This workshop is for:

software developers who want to understand process of software architecture design, methods and principles; architects who want to find new approaches and structure their knowledge; Business and system analytics; DevOps; Delivery Managers; anyone who wants to know what software architecture development is.

Required knowledges:

Experience with software development and software delivery. Knowledge of Software Delivery Lifecycle (SDLC). Basic knowledge of architectural patterns and styles (e.g. microservices, SOA). Basic knowledge of UML. Engineering English (all materials and templates are in English).

Format:

Participants: up to 30 people
Duration: 3 days. Starting on December 13 at 6 p.m. (GMT+2)
Day 1: December 13, 2022 (18:00 - 21:00).
Day 2: December 15, 2022 (18:00 - 21:00).
Day 3: December 17, 2022 (10:00 - 17:00).
Language: Ukrainian
The course will be hosted online in Zoom

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 and enabled functions for Draw.IO.

Програма:

Day 1

Introduction

Theoretical Section – Software Architecture Fundamentals:

• What is Software Architecture and why is it important?
• Architect’s types of engagement, roles and responsibilities.
• System and Software Engineering - Architecture description - ISO/IEC/IEEE 42010.
• Architecture Development Lifecycle.
• Architecture Discovery.
• Architecture Significant Requirements overview.
• Q&A session.

Break.

Architecture in practice (Architectural Kata overview).

Practical Section – Architectural Significant Requirements clarification

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

Exercises:

— Stakeholder register;

— Architectural Vocabulary;

— Discovery Questions for greenfield and brownfield;

— Objectives & primary functional requirements identification;

— Constraints & Concerns.

Day 2

Theoretical Section

Architectural Requirements Analysis and Preparation before Design:

• Architectural Significant Requirements analysis.
• Quality Attributes overview and process of scenarios defining and prioritization.
• From Requirements to Decisions (preparation before Architectural Design): —Choice of methodologies. — Architectural roadmap. — Preparation of architectural principles.
• Architecture frameworks & reusable methods:
  — Trade Offs.
  — Hypothesis Driven-Development.
  — Component-Based Architecture (CBA).
  — ADD.
  — Microsoft Application Architecture Guide.
  — TOGAF.

• Q&A session.

Practical Section – Architectural Drivers analysis

Common goal: to understand the process of information analysis during architecture discovery, final deliverables after this phase and preparation before design.

Exercises:

— Architectural Principles specifying;
— Architecture Methods identification;
— Risks & Assumptions Register;
— Architecture Roadmap & Architecture Team.

Day 3

Theoretical Section

Architectural Design:

• Architectural Design concepts;
• Reference Architectures;
• Deployment Patterns;
• Architecture Patterns/Styles;
• Architecture Tactics;
• Q&A session.
Break.

Theoretical Section

Architectural Documentation:

• Architecture Documentation fundamentals;
• UML;
• C4 model;
• SEI Views & Beyond;
• Kruchten’s 4+1 View Model;
• ADR’s;
• Architecture documents templates;
• Q&A session.
Break.

Practical Section – Architectural Design and Views creation

Common goals: to create common 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 view 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 skill set & toolset;
• Resources for practice;
• Learning materials.