Jingga/Organization-Guide
1
0
Fork 0
mirror of https://github.com/Karaka-Management/Organization-Guide.git synced 2026-01-11 21:08:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update 01_Development_Risk Control Matrix.md

Browse Source 
Signed-off-by: Dennis Eichhorn <spl1nes.com@googlemail.com>
This commit is contained in:
Dennis Eichhorn 2024-03-20 09:24:21 +01:00 committed by GitHub
parent 1b726f60f8
commit eb93183453
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Processes/01_Development_Risk Control Matrix.md
View File

@ -11,7 +11,7 @@
| 7 | CTO/Code reviewer | Operational Risk (Development) | Faulty code due to code changes, additions, removal. | 5 | 1 | Many times a day | | Preventing (System & Manual) | Code tests are automatically run with testing tools. Optionally on the developer side but mandatory and automatic during the code merging. This includes static tests which require no self-written tests and developer written tests. | 2 | 1 | | | yes | yes | |
| 8 | CTO/Code reviewer | Operational Risk (Development) | Faulty code due to code changes, additions, removal. | 5 | 1 | Many times a day | | Preventing (Manual) | Code tests are manually checked and performed which allows handling exceptions and special cases. | 2 | 1 | | | yes | yes | |
| 9 | CTO/Code reviewer | Operational Risk (Development) | Faulty code due to code changes, additions, removal. | 5 | 4 | Many times a day | | Preventing (Manual) | A demo application allows code reviewer to test code changes from a end-user point of view in conjunction with the whole application, other modules and dummy data. | 2 | 1 | | | yes | yes | |
| 10 | CTO/Code reviewer | Operational Risk (Development) | Unauthorized code gets accepted. | 5 | 2 | Many times a day | | Preventing (System & Manual) | Manual and automatic code checks/tests and manual review by authorized and qualified developers ensures high quality and that only code authorized by these developers gets accepted. Developers who can accept code changes are carefully selected and their permissions are handled in the version control software. | | | | | yes | yes | |
| 10 | CTO/Code reviewer | Operational Risk (Development) | Unauthorized code gets accepted. | 5 | 5 | Many times a day | | Preventing (System & Manual) | Manual and automatic code checks/tests and manual review by authorized and qualified developers ensures high quality and that only code authorized by these developers gets accepted. Developers who can accept code changes are carefully selected and their permissions are handled in the version control software. | 1 | 5 | | | yes | yes | |
## Abbreviations