Archive
Category: Software ArchitectureSome software architects tend to think a lot about our place in the software world. In a recent conversation with a colleague, I found myself in agreement with his description of the clear separation between software engineer and software architect. His argument wasn’t that the two roles couldn’t be fulfilled by the same person, simply that they are separate disciplines. I fully agreed, yet as I thought about it, I grew somewhat uncomfortable with my own conviction about the extent of this separation. I felt a need to try to establish what the relationship is, and perhaps what it should be.
Continue reading “Software Architecting .vs. Software Everything-else” »
Part I of this article described the various types of software architect. In this article we’ll describe the work they do, or should do, in a bit more detail.
Continue reading “The Role of the Software Architect, Part II” »
What does an architect do? This surely won’t be the last time this question is asked on this forum. It is an important question, and somewhat hard to pin down; especially when one considers the many titles of a Software Architect. There seems to be a general idea of what a software architect does, but many software managers don’t seem to believe the role is necessary, or even distinct: “Can’t we just have one of our senior developers do that?” Sure you can; If you have a senior developer who possesses those skills.
Continue reading “The Role of the Software Architect, Part I” »
Okay, that’s a bit strong, but it got your attention. In truth, I think design patterns are very useful things. They can aid in understanding software design, for documenting and communicating design, and for applying to or refactoring designs; but many people see them as something more. I saw a consulting job requirement a while ago, and one of the required skills was that the candidate “must have used ALL of the design patterns” documented in the GoF Book
