(under construction)
The goal of the checklist, when complete, is to guide the overall specification process: from initial User Requirements with Spec teams full circle through testing, and any iterative gap analysis.
Functional Spec Teams
Goals/Objectives
The following is a detailed checklist for completing functional specifications, to ensure completeness of documentation, and full understanding of library requirements for:
- Functionality/functional overview
- Workflows
- Data elements, data flows
- Permissions
- Business Rules/Parameters
- E-doc Routing or approvals/Workflow
- KRMS/ advanced business rules
- Acceptance criteria and testing scripts
- User interface wireframes, navigation
- Search
Deliverables
The specific deliverables expected of functional spec teams are:
- Develop...
- Document ...
- Test ...
- Communicate...
Timeline
Phase |
Tasks |
Assigned to: |
Start Date |
Due Date |
Status |
|---|---|---|---|---|---|
Phase 1 - Planning |
Task 1 - Organize Team / Meetings |
|
|
|
|
|
Task 2 - Identify Goals / Deliverables |
|
|
|
|
|
Task 3 - Establish Timelines |
|
|
|
|
|
|
|
|
|
|
Phase 2 - Drafting |
Task 1 - Research / Analyze |
|
|
|
|
|
Task 2 - Write / Document |
|
|
|
|
|
Task 3 - Develop / Acceptance Criteria |
|
|
|
|
|
Task 4- List/define data elements |
|
|
|
|
|
|
|
|
|
|
Phase 3 - Reviewing |
Task 1 - Present / Communicate |
|
|
|
|
|
Task 2 - Implement / System Test |
|
|
|
|
|
Task 3 - |
|
|
|
|
|
|
|
|
|
|
Final Phase- Deliverable Package |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|