Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Under Construction

6- USER REQUIREMENTS -Spec team & SA

    1. User Requirements template
    2. Data elements template
    3. List Acceptance criteria
    4. Table for roles/permissions
    5. Model for workflow
    6. Model for approval steps if any
    7. Business rules?
      8-REVIEW- Tiger Team
    8. Review and approve specs
    9. Finalize or add Acceptance Criteria- what and how?
    10. Note anything out of scope
    11. Meet with PM to help determine prioritization
    12. Sample data needs identified- given to SA and TC
    13. 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
    14. UI Rice 1.0/KFS e-doc template
    15. UI Rice 2.0/full web app template
    16. Roles/permissions added
    17. Rice workflows, approvals finalized
    18. 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)

  • No labels

Operated as a Community Resource by the Open Library Foundation