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...
|
||||
|
||||
|
I had a fantastic time presenting and discussing software architecture at my IASA session called Where do you start? on Tuesday evening. We went through the things that you should do if tasked with designing a software system given a wish-list and a ...
Just a short post to provide a rundown of the events that we'll be speaking at over the next couple of weeks. Kevin and I are presenting a one-day tutorial at QCon London 2010 called Software Architecture for Developers, which covers the ... This is a follow-up to Designing enhancements, where I briefly talked about how enhancements to existing software systems can benefit from the principles and practices of good software architecture, particularly where interfaces to other systems are ... Whenever we talk about software architecture, undoubtedly we'll end up talking about the "big picture", but what exactly does this mean? Read the full essay... We're enhancing one of the software systems that I'm involved with, where we're adding new functionality into some of the existing use cases. If you imagine that these use cases are implemented by the users working through a number of pages in a web ... |
Join us for Software Architecture for Developers, a two-day training course about pragmatic software architecture designed by software architects that code. Preview the slides - there's no death by PowerPoint on this course!
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.
Read our software architecture document guidelines for our advice on what to include and why. |
|||
![]() @simonbrown and @kpseal |
|
|||