Spec Team- Roles in Spec Writing

Library functional or technical staff (SME- Subject Matter Experts) will be called upon to complete User Requirements or fSpecs as the first step of the OLE Development Process.  SME's on Spec Teams will be asked to complete the following documentation as part of the task of "Spec Writing".

Spec Writing Process Overview

The Tiger Team will be available to the Spec Team to answer any scoping questions, and the Tiger Team SA will coordinate all startup and mentoring to Spec Teams to ensure completion of requirements, documentation, and related modeling. Spec Writing will follow a basic process:

1. User Requirements/fSpecs completed by Spec Team.
2. fSpecs reviewed by Tiger Team- may come back to Spec Team with questions.
3. When evaluated as a "completed draft", the specs will be given to Project Management and placed into Spec Inventory. 
4. Specs from all the teams, as completed, are reviewed against planned release schedules, and scheduled for development.
5. Once scheduled for development, the SA/Systems Analyst from the Tiger Team and the Core Team will complete any final documentation, and will restart the process with SMEs. This may include:
   1. Q&A
   2. User Interface/User Design workshops
   3. Gap analysis discussions
   4. Clarifications on how we're coding.
6. As development gets underway, some of the SMEs (those designated for Testing) will begin to draft Test Scripts.
7. Test Scripts will then be used in the execution of User Acceptance Testing.

See Also: Functional Specifications Facilitators Guide

Task Assignments & Documentation

(6)- USER REQUIREMENTS -Spec team & SA

These are linked templates and tools that are required as part of spec-writing.
User Requirements template

• The User Requirements template should be used as the basis of all spec-writing by functional spec teams. Some efforts (such as architecture specs, ingest/load specs) may be documented via alternate documentation approaches, in order to convey detailed technical, API, or rules/overlay logic.
  Unknown macro: {html}

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

  List Acceptance criteria
  Table for roles/permissions
  Model for workflow
  Model for approval steps if any
  Business rules?

(12), (17)- HANDOFFS & REVIEWS

1. Participate in handoffs to developers if requested by SA (due to complexity of specs, or clarifications needed for how we implement).
2. Be available for periodic emails as follow-up and Q&A continue once coding starts.

See:Acceptance Criteria, Test Scripts & Testing
(16)- TEST SCRIPTS- once development is begun, then SA and Spec Team work with QA Manager/team to develop Test Scripts for each set of coded specs (note: some user stories in initial spec writing may have been adapted to Kuali technology OR been combined to code core functions).

(23), (25)-(26) TESTING: Spec Team, Tiger Team