CSC 205
Winter 2005
Professor Stearns
Software Design Checklist
Use this checklist to verify your Software Design.
Everyone is responsible for this verification; the editor takes
the hit if there are problems.
General
- Cover page contains Team Logo, 205 section # and date submitted.
- Document is of professional quality.
- Credits: the jobs of each individual are specified clearly.
("done by team" is
explicitly disallowed)
- Your team has done a design walk-through for every major use case.
i.e. Ensure your design handles every major use case.
English
- Writing meets the standards of a
the WPE level 4 or greater.
- All English, including diagram text, is written in the 3rd person
using active voice, present tense verbs.
- There are no words from the
bad words list
Main Javadoc File
- The overview is at least 2 pages and does a good job of describing
your overall design that any sophomore CSC student would understand.
- The UML diagram is embedded in the code.
- All important variables are declared.
- Your Javadoc URL is noted in the overview.
Javadocs
- Javadocs generated with -private flag
- There are excellent preconditions for public member functions
- UI design is clearly described and the basic philosophy is clear
- Method summaries are one short sentence.
- Whereever possible, names are from the problem domain.
- All important variables are declared.
- Function names use active voice present tense verbs.
- All fields and member functions use the problem domain.
- All member variables are private or protected.
- There are get/set members for every attribute.
- All names and relationships match the UML diagram
UML Class Diagram
- The names and relationships match the code exactly.
- All collection class element types are shown.
(e.g. A LinkedList of Clavitz - Clavitz is drawn)
- There are no associations in the diagram.
Compile/Javadoc
- A script file of a successful compile and Javadoc is shown.
- Javadoc has -private flag on.
Last updated on 3/8/05