Differences

This shows you the differences between two versions of the page.

--- reference:system-architecture [2025/09/03 18:35] – runarbe
+++ reference:system-architecture [2025/09/09 22:03] (current) – [7. API layer] runarbe
@@ Line 37: / Line 37: @@
 The business of street addressing is a complex set of interrelated managerial, planning, technical and engineering/civil works tasks that involves a broad range of distinctive end-users. The diagram below provides an overview of all the components that are required for the efficient operation and flow of data in the addressing system.
-{{:wiki:reference:system:addressing-system-integration-architecturev003.png?nolink&5670x3134}}
+{{  :wiki:reference:system:addressing-system-integration-architecturev003_1.png?direct&800x444  }}
 The diagram can be read both bottom up and top down. From the point of view of technical resources, the preferred reading direction is bottom up, for people who find themselves in end-user roles, it is more easily read from top to bottom.
   * [[:reference:system-architecture:realization|A possible realisation of the system architecture as specified in this document]]
 ===== 5. Data models =====
@@ Line 57: / Line 58: @@
   * Documentation for the [[:reference:system-architecture:signage-data-model|sign management data model]] (to be supplied by future appointed vendor)
-==== 5.3 Naming data model ====
+==== 5.3 Name collection data model ====
+  * Documentation for the [[:reference:system-architecture:name-collection-data-model|naming data model]] (to be supplied by existing vendor)
+==== 5.4 Name allocation data model ====
+  * Documentation for the [[:reference:system-architecture:naming-allocation-data-model|naming data model]] (to be supplied by existing vendor)
+==== 5.5 Field verification application data model ====
+  * Documentation for the [[:reference:system-architecture:field-verification-data-model|naming data model]] (to be supplied by existing vendor)
-  * Documentation for the [[:reference:system-architecture:naming-data-model|naming data model]] (to be supplied by existing vendor)
 ===== 6. Data Layer =====
@@ Line 100: / Line 110: @@
   * [[:reference:system-architecture:authentication-api|Authentication API]]
-  * [[:reference:system-architecture:address-editing-and-query-api|Address Editing and Query API]]
+  * [[:reference:system-architecture:address-editing-and-query-api|Address editing API]]
+  * [[:reference:system-architecture:address-integration-api|Address Integration API]] (vendor to be appointed by by competitive tender)
   * [[:reference:system-architecture:naming-api|Naming API]] (to be supplied by existing vendor)
-  * [[:reference:system-architecture:signage-api|Signage API]] (implemenation to be determined through competitive tender)
+  * [[:reference:system-architecture:signage-api|Signage API]] (vendor to be appointed by by competitive tender)
 ===== 8. Application layer =====
@@ Line 108: / Line 120: @@
 Below, you will find technical and functional requirements for the following applications
-  * [[:reference:system-architecture:address-editing-application|Web based data creation and editing client]]
+  * [[:reference:system-architecture:address-editing-application|Address editing application]]
   * [[:reference:system-architecture:street-naming-application|Street naming application]]
   * [[:reference:system-architecture:mobile-field-verification-application|Mobile field verification application]]
@@ Line 115: / Line 127: @@
   * [[:reference:system-architecture:addressing-viewer-and-search-application|Addressing viewer and search application]]
   * [[:reference:system-architecture:addressing-wiki|Addressing WIKI]]
 ===== 9. Infrastructure layer =====