Difference between revisions of "Review Process"

From QIBA Wiki
Jump to: navigation, search
Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
The same review an approval process occurs prior to releasing a Public Comment Draft, a Reviewed, Draft, or a Tested Draft.  Just the criteria change.  
+
The same review and approval process occurs prior to releasing a Public Comment Draft, a Reviewed Draft, or a Tested Draft.  Just the criteria change.  
  
 
Remember, this is the QA point.  It doesn't have to be perfect.  '''It does have to be good'''.
 
Remember, this is the QA point.  It doesn't have to be perfect.  '''It does have to be good'''.

Revision as of 03:46, 20 August 2012

The same review and approval process occurs prior to releasing a Public Comment Draft, a Reviewed Draft, or a Tested Draft. Just the criteria change.

Remember, this is the QA point. It doesn't have to be perfect. It does have to be good.

Review and Approval

  • Judge the document to be fit for the next phase (Technical Committee)
    • Schedule review meeting(s) as needed with open committee
    • Submit document 1 week before review meeting
    • Line-by-line review/walkthrough led by editor
    • Resolve questions/comments/clarifications
    • Vote (for Public Comment) or Ballot (for Reviewed or Tested) to approve the document as fit for the next phase.

Criteria for publishing Public Comment draft

  • All open issues have been clearly listed
  • Some groundwork projects may be underway
  • Candidate resolutions have been selected for most/all issues and drafted into the Profile
  • All major mechanisms and profile details are mostly clear/complete enough to implement
  • It is clear what is required for a system/organization to claim compliance with the Profile
  • Compliance requirements are sufficient to accomplish the goal of the profile

Criteria for publishing Reviewed draft

  • Few, if any, groundwork projects remain active
  • All major mechanisms and profile details are clear/complete enough to implement
  • It is clear what is required for a system/organization to claim compliance with the Profile
  • Compliance requirements are sufficient to accomplish the goal of the profile

Criteria for publishing Tested draft

  • All open issues have been resolved
  • All major mechanisms and profile details have been tested in the field
  • Groundwork projects are complete
  • All major mechanisms and profile details are clear/complete enough to implement
  • It is clear what is required for a system/organization to claim compliance with the Profile
  • Compliance requirements are sufficient to accomplish the goal of the profile