====== Quality assurance (Parameter database) ====== A parameter instance (a set of values belonging to a specific type of parameters and a specific scenario/case) has a usability status. The usability status positions the parameter in the quality assurance process. ^ Draft | Data has not been quality assured. | ^ Under revision | Data has been assigned to a reviewer for review. | ^ Returned from revision | RData has been reviewed. | ^ Accepted | Data has been reviewed by a reviewer and accepted by an administrator. | ^ Rejected | Data has been reviewed by a reviewer and rejected by an administrator. | **The quality assurance process** The quality assurance process can quickly be summarized by the following steps: A user with the role **Operator** or **Administrator** assigns values to parameters, either directly in the user interface or by importing values from Excel. The parameters now have the usability status of **Draft**. Only parameters with the usability status of **Draft** can be edited. The user submits the parameters for review and assigns a user with the role Reviewer to perform the review. The parameters now have the usability status **Under revision** and cannot be edited. The **Reviewer** logs into the database and reviews the values. The **Reviewer** can comment on each parameter and can also recommend or not recommend the parameter. When done, the Reviewer finalizes the review by changing the usability status to **Returned from revision**. An **Administrator** can now either **Accept** the reviewed parameters or **Reject** them. Only parameter values that have made it through the full quality assurance process are considered quality assured. If changes need to be made to a parameter with the usability status **Accepted** an administrator must either change the usability status back to **Draft**, or a new instance must be created. Also see: *[[Database design]] *[[Users and roles]] *[[dependencies_parameter_database|Dependencies]] ---- \\ [[parameter_database_wiki|Back]]