Skip to content

Commit

Permalink
Updated website
Browse files Browse the repository at this point in the history
  • Loading branch information
@zarbspace
zarbspace committed Jun 18, 2024
1 parent bdf0e49 commit 6dab36d
Show file tree
Hide file tree
Showing 3 changed files with 48 additions and 18 deletions.
49 changes: 37 additions & 12 deletions docs/definitions_and_key_concepts.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,27 @@
margin: 0 0.8em 0.2em -1em; /* quarto-specific, see https://github.com/quarto-dev/quarto-cli/issues/4556 */
vertical-align: middle;
}
</style>
/* CSS for citations */
div.csl-bib-body { }
div.csl-entry {
clear: both;
margin-bottom: 0em;
}
.hanging-indent div.csl-entry {
margin-left:2em;
text-indent:-2em;
}
div.csl-left-margin {
min-width:2em;
float:left;
}
div.csl-right-inline {
margin-left:2em;
padding-left:1em;
}
div.csl-indent {
margin-left: 2em;
}</style>


<script src="site_libs/quarto-nav/quarto-nav.js"></script>
Expand Down Expand Up @@ -292,7 +312,7 @@ <h2 class="unnumbered anchored" data-anchor-id="assurance">Assurance</h2>
</section>
<section id="assurance-activities" class="level2 unnumbered">
<h2 class="unnumbered anchored" data-anchor-id="assurance-activities">Assurance activities</h2>
<p>Assurance activities are anything that is undertaken to validate and verify analysis</p>
<p>Assurance activities are anything that is undertaken to validate and verify analysis.</p>
<p>For example:</p>
<ul>
<li>analyst testing<br>
Expand All @@ -304,8 +324,8 @@ <h2 class="unnumbered anchored" data-anchor-id="assurance-activities">Assurance
</section>
<section id="business-critical-analysis" class="level2 unnumbered">
<h2 class="unnumbered anchored" data-anchor-id="business-critical-analysis">Business critical analysis</h2>
<p>Business critical analysis is defined as analysis which plays such a role in decision making that it influences significant financial and funding decisions, is necessary to the achievement of a Departmental business plan, or an error could have a significant reputational, economic or legal impact for the public sector.</p>
<p>Version 1 of the AQuA book described business critical models. This has been generalised to business critical analysis, as it is possible for analysis to be business critical without including a model. Some departments may continue to use the term business critical models (BCM).</p>
<p>Business critical analysis is analysis which plays such a role in decision making that it influences significant financial and funding decisions, is necessary to the achievement of a Departmental business plan, or where an error could have a significant reputational, economic or legal impact for the public sector.</p>
<p>The first edition of the AQuA book described business critical models. This has been generalised to business critical analysis, as it is possible for analysis to be business critical without including a model. Some departments may continue to use the term business critical models (BCM).</p>
</section>
<section id="change-control" class="level2 unnumbered">
<h2 class="unnumbered anchored" data-anchor-id="change-control">Change control</h2>
Expand All @@ -315,27 +335,27 @@ <h2 class="unnumbered anchored" data-anchor-id="change-control">Change control</
<h2 class="unnumbered anchored" data-anchor-id="documentation">Documentation</h2>
<section id="specification-documentation" class="level3 unnumbered">
<h3 class="unnumbered anchored" data-anchor-id="specification-documentation">Specification documentation</h3>
<p>This documentation captures the initial engagement with the commissioner and identifies the question, the context, and any boundaries of the analysis. It provides a definition of the scope and a mechanism for agreeing the project constraints, e.g., deadlines, available resources, and capturing what level of assurance is required by the commissioner.</p>
<p>This documentation captures the initial engagement with the commissioner and identifies the question, the context, and any boundaries of the analysis. It provides a definition of the scope and a mechanism for agreeing project constraints such as deadlines, available resources, and capturing what level of assurance is required by the commissioner.</p>
</section>
<section id="design-documentation" class="level3 unnumbered">
<h3 class="unnumbered anchored" data-anchor-id="design-documentation">Design documentation</h3>
<p>This document outlines the design of the analysis, including conceptual models to illustrate the analytical problem, and forms an important tool for ensuring that the analytical assurer has the confidence that the analyst can deliver quality analysis.</p>
<p>This document outlines the design of the analysis, including conceptual models to illustrate the analytical problem. It forms an important tool for ensuring that the Analytical Assurer has the confidence that the Analyst can deliver quality analysis.</p>
</section>
<section id="assumptions-log" class="level3 unnumbered">
<h3 class="unnumbered anchored" data-anchor-id="assumptions-log">Assumptions log</h3>
<p>A register of assumptions whether provided by the commissioner or derived by the analysis that have been risk assessed and signed off by an appropriate governance group or stakeholder. Assumption logs should describe each assumption, quantify its impact and reliability and set out when it was made, why it was made, who made it and who signed it off.</p>
<p>A register of assumptions, whether provided by the Commissioner or derived by the analysis, that have been risk assessed and signed off by an appropriate governance group or stakeholder. Assumption logs should describe each assumption, quantify its impact and reliability and set out when it was made, why it was made, who made it and who signed it off.</p>
</section>
<section id="decisions-log" class="level3 unnumbered">
<h3 class="unnumbered anchored" data-anchor-id="decisions-log">Decisions log</h3>
<p>A register of decisions whether provided by the commissioner or derived by the analysis that have been risk assessed and signed off by an appropriate governance group or stakeholder. Decisions logs should describe each decision and set out when it was made, why it was made, who made it and who signed it off.</p>
<p>A register of decisions, whether provided by the Commissioner or derived by the analysis, that have been risk assessed and signed off by an appropriate governance group or stakeholder. Decisions logs should describe each decision and set out when it was made, why it was made, who made it and who signed it off.</p>
</section>
<section id="data-log" class="level3 unnumbered">
<h3 class="unnumbered anchored" data-anchor-id="data-log">Data log</h3>
<p>A register of data provided by the commissioner or derived by the analysis that have been risked assessed and signed-off by an appropriate governance group or stakeholder.</p>
<p>A register of data provided by the Commissioner or derived by the analysis that has been risked assessed and signed-off by an appropriate governance group or stakeholder.</p>
</section>
<section id="quality-assurance-plan" class="level3 unnumbered">
<h3 class="unnumbered anchored" data-anchor-id="quality-assurance-plan">Quality assurance plan</h3>
<p>A detailed plan of what verification and validation activities should be produced identifying the key risk areas within the analysis. This should be thought about throughout the analytical lifecycle, from initial scoping, designing the analysis, to delivering the analysis. The areas identified in the plan can also form the basis of a log for those analysts conducting the verification and validation checks. Any additional verification and validation checks that have been performed should be recorded on the quality assurance plan.</p>
<p>A detailed plan of what verification and validation activities should be produced identifying the key risk areas within the analysis. The plan should be thought about throughout the analytical lifecycle, from initial scoping, designing the analysis, to delivering the analysis. The areas identified in the plan can also form the basis of a log for those analysts conducting the verification and validation checks. Any additional verification and validation checks that have been performed should be recorded on the quality assurance plan.</p>
</section>
<section id="user-technical-documentation" class="level3 unnumbered">
<h3 class="unnumbered anchored" data-anchor-id="user-technical-documentation">User / technical documentation</h3>
Expand Down Expand Up @@ -489,13 +509,18 @@ <h2 class="unnumbered anchored" data-anchor-id="uncertainty">Uncertainty</h2>
</section>
<section id="validation" class="level2 unnumbered">
<h2 class="unnumbered anchored" data-anchor-id="validation">Validation</h2>
<p>Add definition of validation.</p>
<p>Literally meaning to make valid, through the agreement of those judged competent to take such views. The central question that validation raises is the extent to which the right work is being engaged in, given the purpose and constraints placed upon that work. The key output from the validation process is a judgment, based on evidence, concerning the extent to which the work is “fit for purpose”. See <span class="citation" data-cites="glover2014">Glover (<a href="references.html#ref-glover2014" role="doc-biblioref">2014</a>)</span> for more information.</p>
</section>
<section id="verification" class="level2 unnumbered">
<h2 class="unnumbered anchored" data-anchor-id="verification">Verification</h2>
<p>Add definition of verification.</p>
<p>The extent to which the work that has been agreed to is being done in the ‘right’ or ‘accepted’ way, given the ‘art of the possible’. The key output from the verification process is a judgment, based on evidence, concerning the extent to which the agreed work has been conducted appropriately. See <span class="citation" data-cites="glover2014">Glover (<a href="references.html#ref-glover2014" role="doc-biblioref">2014</a>)</span> for more information.</p>


