Version History
Version | Changes | Authors |
|---|---|---|
v0.1.1 | Role of policies in business requirements changed | |
v0.1 |
Value Propositions
Governments, the priority users of GovSpecs, shall be able to improve the following:
...
Use Cases (e.g. use cases from partner countries or https://govstack.gitbook.io/use-cases )
Common Practice Policies Openness to common policies (e.g. EU or Indian ID Policies)
Business requirements shall not be exclusively towards specific national or regional policies
Instead, business requirements shall only describe the requirements to a point where an implementation compliant to every considered policies is still possible
https://www.un.org/en/about-us/universal-declaration-of-human-rights and https://www.dpi-safeguards.org/
...
REQUIRED = Minimum Viable Product (can serve citizens with the minimal functionalities)
RECOMMENDED = Recommended functional scope
OPTIONAL = (Packages of) requirements which are unique to specific business requirements (which a country might not strive to, e.g. for complying to eIDAS trust level 3)
| Info |
|---|
On policies in business requirements: The effect of policies to technical requirements shall be reduced to a minimum. The compliance to selected policies should be described in additional documents (different name?) and might include also organisational, legal and semantic dimensions. |
To be added with agreements from architecture WG 11.11.2024
...