CHRS Knowledge Base

Functional Spec Approval Process

Updated on

Things to Know

  • Functional Specs will be written continuously and sent to Subcommittees* as they are drafted
  • Functional Specs will be posted in the Design Spec Document Library
  • Subcommittees meet monthly to discuss and approve Functional Specs

*BSA and/or Subcommittee Task Force Member

What to Consider When Reviewing a Functional Spec

  • Does this Functional Spec include all of the requirements? If not, what is missing?
  • Are there additional details that should be added?
  • Does this cover the applicable use cases/scenarios?
  • What questions would I like to present to the team for review?

Approval Process

  1. Functional Spec Written
  2. Functional Spec Draft Posted for Stakeholder Review
  3. SMEs are Requested to Review
  4. Subcommittees Meet to Discuss Draft: Provide Feedback
  5. Functional Spec Updated & Share Mock Up (If Applicable)
  6. Functional Spec Approved
  7. Dev Lifecycle Continues
Functional Specifications Approval Process

End of Article

Previous Article (job aid) Change Control (CC) Request Process
Next Article (job aid) Roadmap and Releases
To request a new article or update: Contact Us