-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
e6b0780
commit 0a352a3
Showing
1 changed file
with
27 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
--- | ||
status: draft | ||
tags: | ||
- assurance | ||
- core elements | ||
--- | ||
|
||
# Core Elements of an Assurance Case | ||
|
||
!!! info "Summary" | ||
|
||
In this section we will look at the core elements of an assurance case and how they relate to one another. | ||
|
||
There are many ways to construct an assurance case and several standards exist to help users adopt shared practices. | ||
For instance, the Goal Structuring Notation has thorough and comprehensive documentation for building assurance cases that align with their standards. | ||
|
||
Trustworthy and Ethical Assurance diverges from other standards, primarily because it aims to simplify the process of developing and communicating assurance cases in order to open the process up to wider communities. | ||
That is, we prioritise *accessibility* and *simplicity*. | ||
The trade-off is that assurance cases developed using our platform are *less expressive* than others, but (hopefully) easier to understand. | ||
|
||
All assurance cases contain the following core elements: | ||
|
||
``` mermaid | ||
graph TD | ||
A[Goal] --> B(Claim); | ||
B:::annotate --> C[(Evidence)]; | ||
``` |