Difference between revisions of "MCatalog/Phases of Delivery"
| Line 9: | Line 9: | ||
Document the data types and data content categories in terms of what must be made public and what must be encrypted or stored privately. This will be the foundation for establishing a guideline for implementing the evolving business models as they are to be defined incrementally by [[LKPP]] when new requirements and needs reveal themselves. | Document the data types and data content categories in terms of what must be made public and what must be encrypted or stored privately. This will be the foundation for establishing a guideline for implementing the evolving business models as they are to be defined incrementally by [[LKPP]] when new requirements and needs reveal themselves. | ||
====Technology Demonstration and Deployment Process==== | ====Technology Demonstration and Deployment Process==== | ||
=====TRL 4===== | =====TRL 4===== | ||
Refine and ensure '''all code base''' can switch between public and self-hosted [[Ethereum]]-compatible blockchains, and works on generic web-based human-machine interfaces. | Refine and ensure '''all code base''' can switch between public and self-hosted [[Ethereum]]-compatible blockchains, and works on generic web-based human-machine interfaces. | ||
=====TRL 5===== | =====TRL 5===== | ||
Based on data types defined in [[{{PAGENAME}}#TRL 3|TRL 3]], present repetitive control structures in [[LKPP]]-defined business processes as standardized templates in [[Smart Contract]]s. These standardized templates should be initially written in the programming language [[Solidity]], and they are defined to enhance software reusability and reduce the complexity of business process verification and validation. | Based on data types defined in [[{{PAGENAME}}#TRL 3|TRL 3]], present repetitive control structures in [[LKPP]]-defined business processes as standardized templates in [[Smart Contract]]s. These standardized templates should be initially written in the programming language [[Solidity]], and they are defined to enhance software reusability and reduce the complexity of business process verification and validation. | ||
=====TRL 6===== | =====TRL 6===== | ||
Starting from the beginning of the project, working with [[LKPP]] to define the look and feel of web interfaces, and incorporate UI/UX designers to create an adequate user experience that matches the expectation of stakeholders. The UI/UX code base will incrementally converge with the [[Smart Contract]]s that are being developed in parallel, many design decisions will affect the code integration efforts and influence data service deployment processes. | |||
====Technology Demonstration and Deployment Process==== | |||
=====TRL 7===== | |||
Refine and ensure '''all code base''' can switch between public and self-hosted [[Ethereum]]-compatible blockchains, and works on generic web-based human-machine interfaces. | |||
=====TRL 8===== | |||
Based on data types defined in [[{{PAGENAME}}#TRL 3|TRL 3]], present repetitive control structures in [[LKPP]]-defined business processes as standardized templates in [[Smart Contract]]s. These standardized templates should be initially written in the programming language [[Solidity]], and they are defined to enhance software reusability and reduce the complexity of business process verification and validation. | |||
=====TRL 9===== | |||
Starting from the beginning of the project, working with [[LKPP]] to define the look and feel of web interfaces, and incorporate UI/UX designers to create an adequate user experience that matches the expectation of stakeholders. The UI/UX code base will incrementally converge with the [[Smart Contract]]s that are being developed in parallel, and the testing and deployment process will start at this stage. | |||
Revision as of 16:01, 5 June 2022
Phases of delivery/Technology Readiness Levels(TRLs)
Web-based Smart Contract Demonstration
The first three levels of TRL will 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:
TRL 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.
TRL 2
Demonstrate how each Programmable Account can ensure transparency and non-corruptibility with respect to the security model of blockchain-based Smart Contracts.
TRL 3
Document the data types and data content categories in terms of what must be made public and what must be encrypted or stored privately. This will be the foundation for establishing a guideline for implementing the evolving business models as they are to be defined incrementally by LKPP when new requirements and needs reveal themselves.
Technology Demonstration and Deployment Process
TRL 4
Refine and ensure all code base can switch between public and self-hosted Ethereum-compatible blockchains, and works on generic web-based human-machine interfaces.
TRL 5
Based on data types defined in TRL 3, present repetitive control structures in LKPP-defined business processes as standardized templates in Smart Contracts. These standardized templates should be initially written in the programming language Solidity, and they are defined to enhance software reusability and reduce the complexity of business process verification and validation.
TRL 6
Starting from the beginning of the project, working with LKPP to define the look and feel of web interfaces, and incorporate UI/UX designers to create an adequate user experience that matches the expectation of stakeholders. The UI/UX code base will incrementally converge with the Smart Contracts that are being developed in parallel, many design decisions will affect the code integration efforts and influence data service deployment processes.
Technology Demonstration and Deployment Process
TRL 7
Refine and ensure all code base can switch between public and self-hosted Ethereum-compatible blockchains, and works on generic web-based human-machine interfaces.
TRL 8
Based on data types defined in TRL 3, present repetitive control structures in LKPP-defined business processes as standardized templates in Smart Contracts. These standardized templates should be initially written in the programming language Solidity, and they are defined to enhance software reusability and reduce the complexity of business process verification and validation.
TRL 9
Starting from the beginning of the project, working with LKPP to define the look and feel of web interfaces, and incorporate UI/UX designers to create an adequate user experience that matches the expectation of stakeholders. The UI/UX code base will incrementally converge with the Smart Contracts that are being developed in parallel, and the testing and deployment process will start at this stage.