An article drawing an analogy between the architecture of software systems and the structure of businesses. Might be useful, but the commenters hanve a lot of reservations.
InfoQ: Thoughts On Software Architecture and Corporate Structure
This article certainly echoes some things which I have observed. It’s hard to gain the full power of an agile approach, if the agile teams don’t have the ability to address issues across the whole solution. However tempting it may seem to solve the problem of team size by splitting teams across architectural boundaries, this is rarely a good way to solve big problems in a smart way.
Splitting teams by task or feature, and letting each team solve their task or feature in a way which is optimal in the context of the whole system, will almost always result in a more effective solution, and often a solution which is actually much simpler/cheaper than the way it might have been achieved if each team only considered one part of the system.
InfoQ: Choose Feature Teams over Component Teams for Agility
RAM is the new disk…
19-Jun-08
I have been banging on about this for ages. Modern RAM sizes are so huge, and so much faster and easier to use than disk, that a lot of traditional assumptions about enterprise architectures need radical revision.
Loose Coupling in SOA Defined
17-Jun-08
One of the key tenets of the Service-Oriented Architecture (SOA) approach to software system design is the idea of loose coupling. In some cases it is pragmatically obvious whether one service is loosely or tightly coupled to another, but in the general case it can be tricky to determine. With that in mind InfoQ have produced an article on the topic.
This looks interesting, as much for the business model of establishing credibility through writing a blog, then monetising it in offering training. I have met Simon Brown and do think he knows what he is on about, though, so if you are in the market for software architect training, this should be worth a look.
Software architecture training for £500 - Coding the Architecture
An interview touching on problems with using UML to document software architecture and designs
InfoQ: Markus Voelter about Software Architecture Documentation