Mijn Overheid Zakelijk
Het model voor Mijn Overheid Zakelijk
Error: 101 |
Warning: 0 |
Info: 0 |
Ignore: 0
Inspections: 466 |
Help
|
1. This workspace has no defined scope. It is recommended that the workspace scope is set to "Landscape" or "SoftwareSystem". workspace.scope
|
||
|
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
|
||
|
3. The person "Zakelijke Gebruiker" is missing a description. model.person.description
|
||
|
4. The relationship between the person "Zakelijke Gebruiker" and the container "Mijn Overheid Zakelijk.MOZA Frontend" is missing a technology. model.relationship.technology
|
||
|
5. The relationship between the person "Zakelijke Gebruiker" and the software system "Mijn Overheid Zakelijk" is missing a technology. model.relationship.technology
|
||
|
6. The person "Medewerker bij een Dienstverlener" is missing a description. model.person.description
|
||
|
7. The relationship between the person "Medewerker bij een Dienstverlener" and the container "Dienstverlener.Dienstverlener Service" is missing a technology. model.relationship.technology
|
||
|
8. The relationship between the person "Medewerker bij een Dienstverlener" and the software system "Dienstverlener" is missing a technology. model.relationship.technology
|
||
|
9. The software system "Dienstverlener" has containers, but is missing documentation. model.softwaresystem.documentation
|
||
|
10. The software system "Dienstverlener" has containers, but is missing decisions. model.softwaresystem.decisions
|
||
|
11. The relationship between the software system "Dienstverlener" and the container "Notificatie service.NotifyNL" is missing a technology. model.relationship.technology
|
||
|
12. The relationship between the software system "Dienstverlener" and the software system "Notificatie service" is missing a technology. model.relationship.technology
|
||
|
13. The relationship between the software system "Dienstverlener" and the container "Profiel Service.Profiel Service" is missing a technology. model.relationship.technology
|
||
|
14. The relationship between the software system "Dienstverlener" and the software system "Profiel Service" is missing a technology. model.relationship.technology
|
||
|
15. The relationship between the software system "Dienstverlener" and the software system "BBO" is missing a technology. model.relationship.technology
|
||
|
16. The relationship between the software system "Dienstverlener" and the container "Notificatie service.Kennisgeving service" is missing a technology. model.relationship.technology
|
||
|
17. The container "Dienstverlener.Output management component" is missing a technology. model.container.technology
|
||
|
18. The relationship between the container "Dienstverlener.Output management component" and the container "Notificatie service.NotifyNL" is missing a technology. model.relationship.technology
|
||
|
19. The relationship between the container "Dienstverlener.Output management component" and the software system "Notificatie service" is missing a technology. model.relationship.technology
|
||
|
20. The relationship between the container "Dienstverlener.Output management component" and the container "Profiel Service.Profiel Service" is missing a technology. model.relationship.technology
|
||
|
21. The relationship between the container "Dienstverlener.Output management component" and the software system "Profiel Service" is missing a technology. model.relationship.technology
|
||
|
22. The relationship between the container "Dienstverlener.Output management component" and the container "Dienstverlener.Output management component Database" is missing a technology. model.relationship.technology
|
||
|
23. The relationship between the container "Dienstverlener.Output management component" and the software system "BBO" is missing a technology. model.relationship.technology
|
||
|
24. The relationship between the container "Dienstverlener.Output management component" and the container "Notificatie service.Kennisgeving service" is missing a technology. model.relationship.technology
|
||
|
25. The container "Dienstverlener.Dienstverlener Service" is missing a technology. model.container.technology
|
||
|
26. The relationship between the container "Dienstverlener.Dienstverlener Service" and the container "Notificatie service.NotifyNL" is missing a technology. model.relationship.technology
|
||
|
27. The relationship between the container "Dienstverlener.Dienstverlener Service" and the software system "Notificatie service" is missing a technology. model.relationship.technology
|
||
|
28. The relationship between the container "Dienstverlener.Dienstverlener Service" and the container "Dienstverlener.Output management component" is missing a technology. model.relationship.technology
|
||
|
29. The relationship between the software system "BBO" and the container "Notificatie service.Kennisgeving service" is missing a technology. model.relationship.technology
|
||
|
30. The relationship between the software system "BBO" and the software system "Notificatie service" is missing a technology. model.relationship.technology
|
||
|
31. The relationship between the software system "BBO" and the container "Profiel Service.Profiel Service" is missing a technology. model.relationship.technology
|
||
|
32. The relationship between the software system "BBO" and the software system "Profiel Service" is missing a technology. model.relationship.technology
|
||
|
33. The software system "Notificatie service" has containers, but is missing decisions. model.softwaresystem.decisions
|
||
|
34. The following views are embedded into documentation for the software system "Notificatie service" but do not exist in the workspace: NotificatieServiceDeployment documentation.embeddedview
|
||
|
35. The relationship between the software system "Notificatie service" and the software system "Kanaalhersteldienst " is missing a technology. model.relationship.technology
|
||
|
36. The relationship between the software system "Notificatie service" and the software system "Handelsregister" is missing a technology. model.relationship.technology
|
||
|
37. The container "Notificatie service.Kennisgeving service" is missing a technology. model.container.technology
|
||
|
38. The relationship between the container "Notificatie service.Kennisgeving service" and the software system "Kanaalhersteldienst " is missing a technology. model.relationship.technology
|
||
|
39. The relationship between the container "Notificatie service.Kennisgeving service" and the container "Notificatie service.NotifyNL" is missing a technology. model.relationship.technology
|
||
|
40. The relationship between the container "Notificatie service.Kennisgeving service" and the software system "Handelsregister" is missing a technology. model.relationship.technology
|
||
|
41. The container "Notificatie service.NotifyNL" is missing a technology. model.container.technology
|
||
|
42. The software system "Mijn Overheid Zakelijk" has containers, but is missing documentation. model.softwaresystem.documentation
|
||
|
43. The software system "Mijn Overheid Zakelijk" has containers, but is missing decisions. model.softwaresystem.decisions
|
||
|
44. The relationship between the software system "Mijn Overheid Zakelijk" and the container "Profiel Service.Profiel Service" is missing a technology. model.relationship.technology
|
||
|
45. The relationship between the software system "Mijn Overheid Zakelijk" and the software system "Profiel Service" is missing a technology. model.relationship.technology
|
||
|
46. The relationship between the software system "Mijn Overheid Zakelijk" and the software system "Handelsregister" is missing a technology. model.relationship.technology
|
||
|
47. The relationship between the software system "Mijn Overheid Zakelijk" and the software system "Organisatiesregister" is missing a technology. model.relationship.technology
|
||
|
48. The relationship between the software system "Mijn Overheid Zakelijk" and the container "Dienstverlener.Output management component" is missing a technology. model.relationship.technology
|
||
|
49. The relationship between the software system "Mijn Overheid Zakelijk" and the software system "Dienstverlener" is missing a technology. model.relationship.technology
|
||
|
50. 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
|
||
|
51. The relationship between the container "Mijn Overheid Zakelijk.MOZA Backend" and the container "Profiel Service.Profiel Service" is missing a technology. model.relationship.technology
|
||
|
52. The relationship between the container "Mijn Overheid Zakelijk.MOZA Backend" and the software system "Profiel Service" is missing a technology. model.relationship.technology
|
||
|
53. The relationship between the container "Mijn Overheid Zakelijk.MOZA Backend" and the software system "Handelsregister" is missing a technology. model.relationship.technology
|
||
|
54. The relationship between the container "Mijn Overheid Zakelijk.MOZA Backend" and the software system "Organisatiesregister" is missing a technology. model.relationship.technology
|
||
|
55. The relationship between the container "Mijn Overheid Zakelijk.MOZA Backend" and the container "Dienstverlener.Output management component" is missing a technology. model.relationship.technology
|
||
|
56. The relationship between the container "Mijn Overheid Zakelijk.MOZA Backend" and the software system "Dienstverlener" is missing a technology. model.relationship.technology
|
||
|
57. The software system "Profiel Service" has containers, but is missing decisions. model.softwaresystem.decisions
|
||
|
58. The relationship between the software system "Profiel Service" and the container "Verificatie Service.Verificatie Service" is missing a technology. model.relationship.technology
|
||
|
59. The relationship between the software system "Profiel Service" and the software system "Verificatie Service" is missing a technology. model.relationship.technology
|
||
|
60. The relationship between the container "Profiel Service.Profiel Service" and the container "Profiel Service.Profiel service Database" is missing a technology. model.relationship.technology
|
||
|
61. The relationship between the container "Profiel Service.Profiel Service" and the container "Verificatie Service.Verificatie Service" is missing a technology. model.relationship.technology
|
||
|
62. The relationship between the container "Profiel Service.Profiel Service" and the software system "Verificatie Service" is missing a technology. model.relationship.technology
|
||
|
63. The software system "IAM Gateway" has containers, but is missing decisions. model.softwaresystem.decisions
|
||
|
64. The container named "IAM Service" is not included on any views - add it to a view. model.element.noview
|
||
|
65. The relationship between the container "IAM Gateway.IAM Service" and the container "IAM Gateway.IAM Database" is missing a technology. model.relationship.technology
|
||
|
66. The container named "IAM Database" is not included on any views - add it to a view. model.element.noview
|
||
|
67. The software system "Verificatie Service" has containers, but is missing decisions. model.softwaresystem.decisions
|
||
|
68. The relationship between the software system "Verificatie Service" and the container "Notificatie service.NotifyNL" is missing a technology. model.relationship.technology
|
||
|
69. The relationship between the software system "Verificatie Service" and the software system "Notificatie service" is missing a technology. model.relationship.technology
|
||
|
70. The relationship between the container "Verificatie Service.Verificatie Service" and the container "Verificatie Service.Verificatie Service Database" is missing a technology. model.relationship.technology
|
||
|
71. The relationship between the container "Verificatie Service.Verificatie Service" and the container "Notificatie service.NotifyNL" is missing a technology. model.relationship.technology
|
||
|
72. The relationship between the container "Verificatie Service.Verificatie Service" and the software system "Notificatie service" is missing a technology. model.relationship.technology
|
||
|
73. The deployment node "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT" is missing a description. model.deploymentnode.description
|
||
|
74. The deployment node "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius" is missing a description. model.deploymentnode.description
|
||
|
75. 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
|
||
|
76. The relationship between the software system "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/BBO[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatie service.Kennisgeving service[1]" is missing a technology. model.relationship.technology
|
||
|
77. The relationship between the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatie service.Kennisgeving service[1]" and the software system "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Kanaalhersteldienst [1]" is missing a technology. model.relationship.technology
|
||
|
78. The relationship between the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatie service.Kennisgeving service[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatie service.NotifyNL[1]" is missing a technology. model.relationship.technology
|
||
|
79. The deployment node "Ontwikkelomgeving/DV-O-ENVIRONMENT" is missing a description. model.deploymentnode.description
|
||
|
80. The deployment node "Ontwikkelomgeving/DV-O-ENVIRONMENT/DV" is missing a description. model.deploymentnode.description
|
||
|
81. 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
|
||
|
82. The relationship between the container "Ontwikkelomgeving/DV-O-ENVIRONMENT/DV/Dienstverlener.Output management component[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatie service.NotifyNL[1]" is missing a technology. model.relationship.technology
|
||
|
83. The relationship between the container "Ontwikkelomgeving/DV-O-ENVIRONMENT/DV/Dienstverlener.Output management component[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Profiel Service.Profiel Service[1]" is missing a technology. model.relationship.technology
|
||
|
84. The relationship between the container "Ontwikkelomgeving/DV-O-ENVIRONMENT/DV/Dienstverlener.Output management component[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatie service.Kennisgeving service[1]" is missing a technology. model.relationship.technology
|
||
|
85. The relationship between the container "Ontwikkelomgeving/DV-O-ENVIRONMENT/DV/Dienstverlener.Dienstverlener Service[1]" and the container "Ontwikkelomgeving/LOGIUS-O-ENVIRONMENT/Logius/Notificatie service.NotifyNL[1]" is missing a technology. model.relationship.technology
|
||
|
86. 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
|
||
|
87. The deployment node "Ontwikkelomgeving/LOGIUS-MOZ-ONT" is missing a description. model.deploymentnode.description
|
||
|
88. The deployment node "Ontwikkelomgeving/LOGIUS-MOZ-ONT/client-zakelijk" is missing a description. model.deploymentnode.description
|
||
|
89. 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
|
||
|
90. 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
|
||
|
91. The deployment node "Ontwikkelomgeving/LOGIUS-MOZ-ONT/iam-deployment" is missing a description. model.deploymentnode.description
|
||
|
92. The container named "IAM Service" is not included on any views - add it to a view. model.element.noview
|
||
|
93. 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
|
||
|
94. The container named "IAM Database" is not included on any views - add it to a view. model.element.noview
|
||
|
95. The deployment node "Ontwikkelomgeving/eHerkenning-ONT" is missing a description. model.deploymentnode.description
|
||
|
96. The deployment node "Ontwikkelomgeving/eHerkenning-ONT/eHerkenning-deployment" is missing a description. model.deploymentnode.description
|
||
|
97. The deployment node "Profielservicedeployment/LOGIUS-O-ENVIRONMENT" is missing a description. model.deploymentnode.description
|
||
|
98. The deployment node "Profielservicedeployment/LOGIUS-O-ENVIRONMENT/Logius" is missing a description. model.deploymentnode.description
|
||
|
99. 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
|
||
|
100. 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
|
||
|
101. Container views exist for 5 software systems. It is recommended that a workspace includes container views for a single software system only. workspace.scope
|
||

