You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: guides/Training-guide-BARS/Home/Assure/Assure/SCAL.page.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Request for an **Account Manager** to be set up by sending an email to the BaRS
14
14
15
15
When planning a project to build a BaRS solution, the inclusion of assurance must exist from the outset.
16
16
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.
18
18
19
19
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.
0 commit comments