tags:

views:

62

answers:

1

For those who document their architectures, what sort of artifacts to you produce and recommend?

I've been using the 4+1 Architectural View model for my last couple of projects, and I think it is quite a good approach. But I'm keen to hear if there are alternatives, and if there is an accepted "best practice" in this area. And especially if there is an archtiectural artifact that fits nicely with Scrum.

+1  A: 

4+1 works as well as anything. I've been using it and am reasonably happy.

Customers demand documentation. Their QA folks are happy with 4+1. I'm happy with 4+1 views.

Approximately no one has ever read a single word. How do I know? No questions after delivery.

S.Lott
Yes, I'm beginning to think that while architecture is essential, architectural doco is highly optional...
CraigS
Really, the most valuable thing is the simplified overview picture in a powerpoint presentation. That's what project managers, product owners, users, etc., can point to and articulate. Everything else is details.
S.Lott