Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Project Deliverables

  • A medium article aggregating the relevant resources and design approach.
  • Architectural design of an IoT system utilizing Hyperledger Indy for identity management of the devices.
  • Architectural design of an IoT system enabling device-2-device interaction in an autonomous fashion.
  • Implementation and testing of the system on a virtual test bed.
  • Implementation and testing of the system in a real environment.
  • Academic Output: a conference/journal paper outlining the proposal of autonomous device to device communication using Hyperledger Indy.

Project Milestones

  • Make literature research, design and confirm system architecture and network configuration for a blockchain solution for IoT  
    • Project kick-off, initial communication, share ideas and project organization.
    • Establish working practices, set communication schedule, agree on outputs/targets and milestones.
    • Perform an analysis based on literature review/online tutorial to consider the systems, architectures and configuration tested in projects and compare these to the working model.
    • Analysis to include the basic concepts on Identity(Hyperledger Indy), Blockchain(Hyperledger Fabric/Plenum), Smart Contracts(Hyperledger Burrow), and Access Control.
    • Final outline system design, architecture and configuration.
    • Finalize the system architecture and produce a design document detailing the design choices and details.
  •  Coding the proposed solution  
    • Trying existing solutions developed for Indy
    • Prepare the development environment.
    • Code the solution.
    • Documenting the process. (optional if we don’t have time)

Testing of the developed system on a virtual test bed  

  • Prepare the testing environment.
  • Perform the test.
  • Documenting the process and results. (optional if we don’t have time)
  • Testing of the developed system in a real test environment.  
    • Prepare the testing environment.
    • Perform the test.
    • Document the process and results.
  • Documentation and final submission  (documentation optional if we don’t have time)  

  • No labels