Mijn Overheid Zakelijk
Het model voor Mijn Overheid Zakelijk
Error: 128 |
Warning: 0 |
Info: 0 |
Ignore: 0
Inspections: 618 |
Help
| ERROR |
1. This workspace has no defined scope. It is recommended that the workspace scope is set to "Landscape" or "SoftwareSystem". workspace.scope
|
|
| ERROR |
2. This workspace describes the internal details of 6 software systems. It is recommended that a workspace contains the model, views, and documentation for a single software system only. workspace.scope
|
|
| ERROR |
3. The person "Zakelijke Gebruiker" is missing a description. model.person.description
|
|
| ERROR |
4. The relationship between the person "Zakelijke Gebruiker" and the container "Mijn Overheid Zakelijk.MOZA Frontend" is missing a technology. model.relationship.technology
|
|
| ERROR |
5. The relationship between the person "Zakelijke Gebruiker" and the software system "Mijn Overheid Zakelijk" is missing a technology. model.relationship.technology
|
|
| ERROR |
6. The person "Medewerker bij een Dienstverlener" is missing a description. model.person.description
|
|
| ERROR |
7. The relationship between the person "Medewerker bij een Dienstverlener" and the container "Dienstverlener.Dienstverlener Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
8. The relationship between the person "Medewerker bij een Dienstverlener" and the software system "Dienstverlener" is missing a technology. model.relationship.technology
|
|
| ERROR |
9. The software system "Dienstverlener" has containers, but is missing documentation. model.softwaresystem.documentation
|
|
| ERROR |
10. The software system "Dienstverlener" has containers, but is missing decisions. model.softwaresystem.decisions
|
|
| ERROR |
11. The relationship between the software system "Dienstverlener" and the software system "BBO" is missing a technology. model.relationship.technology
|
|
| ERROR |
12. The relationship between the software system "Dienstverlener" and the container "Notificatiedienst.Notificatie Management Component" is missing a technology. model.relationship.technology
|
|
| ERROR |
13. The relationship between the software system "Dienstverlener" and the software system "Notificatiedienst" is missing a technology. model.relationship.technology
|
|
| ERROR |
14. The relationship between the software system "Dienstverlener" and the component "Notificatiedienst.Notificatie Management Component.Centrale-notificatie-controller" is missing a technology. model.relationship.technology
|
|
| ERROR |
15. The relationship between the software system "Dienstverlener" and the component "Notificatiedienst.Notificatie Management Component.Decentrale-notificatie-controller" is missing a technology. model.relationship.technology
|
|
| ERROR |
16. The container "Dienstverlener.Output management component" is missing a technology. model.container.technology
|
|
| ERROR |
17. The relationship between the container "Dienstverlener.Output management component" and the container "Dienstverlener.Output management component Database" is missing a technology. model.relationship.technology
|
|
| ERROR |
18. The relationship between the container "Dienstverlener.Output management component" and the container "Dienstverlener.Profiel-opslag" is missing a technology. model.relationship.technology
|
|
| ERROR |
19. The relationship between the container "Dienstverlener.Output management component" and the software system "BBO" is missing a technology. model.relationship.technology
|
|
| ERROR |
20. The relationship between the container "Dienstverlener.Output management component" and the container "Notificatiedienst.Notificatie Management Component" is missing a technology. model.relationship.technology
|
|
| ERROR |
21. The relationship between the container "Dienstverlener.Output management component" and the software system "Notificatiedienst" is missing a technology. model.relationship.technology
|
|
| ERROR |
22. The relationship between the container "Dienstverlener.Output management component" and the component "Notificatiedienst.Notificatie Management Component.Decentrale-notificatie-controller" is missing a technology. model.relationship.technology
|
|
| ERROR |
23. The container "Dienstverlener.Dienstverlener Service" is missing a technology. model.container.technology
|
|
| ERROR |
24. The relationship between the container "Dienstverlener.Dienstverlener Service" and the container "Dienstverlener.Output management component" is missing a technology. model.relationship.technology
|
|
| ERROR |
25. The relationship between the container "Dienstverlener.Dienstverlener Service" and the container "Notificatiedienst.Notificatie Management Component" is missing a technology. model.relationship.technology
|
|
| ERROR |
26. The relationship between the container "Dienstverlener.Dienstverlener Service" and the software system "Notificatiedienst" is missing a technology. model.relationship.technology
|
|
| ERROR |
27. The relationship between the container "Dienstverlener.Dienstverlener Service" and the component "Notificatiedienst.Notificatie Management Component.Centrale-notificatie-controller" is missing a technology. model.relationship.technology
|
|
| ERROR |
28. The container "Dienstverlener.Profiel-opslag" is missing a technology. model.container.technology
|
|
| ERROR |
29. The relationship between the software system "BBO" and the container "Notificatiedienst.Notificatie Management Component" is missing a technology. model.relationship.technology
|
|
| ERROR |
30. The relationship between the software system "BBO" and the software system "Notificatiedienst" is missing a technology. model.relationship.technology
|
|
| ERROR |
31. The relationship between the software system "BBO" and the container "Profiel Service.Profiel Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
32. The relationship between the software system "BBO" and the software system "Profiel Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
33. The software system "Notificatiedienst" has containers, but is missing decisions. model.softwaresystem.decisions
|
|
| ERROR |
34. The following views are embedded into documentation for the software system "Notificatiedienst" but do not exist in the workspace: NotificatieServiceDeployment documentation.embeddedview
|
|
| ERROR |
35. The relationship between the software system "Notificatiedienst" and the container "Profiel Service.Profiel Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
36. The relationship between the software system "Notificatiedienst" and the software system "Profiel Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
37. The relationship between the software system "Notificatiedienst" and the software system "Handelsregister" is missing a technology. model.relationship.technology
|
|
| ERROR |
38. The relationship between the software system "Notificatiedienst" and the software system "BRP-API" is missing a technology. model.relationship.technology
|
|
| ERROR |
39. The relationship between the software system "Notificatiedienst" and the person "Zakelijke Gebruiker" is missing a technology. model.relationship.technology
|
|
| ERROR |
40. The container "Notificatiedienst.Notificatie Management Component" is missing a technology. model.container.technology
|
|
| ERROR |
41. The relationship between the container "Notificatiedienst.Notificatie Management Component" and the container "Profiel Service.Profiel Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
42. The relationship between the container "Notificatiedienst.Notificatie Management Component" and the software system "Profiel Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
43. The relationship between the container "Notificatiedienst.Notificatie Management Component" and the container "Notificatiedienst.notificatiedatabase" is missing a technology. model.relationship.technology
|
|
| ERROR |
44. The relationship between the container "Notificatiedienst.Notificatie Management Component" and the software system "Handelsregister" is missing a technology. model.relationship.technology
|
|
| ERROR |
45. The relationship between the container "Notificatiedienst.Notificatie Management Component" and the software system "BRP-API" is missing a technology. model.relationship.technology
|
|
| ERROR |
46. The relationship between the container "Notificatiedienst.Notificatie Management Component" and the container "Notificatiedienst.Contactherstel" is missing a technology. model.relationship.technology
|
|
| ERROR |
47. The relationship between the component "Notificatiedienst.Notificatie Management Component.Centrale-notificatie-controller" and the component "Notificatiedienst.Notificatie Management Component.Notificatie-orchestrator" is missing a technology. model.relationship.technology
|
|
| ERROR |
48. The relationship between the component "Notificatiedienst.Notificatie Management Component.Decentrale-notificatie-controller" and the component "Notificatiedienst.Notificatie Management Component.Notificatie-orchestrator" is missing a technology. model.relationship.technology
|
|
| ERROR |
49. The relationship between the component "Notificatiedienst.Notificatie Management Component.Afleverstatus-callback" and the component "Notificatiedienst.Notificatie Management Component.Notificatie-orchestrator" is missing a technology. model.relationship.technology
|
|
| ERROR |
50. The relationship between the component "Notificatiedienst.Notificatie Management Component.Notificatie-orchestrator" and the component "Notificatiedienst.Notificatie Management Component.Profielservice-adapter" is missing a technology. model.relationship.technology
|
|
| ERROR |
51. The relationship between the component "Notificatiedienst.Notificatie Management Component.Notificatie-orchestrator" and the container "Notificatiedienst.notificatiedatabase" is missing a technology. model.relationship.technology
|
|
| ERROR |
52. The relationship between the component "Notificatiedienst.Notificatie Management Component.Notificatie-orchestrator" and the component "Notificatiedienst.Notificatie Management Component.Verzendadapter" is missing a technology. model.relationship.technology
|
|
| ERROR |
53. The relationship between the component "Notificatiedienst.Notificatie Management Component.Notificatie-orchestrator" and the component "Notificatiedienst.Notificatie Management Component.Contactherstel-coordinator" is missing a technology. model.relationship.technology
|
|
| ERROR |
54. The relationship between the component "Notificatiedienst.Notificatie Management Component.Notificatie-orchestrator" and the component "Notificatiedienst.Notificatie Management Component.Notificatiestatus-callback-adapter" is missing a technology. model.relationship.technology
|
|
| ERROR |
55. The relationship between the component "Notificatiedienst.Notificatie Management Component.Profielservice-adapter" and the container "Profiel Service.Profiel Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
56. The relationship between the component "Notificatiedienst.Notificatie Management Component.Profielservice-adapter" and the software system "Profiel Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
57. The relationship between the component "Notificatiedienst.Notificatie Management Component.Adres-adapter" and the software system "Handelsregister" is missing a technology. model.relationship.technology
|
|
| ERROR |
58. The relationship between the component "Notificatiedienst.Notificatie Management Component.Adres-adapter" and the software system "BRP-API" is missing a technology. model.relationship.technology
|
|
| ERROR |
59. The relationship between the component "Notificatiedienst.Notificatie Management Component.Contactherstel-coordinator" and the component "Notificatiedienst.Notificatie Management Component.Adres-adapter" is missing a technology. model.relationship.technology
|
|
| ERROR |
60. The relationship between the component "Notificatiedienst.Notificatie Management Component.Contactherstel-coordinator" and the container "Notificatiedienst.Contactherstel" is missing a technology. model.relationship.technology
|
|
| ERROR |
61. The container "Notificatiedienst.NotifyNL" is missing a technology. model.container.technology
|
|
| ERROR |
62. The relationship between the container "Notificatiedienst.NotifyNL" and the container "Notificatiedienst.Notificatie Management Component" is missing a technology. model.relationship.technology
|
|
| ERROR |
63. The relationship between the container "Notificatiedienst.NotifyNL" and the person "Zakelijke Gebruiker" is missing a technology. model.relationship.technology
|
|
| ERROR |
64. The relationship between the container "Notificatiedienst.NotifyNL" and the component "Notificatiedienst.Notificatie Management Component.Afleverstatus-callback" is missing a technology. model.relationship.technology
|
|
| ERROR |
65. The container "Notificatiedienst.Contactherstel" is missing a technology. model.container.technology
|
|
| ERROR |
66. The relationship between the container "Notificatiedienst.Contactherstel" and the container "Notificatiedienst.Printstraat" is missing a technology. model.relationship.technology
|
|
| ERROR |
67. The container "Notificatiedienst.Printstraat" is missing a technology. model.container.technology
|
|
| ERROR |
68. The relationship between the container "Notificatiedienst.Printstraat" and the person "Zakelijke Gebruiker" is missing a technology. model.relationship.technology
|
|
| ERROR |
69. The software system "Mijn Overheid Zakelijk" has containers, but is missing documentation. model.softwaresystem.documentation
|
|
| ERROR |
70. The software system "Mijn Overheid Zakelijk" has containers, but is missing decisions. model.softwaresystem.decisions
|
|
| ERROR |
71. The relationship between the software system "Mijn Overheid Zakelijk" and the container "Profiel Service.Profiel Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
72. The relationship between the software system "Mijn Overheid Zakelijk" and the software system "Profiel Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
73. The relationship between the software system "Mijn Overheid Zakelijk" and the software system "Handelsregister" is missing a technology. model.relationship.technology
|
|
| ERROR |
74. The relationship between the software system "Mijn Overheid Zakelijk" and the software system "Organisatiesregister" is missing a technology. model.relationship.technology
|
|
| ERROR |
75. The relationship between the software system "Mijn Overheid Zakelijk" and the container "Dienstverlener.Output management component" is missing a technology. model.relationship.technology
|
|
| ERROR |
76. The relationship between the software system "Mijn Overheid Zakelijk" and the software system "Dienstverlener" is missing a technology. model.relationship.technology
|
|
| ERROR |
77. The relationship between the container "Mijn Overheid Zakelijk.MOZA Frontend" and the container "Mijn Overheid Zakelijk.MOZA Backend" is missing a technology. model.relationship.technology
|
|
| ERROR |
78. The relationship between the container "Mijn Overheid Zakelijk.MOZA Backend" and the container "Profiel Service.Profiel Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
79. The relationship between the container "Mijn Overheid Zakelijk.MOZA Backend" and the software system "Profiel Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
80. The relationship between the container "Mijn Overheid Zakelijk.MOZA Backend" and the software system "Handelsregister" is missing a technology. model.relationship.technology
|
|
| ERROR |
81. The relationship between the container "Mijn Overheid Zakelijk.MOZA Backend" and the software system "Organisatiesregister" is missing a technology. model.relationship.technology
|
|
| ERROR |
82. The relationship between the container "Mijn Overheid Zakelijk.MOZA Backend" and the container "Dienstverlener.Output management component" is missing a technology. model.relationship.technology
|
|
| ERROR |
83. The relationship between the container "Mijn Overheid Zakelijk.MOZA Backend" and the software system "Dienstverlener" is missing a technology. model.relationship.technology
|
|
| ERROR |
84. The software system "Profiel Service" has containers, but is missing decisions. model.softwaresystem.decisions
|
|
| ERROR |
85. The relationship between the software system "Profiel Service" and the container "Verificatie Service.Verificatie Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
86. The relationship between the software system "Profiel Service" and the software system "Verificatie Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
87. The relationship between the container "Profiel Service.Profiel Service" and the container "Profiel Service.Profiel service Database" is missing a technology. model.relationship.technology
|
|
| ERROR |
88. The relationship between the container "Profiel Service.Profiel Service" and the container "Verificatie Service.Verificatie Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
89. The relationship between the container "Profiel Service.Profiel Service" and the software system "Verificatie Service" is missing a technology. model.relationship.technology
|
|
| ERROR |
90. The software system "IAM Gateway" has containers, but is missing decisions. model.softwaresystem.decisions
|
|
| ERROR |
91. The container named "IAM Service" is not included on any views - add it to a view. model.element.noview
|
|
| ERROR |
92. The relationship between the container "IAM Gateway.IAM Service" and the container "IAM Gateway.IAM Database" is missing a technology. model.relationship.technology
|
|
| ERROR |
93. The container named "IAM Database" is not included on any views - add it to a view. model.element.noview
|
|
| ERROR |
94. The software system "Verificatie Service" has containers, but is missing decisions. model.softwaresystem.decisions
|
|
| ERROR |
95. The relationship between the software system "Verificatie Service" and the container "Notificatiedienst.NotifyNL" is missing a technology. model.relationship.technology
|
|
| ERROR |
96. The relationship between the software system "Verificatie Service" and the software system "Notificatiedienst" is missing a technology. model.relationship.technology
|
|
| ERROR |
97. The relationship between the container "Verificatie Service.Verificatie Service" and the container "Verificatie Service.Verificatie Service Database" is missing a technology. model.relationship.technology
|
|
| ERROR |
98. The relationship between the container "Verificatie Service.Verificatie Service" and the container "Notificatiedienst.NotifyNL" is missing a technology. model.relationship.technology
|
|
| ERROR |
99. The relationship between the container "Verificatie Service.Verificatie Service" and the software system "Notificatiedienst" is missing a technology. model.relationship.technology
|
|
| ERROR |
100. The deployment node "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT" is missing a description. model.deploymentnode.description
|
|
| ERROR |
101. The deployment node "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius" is missing a description. model.deploymentnode.description
|
|
| ERROR |
102. The relationship between the software system "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/BBO[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Profiel Service.Profiel Service[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
103. The relationship between the software system "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/BBO[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatiedienst.Notificatie Management Component[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
104. The relationship between the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatiedienst.NotifyNL[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatiedienst.Notificatie Management Component[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
105. The relationship between the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatiedienst.Notificatie Management Component[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Profiel Service.Profiel Service[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
106. The relationship between the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatiedienst.Notificatie Management Component[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatiedienst.Contactherstel[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
107. The relationship between the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatiedienst.Contactherstel[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatiedienst.Printstraat[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
108. The deployment node "Ontwikkelomgeving/DV-O-ENVIRONMENT" is missing a description. model.deploymentnode.description
|
|
| ERROR |
109. The deployment node "Ontwikkelomgeving/DV-O-ENVIRONMENT/DV" is missing a description. model.deploymentnode.description
|
|
| ERROR |
110. The relationship between the container "Ontwikkelomgeving/DV-O-ENVIRONMENT/DV/Dienstverlener.Output management component[1]" and the software system "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/BBO[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
111. The relationship between the container "Ontwikkelomgeving/DV-O-ENVIRONMENT/DV/Dienstverlener.Output management component[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatiedienst.Notificatie Management Component[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
112. The relationship between the container "Ontwikkelomgeving/DV-O-ENVIRONMENT/DV/Dienstverlener.Dienstverlener Service[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatiedienst.Notificatie Management Component[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
113. The relationship between the container "Ontwikkelomgeving/DV-O-ENVIRONMENT/DV/Dienstverlener.Dienstverlener Service[1]" and the container "Ontwikkelomgeving/DV-O-ENVIRONMENT/DV/Dienstverlener.Output management component[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
114. The deployment node "Ontwikkelomgeving/LOGIUS-MOZ-ONT" is missing a description. model.deploymentnode.description
|
|
| ERROR |
115. The deployment node "Ontwikkelomgeving/LOGIUS-MOZ-ONT/client-zakelijk" is missing a description. model.deploymentnode.description
|
|
| ERROR |
116. The relationship between the container "Ontwikkelomgeving/LOGIUS-MOZ-ONT/client-zakelijk/Mijn Overheid Zakelijk.MOZA Backend[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Profiel Service.Profiel Service[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
117. The relationship between the container "Ontwikkelomgeving/LOGIUS-MOZ-ONT/client-zakelijk/Mijn Overheid Zakelijk.MOZA Backend[1]" and the container "Ontwikkelomgeving/DV-O-ENVIRONMENT/DV/Dienstverlener.Output management component[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
118. The deployment node "Ontwikkelomgeving/LOGIUS-MOZ-ONT/iam-deployment" is missing a description. model.deploymentnode.description
|
|
| ERROR |
119. The container named "IAM Service" is not included on any views - add it to a view. model.element.noview
|
|
| ERROR |
120. The relationship between the container "Ontwikkelomgeving/LOGIUS-MOZ-ONT/iam-deployment/IAM Gateway.IAM Service[1]" and the container "Ontwikkelomgeving/LOGIUS-MOZ-ONT/iam-deployment/IAM Gateway.IAM Database[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
121. The container named "IAM Database" is not included on any views - add it to a view. model.element.noview
|
|
| ERROR |
122. The deployment node "Ontwikkelomgeving/eHerkenning-ONT" is missing a description. model.deploymentnode.description
|
|
| ERROR |
123. The deployment node "Ontwikkelomgeving/eHerkenning-ONT/eHerkenning-deployment" is missing a description. model.deploymentnode.description
|
|
| ERROR |
124. The deployment node "Profielservicedeployment/LOGIUS-O-ENVIRONMENT" is missing a description. model.deploymentnode.description
|
|
| ERROR |
125. The deployment node "Profielservicedeployment/LOGIUS-O-ENVIRONMENT/Logius" is missing a description. model.deploymentnode.description
|
|
| ERROR |
126. The relationship between the container "Profielservicedeployment/LOGIUS-O-ENVIRONMENT/Logius/Profiel Service.Profiel Service[1]" and the container "Profielservicedeployment/LOGIUS-O-ENVIRONMENT/Logius/Profiel Service.Profiel service Database[1]" is missing a technology. model.relationship.technology
|
|
| ERROR |
127. System context views exist for 6 software systems. It is recommended that a workspace includes system context views for a single software system only. workspace.scope
|
|
| ERROR |
128. Container views exist for 5 software systems. It is recommended that a workspace includes container views for a single software system only. workspace.scope
|
|