Skip to content

Commit f52fb35

Browse files
committed
Update SCAL.page.md
NBRS-4886 Correct assurance guidance wording
1 parent 00c7ec2 commit f52fb35

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

guides/Training-guide-BARS/Home/Assure/Assure/SCAL.page.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Request for an **Account Manager** to be set up by sending an email to the BaRS
1414

1515
When planning a project to build a BaRS solution, the inclusion of assurance must exist from the outset.
1616

17-
The process of being assured via the SCAL can vary depending on the completeness and quality of the first submission, requests for further information, and any required resumbmissions review by the Solution Assurance team. Sufficient time should therefore be included in any project plan for the assurance process.
17+
The process of being assured via the SCAL can vary depending on the completeness and quality of the first submission, requests for further information, and any required resumbmissions after review by the Solution Assurance team. Sufficient time should therefore be included in any project plan for the assurance process.
1818

1919
It is advised the SCAL requirements are reviewed after reading the implementation guidance. The two combined will help build a backlog of requirements for the anticipated solution. For example, there is implementation guidance for {{pagelink:core-EHFailureScenarios-1.1.3, text:error handling}} while the SCAL highlights the expectation for logging and auditing of errors.
2020

0 commit comments

Comments
 (0)