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

• Unknown macro: {html}

  <A href="https://docs.google.com/a/kuali.org/document/d/1mgymZ80ckxS02HdZjjLBU8GZv49Oum8t3egx0ftCs3M/edit?hl=en_US" mce_href="https://docs.google.com/a/kuali.org/document/d/1mgymZ80ckxS02HdZjjLBU8GZv49Oum8t3egx0ftCs3M/edit?hl=en_US" target="_Blank"><STRONG>Final Specifications Template</STRONG></A>

  • Sample: To be developed between SA & Core Team for next completed User Story Spec scheduled for development.
  • FINAL template includes ALL requirements sections
    • KFS existing functions can be translated in integrated spec format
    • SA's and Core Team can remove any sections not relevant to the spec in progress
• Unknown macro: {html}

  <A href="https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AlzG4eNDtxYpdDBaTmRjWGVsUnAzQU5kZ1pkUmVmUVE&hl=en_US#gid=0" mce_href="https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AlzG4eNDtxYpdDBaTmRjWGVsUnAzQU5kZ1pkUmVmUVE&hl=en_US#gid=0" target="_Blank"><STRONG>Blank Roles and Routing Template</STRONG></A>

• Unknown macro: {html}

  <A href="https://docs.google.com/a/kuali.org/document/d/10fgvhWMUOCLr2kvffy9RwIPnBs0vI-5sKcR70YjuTEw/edit?hl=en_US" mce_href="https://docs.google.com/a/kuali.org/document/d/10fgvhWMUOCLr2kvffy9RwIPnBs0vI-5sKcR70YjuTEw/edit?hl=en_US" target="_Blank"><STRONG>KRMS Rules Template</STRONG></A>

  (link to template location- early draft in progress)
• See Business Rules, Workflows, Roles & Reference Documentation: [Tiger Team SA\- Spec Writing & Analysis: Reference]
  
• Review or complete
  Unknown macro: {html}

   <A href="https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AlzG4eNDtxYpdFVZekVWUzdhT0U5M0JrcEwxNllTZUE&hl=en_US#gid=1" mce_href="https://docs.google.com/a/kuali.org/spreadsheet/ccc?key=0AlzG4eNDtxYpdFVZekVWUzdhT0U5M0JrcEwxNllTZUE&hl=en_US#gid=1" target="_Blank"><STRONG>Data Requirements Worksheet</STRONG></A>

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 User Requirements for KFS/inherited functions and UI translations
2. Complete existing User Requirements Sections and extend for
3. Complete Acceptance Criteria:
   1. Add/edit existing AC for functional requirements
   2. Add AC for non-functional requirements
4. Annotate Complex Business Rules Requirements (KRMS)
5. UI Wireframes
   1. including UI inventory
   2. Intra-spec, Intra-process UI and Navigation needs
6. Maintenance Document Needs (with Data Architect)

1. Workflow/Routing Requirements (as needed)
   1. Reconciliation & Additions to Roles/Permissions Matrix
2. Federated Search extensions (iterative workshops & documentation to extend Search/Docstore)

1. Document & System Control Requirements
   1. Audit Trail Requirements
   2. Version Control Requirements (Docstore)
   3. Document Statuses
2. Sample Data & Mappings for Testing (with spec team, TC)
3. Interoperability Requirements: API specification (from SA or TC member of Tiger Team) for system integration points

1. 1. including workflows and permissions for each
2. Error Handling and Messaging Requirements
3. Scalability/Load/Performance Requirements
4. Privacy Requirements (if applicable, and as extension of Permissions)
5. Dependencies (added to spec)
6. Index/links to Reference Documentation
7. Design & Implementation Notes (Assumptions, Constraints, Issues)

1. 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)