Final Functional Specifications

In the revised OLE Development process, we are distinguishing between:

• User Requirements- preliminary functional requirements documented by the Spec Teams for User Stories
• Complete & Final Functional Specifications- taking the above draft user requirements, and translating into FINAL codeable specs for developers

Completing Final Functional Specifications

1. Review Draft User Requirements
2. Use Spec Team Draft User Requirements to start and extend [final specs], or,
   1. Combine multiple Spec Team drafts into final use case/specification document (if determined with BA), or,
   2. Extract portions of Spec team draft into technical or foundational spec document (to enable coding of dependencies in advance. Ex. Circulation Policy, Instance Record)
3. Admin: SA must annotate and track how final specs are being combined in #2 above and reflect those changes in
   Unknown macro: {html}

   <A href="https://jira.kuali.org/browse/OLE" mce_href="https://jira.kuali.org/browse/OLE" target="_Blank">OLE Jira</A>

   (exact admin process being determined for turning over specs to Project Management and Spec inventory)
4. Work with Core Team, Developers and Technical Architect to inform follow-on or confirming Technical Specifications, or how we will "interpret functional requirements in KFS-Rice coding"

Final Specification Templates

<insert templates here- coming soon>

<insert KFS translation template (if using existing UI/code for OLE)- coming soon>

Sample Final/Complete Spec: To be developed between SA & Core Team for next completed User Story Spec scheduled for development.

Final specification will need to extend the draft User Requirements, by filling in any gaps or additional details, and then augmenting those specs with Non-Functional Requirements (where applicable). In total, may include:

1. Extend Acceptance Criteria:
   1. Add/edit existing AC for functional requirements
   2. Add AC for non-functional requirements
2. Document & System Control Requirements
   1. Audit Trail Requirements
   2. Version Control Requirements (Docstore)
   3. Document Statuses
3. Sample Data & Mappings for Testing (with spec team, TC)
4. Interoperability Requirements: API specification (from SA or TC member of Tiger Team) for system integration points
5. Maintenance Document Needs (with Data Architect)
   1. including workflows and permissions for each
6. Error Handling and Messaging Requirements
7. Scalability/Load/Performance Requirements
8. Privacy Requirements (if applicable, and as extension of Permissions)
9. Dependencies (added to spec)
10. UI Wireframes
    1. including UI inventory
    2. Intra-spec, Intra-process UI and Navigation needs
11. Index/links to Reference Documentation
12. Federated Search extensions (iterative workshops & documentation to extend Search/Docstore)
13. Design & Implementation Notes (Assumptions, Constraints, Issues)
14. Reconciliation & Additions to Roles/Permissions Matrix
15. Workflow/Routing Requirements (as needed)
16. Annotate Complex Business Rules Requirements (KRMS)
17. Change Control (documentation)

Extensions to Final Specifications

1. Specifications checklist (as needed)
2. Change Controls
3. Reference Documentation
4. Gap Analysis
5. Jira maintenance (for Requirements Traceability)