Under Construction
6- USER REQUIREMENTS -Spec team & SA
- User Requirements template
- Data elements template
- List Acceptance criteria
- Table for roles/permissions
- Model for workflow
- Model for approval steps if any
- Business rules?
8-REVIEW- Tiger Team
- Review and approve specs
- Finalize or add Acceptance Criteria- what and how?
- Note anything out of scope
- Meet with PM to help determine prioritization
- Sample data needs identified- given to SA and TC
- Sample technical integration points culled by TC (ie for APIs, other tech specs needed)
11-CODEABLE SPECS- From above re-prioritization, SA and BA (with spec team or Tiger Team where needed) complete Functional Specs/Requirements docs for coding
- UI Rice 1.0/KFS e-doc template
- UI Rice 2.0/full web app template
- Roles/permissions added
- Rice workflows, approvals finalized
- Acceptance Criteria reviewed and completed?
12, 17- HANDOFFS & REVIEWS- SA, Spec Team, Tiger Team
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, SA, Tiger Team
(iterative) Gap Analysis: SA, Tiger Team
Summary: Business Rules
(insert table/link)
Summary: Workflows, Routing
(insert table/link)
Summary: Roles, Permissions
(insert table/link)