Skip to main content

Format for design, requirements, etc

Posted by staufferjames on October 21, 2010 at 8:02 AM PDT

Do a "requirements document" and "design document" use an outdated format? Is one monolithic document the right way to handle that information? Are there better ways to handle that information?

Consider this idea:

  • Keep requirements/design info in a tree structure.
  • Support viewing the whole tree to a specific depth so that people can ignore undesired detail.
  • Allow ownership to be set by branch.

Are there products/techniques currently available that handle this better?