Continuous Architecture in Practice Eoin Woods & Simon Brown • GOTO 2021

Interview in two parts of Eoin Woods (Author of "Continuous Architecture in Practice")which he gave to Simon Brown. (Author of Software Architecture for Developers).

In first discuss At the beginning of the 2000s, Eoin and Nick Rozanski wrote a book called Software Systems Architecture: Working with Stakeholders Using Viewpoints and Perspectives. It was the time of waterfall, RUP. (rational unified processes)UML and other things that have lost popularity in our time Then there’s the immersion in what Viewpoints and Perspectives are all about – Eion talks about it.4+1 architectural view model"and how they expanded this approach." Next, the guys discuss the "context view", which was in the book "Software Systems Architecture", where this context should be in the product of the system, but in practice it turned out that no one has such a context and it has to be collected at the beginning of the design of the system.

• And everything goes on with the question of architectural documentation and what the minimum composition is needed - Eion answers that it all depends on the needs of stakeholders:) Next comes the guys from operations, compliance, ... Immediately discusses the story of self-documented code and the lack of documentation, as preached by Uncle Bob – this approach is questioned by the authors.

Wo second The discussion continues with other topics

• UML in 2021 Eoin has been promoting UML for years. 2021 Many people no longer know how to read or understand it. About synchronizing parts of the system - here is about modeling, unlike pictures in Power Point (can be seen in more detail in Simon Brown's speech about structurizr) About the difference between evolutionary and contionuos architecture - here the author compares the book evolutionary architecture (what discuss Book Club "Code of Architecture") A more practical approach to constantly working on the architecture of systems. About the importance of software architecture in the age of agile development, when issues of thinking architecture are dismissed as a rudiment of large up front investments and decide to just start writing code sprint by sprint:) About architectural thinking and smearing of architectural solutions during the software development life cycle with a shift to the left (shift left) About the practicality of the book "Continuous Architecture in Practice" - the target audience of the book according to the authors: practicing architects with experience and those who are new to this role:)

P.S. I already am. wrote About the principles of Continuous Architecture and what the book came to me. In fact, after these interviews, I liked the authors’ approach even more.

#Software #Architect #SystemDesign #Philosophy #SoftwareArchitecture #Processes #Management