Version

Terminology

• “non-bb software” describes software which does not match the functional scope of a Building Block but is nevertheless frequently used in government systems (e.g. a software covering specialized sectoral business processes).

Value Proposition

For software providers, the compliance check enables public advertisement and transparency if and how the software solution is prepared to be integrated into GovStack-based systems.

For governments, the overview of compliant non-BB software enables governments to select software for specific use cases where commonly high-specialized software solutions are used. At the same time it assures governments that an integration is possible.

Integration Compliance Criteria

Integration compliance is evaluated by its possibility to integrate with the four foundational BBs

1. Cross-functional

   1. Software muss fulfill cross-functional architecture requirements.

2. Integration with ID BB

   1. The software must be able to use external authentication mechanisms.

3. Integration with Workflow BB

   1. The software must be able to handle inbound API request coming from a Workflow BB software.

4. Integration with Registry BB

   1. The software must be able to use external data storage applications (outbound API requests as alternative to internal database).

5. Integration with Information Mediator BB

   1. The software must be compatible with security servers of Information Mediator.

6. Deployment

   1. The software must be containerized.

   2. More to be followed once we have defined deployment compliance of the main compliance concept further.