View online or download the slides from our conference presentations that cover the role of a software architect through to sharing and documenting your architecture.
One of my key points about software architecture is that it introduces structure and guidelines into a software system, which in turn leads to consistency and clarity of the overall design. Basically, I'm saying that there are some real benefits from ... There's some very interesting follow-up to a blog entry called If you’re an architect… on Edward Williams' blog and one of the questions that has just been posed is this. Is defining the development process (agile, waterfall - XP/Scrum/DSDM/Lean etc) ... I get my fair share of questions about software architecture; ranging from queries about the role through to "I have this problem, how would you design a solution"? This question, though, represents a fairly common situation but isn't one that I get ... A quick note to say that I'm presenting a free "In-the-brain" session at Skills Matter in London on the 8th of September. Writing code is easy. Writing good code is still relatively easy if you know what you're doing. Yet delivering quality software ... We had an interesting discussion on the course a couple of weeks ago that I thought was worth summarising here. One of the key functional requirements of the case study that we run through is that the system should be able to distribute data to a subset ... |
Read our software architecture document guidelines for our advice on what to include and why.
Join us for Software Architecture for Developers, a two-day training course about pragmatic software architecture designed by software architects that code.
Alternatively there's Enterprise Software Developer, a four-day practical training course about building software within an enterprise environment in a structured, lightweight and pragmatic way.
The line between software development and software architecture is a tricky one. Some people will tell you that it doesn't exist and that architecture is simply an extension of the design process undertaken by developers. Others will make out it's a massive gaping chasm that can only be crossed by lofty developers who believe you must always abstract your abstractions and not get bogged down by those pesky implementation details. As always, there's a pragmatic balance somewhere in the middle, but it does raise the interesting question of how you move from one to the other. Read more...
|
![]() @simonbrown and @kpseal |
|