Главная
Study mode:
on
1
Introduction
2
Diagrams
3
Upfront Design
4
What are your boxes
5
Why dont you use UML
6
Whats wrong with diagrams
7
Architecture diagrams
8
Tech decisions
9
Up front design
10
Significant decisions
11
A ubiquitous language
12
System context diagrams
13
Spark meaningful questions
14
Risk storming
Description:
Explore the importance of upfront software design in this thought-provoking conference talk from YOW! 2019. Delve into the balance between agile methodologies and architectural thinking as Simon Brown, author of "Software Architecture for Developers" and creator of the C4 model, challenges the notion that all design should emerge during development. Learn how to create a sufficient starting point for your software projects, avoiding costly rework and refactoring. Discover techniques for effective diagramming, modeling, and documentation that support meaningful architectural discussions. Gain insights into creating system context diagrams, establishing a ubiquitous language, and making significant design decisions early in the process. Understand the value of sparking meaningful questions and conducting risk storming sessions to improve your software design approach.

The Lost Art of Software Design

GOTO Conferences
Add to list
0:00 / 0:00