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.

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,
  3. Combine Spec Team drafts into final use case/specification document, or,
  4. Extract portions of Spec team draft into technical or foundational spec document (to enable coding of dependencies in advance)
  5. Admin: SA must annotate and track how final specs are being combined in 2,3,4 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)
  6. 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"
  7. ....move on to Testing Scripts, Testing, and back to additional functional specifications

Final Specification Templates

  • No labels