 |
This diagram outlines the process flow of querying software dependencies.
Step 1: The process begins with a user querying the dependency information for a specific software component 'XXX'.
Step 2: The system then requests the DID document of 'XXX' from the DID resolver to discover the address of smart contract SC_XXX.
Step 3: The DID document of 'XXX' is retrieved
Step 4: The query service requests dependency information of XXX from SCXXX. The SCXXX retrieves the addresses of the smart contracts for YYY and ZZZ from its relationship mapping. It then requests and receives dependency information from SCYYY and SCZZZ.
This querying process is recursive; for example, upon receiving a request from SCXXX, SCZZZ requests and compiles dependency information from its direct dependency components AAA and BBB, aggregates this data, and provides its complete dependency information back to SCXXX.
Step 5: SCXXX aggregates the dependency information received from SCYYY and SCZZZ to generate its comprehensive dependency information. This information encompasses not only the direct dependencies of XXX but also all components in a transitive dependency relationship.
Step 6: This comprehensive dependency information of XXX is provided back to the user who initiated the request through the query service.
This dependency information is automatically generated by the blockchain's smart contracts, ensuring tamper-proof data and high trustworthiness.
|
IEEE/ICACT20250067 Slide.12
[Big Slide]