Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • This answer is "correct", but doesn't really think beyond that. What about an architecture design for example? What about developer/business turnover? How is this handled by lots of quality unit tests? Commented Aug 29, 2012 at 14:10
  • @Paul: It is a good idea to have VERY high-level architecture diagrams, along with very light-weight coding standards, for new-comers. I've found that a good way to keep those documents up-to-date is to keep them in a wiki and get each newcomer to update where they find it is dated. But this question was about up-front design documents specifically. Commented Aug 29, 2012 at 14:31
  • I still stand by what I'm saying. Change Architecture to whatever the business wants to call it, and change unit tests to regression tests (automated?) and it applies. Commented Aug 29, 2012 at 17:03
  • @Paul: Sorry, I'm not following. What worthwhile document do you think I'm suggesting is bad? Commented Aug 29, 2012 at 19:59