Let's say you're a software architect and you want to know how to arrive at and document a an architecture. This paper puts forth a process for accomplishing this objective. Architecture is documented from separate views, each with its own goal.
I thought this was a great approach to follow, for two reasons. One, in my experience, use cases or scenarios can be extremely useful for verifying what the customer is envisioning, and this process uses them extensively (the "+1"). Second, it is flexible. I often work on small projects, and following an exhaustive process for documentation will take longer than actually doing the designing and implementing.
I have not used the 4+1 model before, but I can envision using it more in the future. Anyone else have experience with it?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment