Implement submission method (Architecture)

[Tom-Davis]

Description

Define the architectural structure of the Digital Dispute from and submission flow.

Pre-Development Tasks (Required for the Colaboration Cycle)

The items below are all required for the Collaboration Cycle Architectural Review step. These are required to be complete 2 days prior to the review.

• Create an Architecture Intent brief using this template.
• Create an Security Checklist as referenced here.
• Fill out the Architecture Intent Meeting Template and store your Architecture Diagrams in the Diagrams folder in the Sensitive Repo.
• Create a user data flow diagram if your application accepts data from a user.

Development Tasks

• API Endpoints are setup.
• A submitter confirmation flow is identified and setup.
• Submissions (Test data can be used) can be sent/confirmed.
• Any FE page development work is complete for the form submission to be initiated.
• The submitter confirmation is sent.

Design and Front End sync on implementation of design

• Required
• Complete
• Not Required

Acceptance criteria

• All tasks for Pre-Development are complete.
• AThe Implimention of the Submission Process is complete.

Testing

• N/A if non development work
• Testing passed and documented in this ticket based off the tasks

Testing procedure:
If additional testing steps or credentials to perform testing are needed list them here

---

Ticket creation

Ticket requirements

Required to be "Ready"

• Description written
• Tasks defined
• Acceptance criteria written
• Testing defined
• Add Labels
• Attach to an Epic
• Estimate Points

[Tom-Davis]

@amponce @digitaldrk @Dr-Pongo @denisecoveyduc here is the ticket with a section dedicated to Collaboration Cycle requirements. I will schedule that for November 12th at 1:30PM ET now with the anticipation that we can complete the first portion of this ticket for that by Nov 8th (allowing for the 2-day review window) in sprint 138 (Nov 6 - Nov 19).