Page Comparison

{note}Under Construction.{note}
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



h2. Completing Final Functional Specifications

# Review Draft User Requirements
# Use Spec Team Draft User Requirements to start and extend final specs, or,
# Combine Spec Team drafts into final use case/specification document, or,
# Extract portions of Spec team draft into technical or foundational spec document (to enable coding of dependencies in advance)
# Admin: SA must annotate and track how final specs are being combined in 2,3,4 above and reflect those changes in {html}<A href="https://jira.kuali.org/browse/OLE" mce_href="https://jira.kuali.org/browse/OLE" target="_Blank">OLE Jira</A>{html} (exact admin process being determined for turning over specs to Project Management and Spec inventory)
# 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"
#
....move on to Testing Scripts, Testing, and back to additional functional specifications

Final Specification Templatesh2. Final Specification Templates

<insert templates here\- coming soon>

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 for:

# Audit Trail Requirements
# Version Control Requirements (Docstore)
# Sample Data & Mappings for Testing (with spec team, TC)
# Interoperability Requirements: API specification (from SA or TC member of Tiger Team) for system integration points
# Maintenance Document Needs (with Data Architect)
## including workflows and permissions for each
# Error Handling and Messaging Requirements
# Scalability/Load Requirements
# Privacy Requirements (if applicable, and as extension of Permissions)