About Design Overview Documents

What are design documents?

• Design documents list feature sets and requirements, but not implementation details about how to fulfill those requirements.

Why do we have design documents, and who are they for?

• Initially, our design documents are intended primarily for the Design Working Group. These design documents summarize our discussions to date. They help us stay on the same page about the decisions made, and about the organization and priority of the issues yet to be threshed out.
• As we make progress, we want these docs to become definitive and complete enough so that
  • Mimi can use this doc as a basis for our UI Design
  • Apps Working Group can get a big picture sense of what Canoga will look like
  • for for each dot release (0.4, 0.5 etc.), engineering can implement a subset of the Canoga features

What material to design documents cover?

• To illustrate what we want Canoga to do, we often start a design doc with a set of use cases. While these use cases are not meant to be exhaustive, they are meant to represent the key use cases and thus the ones the Design group is focused on doing well.
• We then describe the key concepts and elements to construct a design framework.
• Finally, we describe a prioritized list of issues still unaddressed and what next steps we should take.

Is there a template for design overview documents?

* Yes, see Projects.TemplateDesign

What other types of pages are there?

• To find out about all the different "PageTypes", see About Page Types^?.

Add your question here...

• Add your answer here...

Contributors

• BrianDouglasSkinner - 16 Jan 2004 to 17 Mar 2004

Comments Welcome

This is a place for posting comments. Anyone is welcome to contribute here, with any sort of comment.