那是一门基于罗赞斯基（Rozanski）和伍兹（Woods）合著的《软件系统架构》（Software Systems Architecture）的课程。讲师是丽贝卡·沃尔夫斯-布洛克（Rebecca Wirfs-Brock）。学习架构时，读这本书应该是一个非常有用的起点。要是决定去上这门课，关键在于……
It was a course based on the book Software Systems Architecture by Rozanski & Woods. The trainer was Rebecca Wirfs-Brock. Reading the book should be a very useful first step when learning about architecture. If one decides to go to the course it's essential that…
“Software Systems Architecture” by Rozanski Basically, it’s not about the code. It’s about the form following the function. That is, first, deeply understand the context and purpose of the software, and the structure will follow.…
I am a fan of Phillipe Krutchen's[1] "4+1" model[2], or variants thereof. The book Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives[3] by Eoin Woods and Nick Rozanski is a really good overview of the overall mechanism. Also, while this bit is probably overkill for your…
"Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives" by Nick Rozanski, Eóin Woods. Found this book really useful due to its methodical approach on views and perspectives. It really helped me…
听起来可能是废话，但“别试图把所有东西都塞进一张图里”真是我能给出的最中肯的建议了。我挺喜欢《软件系统架构》那本书里按“视点和视角”（Viewpoints and Perspectives）进行拆分的思路。https://www.viewpoints-and-perspectives.info/
Might seem obvious, but “don’t try to express everything one diagram” is some of the best advice I could give. I like the idea of breaking down by Viewpoints and Perspectives, from the book Software Systems Architecture. https://www.viewpoints-and-perspectives.info/
那是一门基于罗赞斯基（Rozanski）和伍兹（Woods）合著的《软件系统架构》（Software Systems Architecture）的课程。讲师是丽贝卡·沃尔夫斯-布洛克（Rebecca Wirfs-Brock）。学习架构时，读这本书应该是一个非常有用的起点。要是决定去上这门课，关键在于……
It was a course based on the book Software Systems Architecture by Rozanski & Woods. The trainer was Rebecca Wirfs-Brock. Reading the book should be a very useful first step when learning about architecture. If one decides to go to the course it's essential that…
罗赞斯基写的《软件系统架构》。基本上，它的核心不是代码，而是形式服从功能。也就是说，首先要深刻理解软件的业务背景和目标，结构自然就会水到渠成。……
“Software Systems Architecture” by Rozanski Basically, it’s not about the code. It’s about the form following the function. That is, first, deeply understand the context and purpose of the software, and the structure will follow.…
我是菲利普·克鲁赫滕[1]的“4+1”视图模型[2]（及其变体）的拥趸。埃恩·伍兹和尼克·罗赞斯基合著的《软件系统架构：基于视点和视角的利益相关者协作》[3]这本书对整体机制做了非常棒的梳理。此外，虽然这部分内容对你来说可能有点 overkill……
I am a fan of Phillipe Krutchen's[1] "4+1" model[2], or variants thereof. The book Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives[3] by Eoin Woods and Nick Rozanski is a really good overview of the overall mechanism. Also, while this bit is probably overkill for your…
尼克·罗赞斯基和埃恩·伍兹写的《软件系统架构：基于视点和视角的利益相关者协作》。我觉得这本书非常实用，因为它在视点和视角方面的方法论很系统。它真的帮到了我……
"Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives" by Nick Rozanski, Eóin Woods. Found this book really useful due to its methodical approach on views and perspectives. It really helped me…
听起来可能是废话，但“别试图把所有东西都塞进一张图里”真是我能给出的最中肯的建议了。我挺喜欢《软件系统架构》那本书里按“视点和视角”（Viewpoints and Perspectives）进行拆分的思路。https://www.viewpoints-and-perspectives.info/
Might seem obvious, but “don’t try to express everything one diagram” is some of the best advice I could give. I like the idea of breaking down by Viewpoints and Perspectives, from the book Software Systems Architecture. https://www.viewpoints-and-perspectives.info/