<div id="refs" class="references csl-bib-body hanging-indent" data-entry-spacing="0" role="list" style="display: none">
<div id="ref-glover2014" class="csl-entry" role="listitem">
Glover, Paul. 2014. <em>Verification and Validation for the AQuA Book</em>. DSTL Portsdown West Portsdown Hill Road Fareham PO17 6AD: HM Government. <a href="https://www.gov.uk/government/publications/verification-and-validation-for-the-aqua-book">https://www.gov.uk/government/publications/verification-and-validation-for-the-aqua-book</a>.
</div>
</div>
</section>

</main> <!-- /main -->
Expand Down
5 changes: 5 additions & 0 deletions docs/references.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -240,6 +240,11 @@ <h1 class="title">References</h1>


<div id="refs" class="references csl-bib-body hanging-indent" data-entry-spacing="0" role="list">
<div id="ref-glover2014" class="csl-entry" role="listitem">
Glover, Paul. 2014. <em>Verification and Validation for the AQuA
Book</em>. DSTL Portsdown West Portsdown Hill Road Fareham PO17 6AD: HM
Government. <a href="https://www.gov.uk/government/publications/verification-and-validation-for-the-aqua-book">https://www.gov.uk/government/publications/verification-and-validation-for-the-aqua-book</a>.
</div>
<div id="ref-knuth84" class="csl-entry" role="listitem">
Knuth, Donald E. 1984. <span>“Literate Programming.”</span> <em>Comput.
J.</em> 27 (2): 97–111. <a href="https://doi.org/10.1093/comjnl/27.2.97">https://doi.org/10.1093/comjnl/27.2.97</a>.
Expand Down
Loading

0 comments on commit 6dab36d

Please sign in to comment.