(6)- USER REQUIREMENTS -Spec team & SA
- User Requirements template
- Unknown macro: {html}
<A href=" https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AlzG4eNDtxYpdFVZekVWUzdhT0U5M0JrcEwxNllTZUE&hl=en_US#gid=0" mce_href=" https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AlzG4eNDtxYpdFVZekVWUzdhT0U5M0JrcEwxNllTZUE&hl=en_US#gid=0" target="_Blank">Data Requirements Template</A>
- List Acceptance criteria
- Table for roles/permissions
- Model for workflow
- Model for approval steps if any
- Business rules?
(12), (17)- HANDOFFS & REVIEWS
See:Acceptance Criteria, Test Scripts & Testing
(16)- TEST SCRIPTS- once development is begun, then SA and Spec Team work with QA Manager/team to develop Test Scripts for each set of coded specs (note: some user stories in initial spec writing may have been adapted to Kuali technology OR been combined to code core functions).
(23), (25)-(26) TESTING: Spec Team, Tiger Team