Software's unique properties like invisibility and changeability create a communication gap between internal technical teams and external business stakeholders.
An architect's role involves a continuous cycle of gathering requirements, designing solutions, evaluating them, and verifying the final implementation.
The ISO 25010 standard provides a framework for defining crucial non-functional requirements that guide architectural decisions like choosing a monolith for performance.
Unplanned architecture leads to technical debt, which is often a symptom of deeper issues like missing requirements and a lack of documentation.
Software evolves through phases from initial development and feature addition to servicing and eventual phase-out, with early decisions impacting its entire lifespan.
Small, safe changes are refactoring, while large-scale changes like cloud migration are restructuring projects that require significant planning and investment.
Architecture extends beyond code to include layers like business, application, data, and technology, which together form the enterprise architecture.
The architect provides strategic oversight, ensuring the team stays on track by combining skills from development, testing, and product ownership.
30:14Eberhard Wolff
28:11Simon Lasselsberger
42:02Simon Lasselsberger
21:39Johannes Hansen
26:22David Tielke
26:15Gernot Starke & Benjamin Wolf
25:40Julian Lang
21:14Andrey Semenyuk
.gif?w=240&auto=compress,format)
.png?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
M&M Software GmbH
Sankt Georgen im Schwarzwald, Germany
Vesterling Consulting GmbH