What are the key milestones you need to achieve in order to complete your project successfully?
Milestone 1: Planning, architecture and design documents for the new features and integrations.
Milestone Outputs:
In this first milestone we will produce and deliver the following:
- The architecture design of the secure extension integration with Switchchord.
- UI: we will provide a technical design of the UI components as it should be developed. It will include a list of features and functionalities that the UI will provide.
- Flow of operation: we will provide a document and diagram on how users interact with the Cardano enabled KERI secure browser extension.
- Project planning and task allocation: based on items 1 and 2, we will define and plan each individual development and operational task using an Agile methodology and will be published in the GitHub repository issue tracker and project management tool.
Acceptance criteria:
The milestone should be accepted when all deliverables defined above are completed. The goal is to have clearly defined:
- what is going to be developed. That is the architecture design of the system
- how users will interact with Switchchord using the KERI secure browser extension. That is the flow of operation
- how we are going to implement in terms of developer resources allocation. That is the project planning per se
Item 1 and 2 will be more technical, however an overall review should be enough to understand the architecture at a high level. Item 3 is just the detailed planning of task for the next milestones.
Evidence of milestone completion:
- For the first output, a document of the project describing the design of the Switchchord integration with the KERI secure browser extension functionalities.
- For the second one, a document of the project with a flow diagram that explains how interactions with other systems will be handled.
- For the last output, the creation of individual GitHub issues defining each development activity created in the repository and organized in milestones that can be easily tracked.
All the evidence will be provided to the above documents will be provided to the reviewers.
Milestone 2: Development of the <u>Initial Switchcord UI integration</u> with the KERI secure browser extension.
Milestone Outputs:
In this milestones we will be developing changes to the Switchchord webapp to integrate with the KERI secure browser extension based on the design produced in the first milestone. The prototype should allow the user to interact with the KERI secure browser extension features based in the operational flows defined. As a first prototype, the added features shouldn't be considered an MVP.
Acceptance criteria:
The prototype delivered in this milestone should be able to demo at least 70% of the UI features defined in milestone 1. As a first prototype, it's not expected to be production ready and running and demoing may require manual procedures. The goal is to validate the initial design and a final product can be delivered a later milestone.
The prototype delivered should be considered as the first iteration of a product, that will be improved towards an MVP in the next milestone.
Evidence of milestone completion:
The full evidence for completeness is the demo of the Switchchord integration of the KERI secure browser extension with corresponding archive. Since this task may require expertise and knowledge of this technology, the evidence will also consist of a video showing and explaining how the prototypes deliver its functionalities.
Milestone 3: Development of <u>ALL prototype UI features</u> needed to connect to the KERI secure browser extension ecosystem.
Milestone Outputs:
In this milestones we will be developing the first working prototype of all of the KERI secure browser extension UI features based on the design produced in the first milestone. The prototype should allow the user to interact with the KERI secure browser extension features based in the operational flows defined. As a prototype, some of the added features will be MVP; more will be added in milestone 4.
Acceptance criteria:
The prototype delivered in this milestone should be able to demo 100% of the UI features defined in milestone 1. As a first prototype, it's not expected to be production ready and running and demoing may require manual procedures. The goal is to validate the initial design and a final product can be delivered a later milestone.
The prototype delivered should be considered as the first iteration of a product, that will be improved towards an MVP in the next milestone.
Evidence of milestone completion:
The full evidence for completeness is the demo of the KERI secure browser extension with corresponding archive. Since this task may require expertise and knowledge of this technology, the evidence will also consist of a video showing and explaining how the prototypes deliver its functionalities.
Milestone 4: Development of authentication and authorization prototype <u>integrations</u> between the UI components in the KERI secure browser extension and the did:webs Switchord identities:
Milestone Outputs:
The goal of this milestones is to deliver a prototype integration of authentication and authorization of the user based on the design of milestone 1 and the prototype delivered in milestone 2 & 3. This step is an iteration process of improvement of the prototype, where the rest the features defined in milestone 1 should be integrated to identify any issues detected so that integration testing can be mostly stable.
Acceptance criteria:
The prototype delivered in this milestone should be able to demo 100% of the UI integrations related to authentication and authorization of a user as defined in milestone 1. As a first prototype, it's not expected to be production ready and running and demoing may require manual procedures. The goal is to validate the initial design and a finalized prototype can be delivered in a later milestone.
The prototype delivered should be considered as the first iteration of a product, that will be improved towards our final concept in the next milestone.
Evidence of milestone completion:
Since this task may require expertise and knowledge of this technology, the evidence will consist of a demo video showing and explaining how the authentication and authorization deliver its functionalities.
Milestone 5: Development of prototype <u>integrations</u> between the Switchchord KERI identities and the RootsID Cardano Super-Watcher funded in Catalyst F11.:
Milestone Outputs:
The goal of this milestones is to deliver a prototype integration that bridges to the Cardano/KERI ecosystem. Based on the design of milestone 1 and the features delivered in milestone 2, 3, and 4. This step is an iteration process of improvement of the other prototype developments and integrations, where the rest the features defined in milestone 1 should be integrated to identify any issues detected so that integration testing can be demonstrated.
Acceptance criteria:
The prototype delivered in this milestone should be able to demo the use of the RootsID Cardano Super-Watcher funded in Catalyst F11 in the Switchchord identifiers. As a first prototype, it's not expected to be production ready and running and demoing may require manual procedures. The goal is to validate the initial design and a finalized prototype can be delivered in a later proposal.
The prototype delivered should be considered as the first iteration of a product, that will be improved towards our final concept in the next milestone.
Evidence of milestone completion:
Since this task may require expertise and knowledge of this technology, the evidence will consist of a video showing and explaining how the feature works with the Cardano/KERI ecosystem.
Final Milestone: Final goals:
Final development deployment of Switchchord prototype features completed.
Presentations of the prototype features to the community and stakeholders
Final Milestone outputs:
A recording of the app being demonstrated to the Cardano, KERI, and vLEI communities.
Final milestone acceptance criteria:
- The Switchchord prototype features platform has been opened to the public
- The community has been briefed on this impressive innovation
Final milestone evidence of milestone completion:
- The URL for the prototype features is available
- A final report including the community meeting recording is provided.