[Concept] Creation and Evaluation for Multi-Issuer Enablement in SSI Issuance Flow

[jjeroch]

This feature was created by the network service committee to ensure that the scope is planned for 24.08.

Description: The objective of this ticket is to design and evaluate the necessary changes in the Self-Sovereign Identity (SSI) issuance flow to support multiple issuers within the dataspace. The new process must prioritize a customer-centric approach, ensuring that the user experience is seamless and intuitive. This involves creating a detailed customer journey map that outlines each touchpoint a user interacts with during the SSI issuance process, and identifying areas where multiple issuers can be integrated without compromising the user experience.

Acceptance Criteria:

1. Customer Journey Map Creation:

   • Develop a comprehensive customer journey map that illustrates the current SSI issuance process from the customer's perspective.
   • Identify and mark potential touchpoints for the integration of multiple issuers.

2. Concept Development:

   • Propose a conceptual framework that enables the integration of multiple issuers within the SSI issuance flow.
   • Ensure that the concept adheres to the principles of customer-centric design, with a focus on simplicity and usability.

3. Technical Evaluation:

   • Assess the current technical infrastructure to determine the feasibility of integrating multiple issuers.
   • Identify any technical constraints or requirements needed to support the new concept.
   • Prepare architecture committee sync and approval
   • Run through the architecture circle with the preferred solution

4. Impact Assessment:

   • Analyze the potential impact of the new multi-issuer process on existing systems and processes.
   • Develop a change management plan to address any identified impacts.

5. Documentation:

   • Produce detailed documentation of the new concept, including diagrams, flowcharts, and user interface designs.
   • Ensure that the documentation is accessible and understandable to both technical and non-technical stakeholders.

6. Compliance and Security Review:

   • Ensure that the new concept complies with relevant regulations and industry standards.
   • Conduct a security review to ensure that the integration of multiple issuers does not introduce vulnerabilities.

Deliverables:

1. Customer Journey Map
2. Conceptual Framework Document
3. Technical Evaluation Report
4. Impact Assessment Report
5. Documentation Package
6. Compliance and Security Review Report

Timeline:

• The timeline for this project will be established after the initial assessment phase.

Resources Needed:

• Access to current SSI issuance flow documentation and infrastructure
• Customer data and personas for journey mapping
• Strong collab with Network Committee
• Architecture Circle connect
• Expert group EDC connection

Risks and Mitigations:

• Risk: Integration complexity may lead to extended timelines.
  • Mitigation: Allocate additional resources and conduct thorough planning sessions to manage complexity.
• Risk: Resistance from stakeholders due to process changes.
  • Mitigation: Engage with stakeholders early in the process and incorporate their feedback to ensure buy-in.

Additional Notes:

• The customer-centric design must be at the forefront of every decision made during this project.
• Collaboration with UX/UI designers will be crucial in creating an intuitive and user-friendly interface.
• Regular updates and checkpoints with expert groups and committee need to be scheduled to ensure alignment and transparency throughout the project lifecycle.

[stephanbcbauer]

Was presented in the open planning ⇾ its just a concept ⇾ moved to the expert group ⇾ no committer needed for now

[stephanbcbauer]

Hello @jjeroch , @evegufy

Since the feature is a 24.08 feature and the development phase is coming to an end, we need a status on the feature.

• [ ] Currently you are assigned (Responsible) → Is this correct? If not, please assign the correct contact person
• [ ] Please check whether the status (backlog, work in progress ...) is set correctly
• [ ] Please check whether there is an assignment to a committee or expert group (supported-by) to be found on the board
• [ ] Please comment on the current status of the feature
• [ ] Are all SubTasks (issues from other repositories that deal with the feature) linked? → The easiest way is to mention the feature here in the issue (via the ID) so we can see which teams/repositories are involved.

If you need any clarification, please get in touch, thank you very much. Stephan

[jjeroch]

Updated the ticket to the next release. Start by Expert Group needed