Do you write a separate database design document? Or include that details into technical specification?
What a good database design document should contains?
posted 8 years ago
Every document should contain exactly what the reader needs to know. That sounds like a smart-ass answer, but seriously, why else would you write one? So, you first need to meet your readers and find out what they need. Are they newbies who need everything spelled out? Experts who know more than you and I ever will and just need broad hints? Or is the reader just yourself - you need a diagram to work out some ideas and keep them straight? [ August 27, 2007: Message edited by: Stan James ]
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi