see GovSpecs Value PropositionPreview

The above mentioned value propositions are generated by the working groups who derive technical specifications from business requirements:

1. Exemplary use cases/government services Use Cases/E-ServicesPreview

2. Organisational realities in governments Organisational RequirementsPreview (resulting in e.g. distributed system, see IM BB; Tenant-Function, see CMS BB)

3. Openness to common policies (e.g. EU or Indian ID Policies)

   1. Requirements shall not aim for compatibility with specific national or regional policies

   2. Instead, requirements shall only describe a state where an implementation compliant to every considered policies is still possible

4. Universal Declaration of Human Rights and UN Universal Safeguards for Inclusive Digital Public Infrastructure

The commonalities (or lowest common denominator) of these business dimensions shall be taken.

These common business requirements inform the 1) technical requirements and 2) its requirement status/priority:

• REQUIRED = Minimum Viable Product (can serve citizens with the minimal functionalities)

• RECOMMENDED = Recommended functional scope

The above mentioned value propositions are only valid with actual software applications fulfilling the functional scope of Building Blocks. In addition, the value propositions are improved by software applications not fulfilling the functional scope but by being ready for integration.

1. Building Block Software Software Compliance ConceptPreview

2. Integration-ready software (plan to introduce in 2026)

The affiliation to one of the categories above is measured in GovStack as “compliance”. For definition of the term, see https://pubs.opengroup.org/togaf-standard/ea-capability-and-governance/chap06.html

For Building Block software, the compliance is measured against the individually listed requirements and its priority/status. The REQUIRED scope of a Building Block Specification MUST at least be fulfilled by 2 different software applications on the market.

For integration-ready software (TBD in 2026), the compliance is measured against the cross-functional requirements. These are software components which are not matching the REQUIRED scope of Building Blocks. Often times, they are sector-specific (monolithic) software components for which the software providers would like to state a readiness to be integrated on the edges of a GovStack architecture.

Version History