Monthly Archives: May 2009

Alan Inglis posted about What good looks like from a solutions architecture perspective. How do you create a solution for a new project without creating architecture that already exists or making the same mistakes that previous projects made? This is a must read post and I recommend it.

Alan described 10 artefacts that he would expect a solutions architect to leave behind from a project implementation. They are:

Project Background

Terminology

Key Drivers, Principles, Standards and Constraints

Business Problem

Information View

Risk View

Application View

Data View

Integration View

Infrastructure View

I have some questions for Alan on this:

How big a project would require this level of artefact creation? For small and possibly medium projects, the work to do the architecture may be more than delivering the project.

Is there a subset of these artefacts that would be sufficient for small and medium projects?