the documentation

[jonniesweb]

a must have feature

• FRs should be in sync with the most recent version of the correction grid
• For traceability: refer to either the 2nd or 3rd edition rules
• do not forget to describe short scripts associated with testing each FR
• Please put each unbound UCM directly after its corresponding UCM
• IF YOU ARE RUNNING OUT OF TIME for the doc: downplay or forget bound UCMs, class diagrams and object specifications in that order
• Use the format of previously posted example documentation

Sections: Requirements

• [ ] Functional requirements
• [ ] Non functional requirements
• [ ] Assumptions

Use Cases

• [ ] Use case diagram
• [ ] Use cases
• [ ] Responsibilities
• [ ] Unbound UCMs
• [ ] Bound UCMs

Design Decisions

• [x] Decisions
• [ ] Structural model

Object Specifications

• [ ] for each class, or main ones at least

Interaction diagrams

• [ ] I don't even know

[zach-chai]

this is worth 10/35 apparently almost 30% very important

[jonniesweb]

Duplicated the use cases document that we had from iteration 1. The new one is called Final Documentation, and its in the same shared folder on drive.

[zach-chai]

woohoo