Difference between revisions of "MCatalog/Phases of Delivery"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
===Phases of delivery/[[wikipedia:Technology_readiness_level|Technology Readiness Levels(TRLs)]]=== | ===Phases of delivery/[[wikipedia:Technology_readiness_level|Technology Readiness Levels(TRLs)]]=== | ||
* TRL 1: Web-based Smart Contract Demonstration: Use [[Smart Contract]]s and [[Ethereum]]-based account classification to perform [[LKPP]]-defined product catalog data update and publication business process. This includes the following features: | * TRL 1: Web-based Smart Contract Demonstration: Use [[Smart Contract]]s and [[Ethereum]]-based account classification to perform [[LKPP]]-defined product catalog data update and publication business process. This includes the following features: | ||
1. Demonstrate that each [[Programmable Account]] represents a self-contained [[LKPP]]-specified business process, each business process would involve a set of explicitly defined roles, such as [[buyer]]/[[vendor]]/[[administrator], who are identified by [[Externally Owned Account]]s. | 1. Demonstrate that each [[Programmable Account]] represents a self-contained [[LKPP]]-specified business process, each business process would involve a set of explicitly defined roles, such as [[buyer]]s/[[vendor]]s/[[administrator]]s, who are identified by [[Externally Owned Account]]s. | ||
2. Demonstrate that the code base can easily switch between multiple [[Ethereum]]-compatible blockchains. | 2. Demonstrate that the code base can easily switch between multiple [[Ethereum]]-compatible blockchains. | ||
3. | 3. | ||
* TRL 2: | * TRL 2: |
Revision as of 15:18, 5 June 2022
Phases of delivery/Technology Readiness Levels(TRLs)
- TRL 1: Web-based Smart Contract Demonstration: Use Smart Contracts and Ethereum-based account classification to perform LKPP-defined product catalog data update and publication business process. This includes the following features:
1. Demonstrate that each Programmable Account represents a self-contained LKPP-specified business process, each business process would involve a set of explicitly defined roles, such as buyers/vendors/administrators, who are identified by Externally Owned Accounts. 2. Demonstrate that the code base can easily switch between multiple Ethereum-compatible blockchains. 3.
- TRL 2: