|
You may have seen this on Matt Deacon's blog already ... I'm running a session for the IASA UK chapter on the 9th of March in London. Where do you start? One of the hardest things about software development is being asked to come up with a design ...
I'm currently involved in a project to upgrade a third party piece of software and it's apparent that when the software was originally designed, the upgrade process was not considered. This became obvious when we totaled up the time required to perform, ... Sergey Mikhanov has written a blog entry called Why I don't believe in software architects that, along with the follow-up comments, makes for a good read. It discusses some of the ways that software architecture is typically viewed (e.g. models rather ... Onwards then. The plan for 2010 is simple ... more content about pragmatic software architecture and more training. I particularly want to tackle the practical side of the software design process, including how to approach software design given a blank ... My final highlight from 2009 is that we improved our Software Architecture for Developers training course by restructuring it and adding more content. We've run this course for several hundred people now and the feedback is consistently excellent. ... |
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 |
|