Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page Properties


Project TitleApplying fault-tolerant software patterns to Hyperledger Fabric chaincode
Status

Status
colourBlueGreen
titlein progresscompleted

Difficulty

Status
colourYellow
titleMedium
  


...

The project is expected to primarily focus on the patterns collected in the reference book Hanmer, Robert S.Patterns for fault tolerant software. John Wiley & Sons, 2013. It also serves as a good general introduction to fault-tolerant computing. The scope will be extended towards other academic papers (and existing fault-tolerant computing APIs, as, e.g., SA Forum) as and if justified by the progress.

Learning Objectives

  • Introduction to open source culture and collaboration tools
  • Deep knowledge of the operational principles of Hyperledger Fabric
  • Software engineering techniques of fault tolerant computing

...

WeekPlanStatus
June 6  - June 13Mentee intro with the mentor.
Communicating the details of research obejtivesobjectives.
Discussing the resources.
Complete
June 13  - June 20Litrature Literature review on:
Fault tolerant software patterns.
Fabric's architecture.
Chaincode lifecycle.

Complete
June 20  - June 27Identifying vulnerabalitiesvulnerabilities.
Ientifying Identifying the respective mitigation approaches.
Drafting the intial initial FMEA, icluding including the softare software patterns.
Complete
June 27  - July 4Completing the FMEA:
Differentiating Weakness from Vulnarabilitiesvulnerabilities(CEW, CVE).
Including existing vulnerabilities and prospective vulnarabilitesvulnerabilities.
Report progress for evaluation.
In Progress
July 4 - July 11Completing ressearch research work on:
Background work on formal specification and run time verification of chain code.
TBD
July 11 - July 18Completing research work on:
Runtime monitoring, observers and ordere orderer metrics for chain code.
Report progress for evaluation.
TBD
Evaluation
July 18 - July 25Design I:
Functionalities, architecture and properties.
TBD
July 25 - August 1Design II:
Error detection, analysis of technical requirements.
TBD
August 1 - August 8Design III:
Units of mitigation, system prototype, aaplicability applicability of pattern.
TBD
August 8 - August 15Deployment I:
Chain code Chaincode execution and error detection.
TBD
August 15 - August 22Deployment II:
Chain code Chaincode execution and error detection.
Report progress for evaluation.
TBD
August 22 - August 29Deployment III:
Chain code Chaincode execution and error detection.
TBD
Evaluation
August 29 - September 5Test case I:
Chain code Chaincode execution and error detection.
TBD
September 5 - September 12Test case II:
Chain code Chaincode execution and error detection.
Report progress for evaluation.
TBD
September 12 - September 19Test case III:
Chain code Chaincode execution and error detection.
TBD
September 19 - September 26Error Processing I:
Error handling control flow, rollback , etc.
TBD
September 26 - October 3Error Processing II:
Error handling control flow, roll forward, etc.
Report progress for evaluation
TBD
October 3 - October 10Error Processing III:
Error handling control flow, roll forward, etc.
Report progress for evaluation
TBD
Evaluation
October 10 - October 17Deliverables I:
Completing the technical requirements and modules on applicabality applicability of fault-tolerant patterns.
TBD
October 17 - October 24Deliverables II:
Completing the prototype fault tolerant libraries and patterns.
TBD
October 24 - October 31Documentation I:
Complete documentation of the implementation.
TBD
October 31 - November 7Documentation II:
Complete documentation of the implementation.

TBD
November 7 - November 14Report progress for evaluation.TBD
Evaluation

...