Let's determine the solution's components and the interactions between them that are required to implement the OBP-based solution. The following diagram depicts the high-level solution architecture:
Solution architecture - high-level
These are the solution's components:
- OBP Dashboard provides an interface for OEU and ORS administrators/operators to perform OBP administration and configuration tasks.
- Different sets of client applications would be needed for each of the stakeholders:
- ORS:
- To create a student entry and insert certificate data for the student on the ledger
- To be able to search student and certificate data
- OEU:
- To be able to search student and certificate data
- To approve/reject students' certificate data
- Student (CV):
- To be able to view their approved certificates
- Generate a token for a certificate verifier to verify their academic credentials stored on an OBP ledger
- Certificate verifier:
- To be able to verify a student's academic credentials using the token generated by the student using the OBP solution
- ORS: