fearlesssolutions / icts Goto Github PK

These personas can be very simple, mostly character-driven. They will also be redesigned with new information.

📜Acceptance Criteria

• Navigation
• Header/Footer
• Branding
• Baseline Styles
• Component Library (USWDS Customization)

🤔Assumptions

• Working off of the current product requirements document
• This will be a responsive web app
• This will use USWDS components and style

🐤Dependencies

• Approval from ICTS stakeholders and the Fearless team
• Initial approval of #52

After "Register" button is pressed on Login page, app navigates to registration page to fill out needed info.

Acceptance criteria:

• Customer Name
• Address
• Phone number
• POC name
• Email
• other needed info?

Mural for work Technical Solution Diagrams: https://app.mural.co/t/playground6620/m/playground6620/1675636349137/9867daacfc39af75f93ba2a072e1949ab5921e37?sender=u814d83b371f79b4624892743

As DevOps engineer I want to create API app container configuration on Azure so that API container app instance can be launched on Azure app configuration.
I know this is done when:

• API container app instance is deployed on Azure Apps configuration
• API app is up and running and can be accessed on healthcheck URL

Setup ICTS API github repository in Fearless github space and create maven based spring boot project.

Using the design technique of Crazy 8s, @afknot and @SelaLewis are going to illustrate two user flows:

• When the company receives a notice from Commerce to apply for exemption or extension and receives a link to the portal.
• Once the application is submitted, what the adjudicator needs to make a decision about the application.

Dependencies: @icts #13-Requirements Gathering, #22 User management page - UI

We've chosen standard practice naming conventions for various folder/file names pertaining to react components and services.

We need to add these directories to the icts-ui repo.

Add dependencies and example test for cypress and react-testing-library.

Decided on using Cypress for both E2E testing and Component testing.

https://miro.com/app/board/uXjVPi9DG0k=/

Link to issue: #10

Link to PR: https://github.com/FearlessSolutions/icts-ui/pull/2

Completion of an epic must meet the following criteria:

• All In Scope Items completed
• 508 Compliance
• Mobile Responsive
• Usage Analytics Logging
• Security Compliant
• Multi-Browser Support - What browsers and versions do we need for internal users?
• Automatic/Smoke/Regression Testing - front end is covered, need a plan for API (may need to accept as technical debt, likely postman)
• Release Planning
• PO Approves of Epic at Demo
• Project Manager approves of Epic at Demo
• Plain Language Used
• Content Supplied by PO
• Change Request Form filled out and approved (Prod)

Add endpoint for Exemptions with the following functionalities:

• add an exemption
• get all exemptions
• get an exemption by ID
• get exemptions by status

Need to dockerize front-end to deploy to these environments:

• dev
• test
• prod

Link to issues: #9
https://github.com/FearlessSolutions/icts-ui/tree/feature/registration-page-gb

As a DevOps Engineer I want to create Key Vault with parameters for application container so that run environment variables are available at run time.
I know this is done when:

• Key vault is created in Fearless Azure environment
• Key vault have parameters stored in it

Initially spin up with mock data for testing existing and new frontend components

AuthService functionality:

• register user
• login user
• logout user
• get current user

Link to issue: #12

This should be done before the dashboard

As an ICTS business stakeholder, I want to limit the view of different personas/roles so that users can easily and more focused/effectively do their jobs.

Given I am an adjudicator role in the application, when I log in successfully, then I must be able to take the following actions:

• View a list of all completed submissions
• Be able to view details of successfully completed submission

Given I am a submitter role in the application, when I log in successfully, then I must be able to take the following actions:

• Create a new submission
• Save a new submission as a draft
• View details Draft submission (only if they're the initial submitter)
• Complete draft submissions (only if they're the initial submitter)
• View a list of all submissions added by my company
• Be able to view details of each successfully completed submission

Given I am a system admin role in the application, when I log in successfully, then I must be able to take the following actions:

• View a user management dashboard
• Change/update/remove roles for all users
• Add new users to the application
• View a list of all completed submissions
• Be able to view details of successfully completed submission

Link to issue: #11

📜Acceptance Criteria

• Registration flow
• Login flow
• Password reset flow
• Exception request submission flow
• FAQs
• Rule information screen
• Review and Sign Off from Dev/Design
• Review and Sign Off from BIS
• Review and Sign Off from ICTS Stakeholder

🤔Assumptions

• Working off of the current product requirements document

🐤Dependencies

• Hearing back about data capture requirements from ICTS stakeholders

Evan wants to include a persona of a foreign party. This will be completed by EOD 02/27. Additional features to consider this persona will be post-minimal viable product.

Link to Issue: Login Page #1

Link to PR: https://github.com/FearlessSolutions/icts-ui/pull/1

Barebones --> link to disclosure submission and link to internal user login

Home page now:

As a Team Fearless Team member, I need detailed requirements for the ICTS extension/exemption intake system so that I can quickly and easily creates our MVP.

Given I am on the ICTS PDR, when I got to the Key Decisions Sections, then I must be able to see the answer to the following questions:

1. Are there parts of the exemption process that require paperwork? Where and when does that handoff happen?
2. What are the specific ICTS impacted? How many imports do we anticipate needing exemptions for? Is it solely the ones from the ICTS supply chain document?
3. Are export companies the same as import companies? Will we be able to use any of the export discoveries for ICTS?
4. Do submitters need the ability to see their documents after submission?
5. Do submitters need the ability to add support documentation after the first submission?
6. Are there any upstream or downstream data dependencies?
7. What occurs during the adjudication of an exemption request? What is the workflow?
8. What information is required to make an exemption request determination
9. What information is required to make an extension request determination
10. Will Help Desk be supporting this effort?
11. Would companies using the ICTS system have BIS CIN or another unique identification number? If not, how will the company be uniquely identifiable
12. Will users be uploading files of any sort or will only be submitting online forms?
13. Will BIS Azure cloud be used for this project? Who will be managing the cloud etc.? (Simon computing? Or internal resources or Fearless).
14. What information is required to be published on the BIS website?
15. What information is required for the submission accepted notification to
16. What ICTS staff will need access to the product?
17. Does ICTS need to approve the industry users?
18. What’s the difference between exemption requests and extension requests
19. Do ICTS censored products will only be names of products or include version numbers too?
20. Does the list of subpoenaed companies list that ICTS has include company email and/or CIN?
21. Are these companies uploading lists of all employees that have this software installed?
22. Are there any cases where adjudication can be automatically approved without human intervention?
23. What are the reporting requirements? What kind of data does ICTS need to see?
24. Does ICTS want to limit access to the system to only someone who is accessing it within the US?
25. What will be the domain/parent domain name where the application will live? (e.g. icts.gov, exempt.icts.gov, etc)

Expand data models, auth service, and relative mock data for them.

Create a react app with Next.js with TypeScript. Add USWDS.

Create user login data model and service to allow users to be created and login.

📜Acceptance Criteria

• Registration flow - TBD if Sam or Matthew - dependent of Azure
• Login flow
• Password reset flow
• Exemption request review flow - internal

🤔Assumptions

• Working off of the current product requirements document
• This will be a responsive web app
• This will use USWDS components and style

🐤Dependencies

• Approval from ICTS stakeholders, and the Fearless team
• Initial approval of #52

User Story
As someone working on behalf of the offending company submitting exemptions, I worry that I may not have enough time to gather all the information from potentially thousands of customers and clearly label each of them within this submission process. I worry that this will be unadministrable.

Acceptance Criteria
Through usability testing, we want to learn:

• if the welcome screen with a card to begin the exemption requests improves organizing the amount of submissions.
• if "Save and Continue" assures the user their data has been saved.
  -if the user decides to submit another exemption request, will they go back to the welcome screen with the card or will it take them back to the dashboard that show completed exemptions.
  -if the user goes to the dashboard, how helpful is the option edit incomplete exemptions.
  -if the user understands that once an exemption is completed, they cannot go back and change it.

After the "Forgot Password" button on the Login page is pressed, takes user to page to enter email

Acceptance criteria:

• Input field for email address to reset password with
• "Reset Password" button

As DevOps engineer I want to create Azure App configuration for ICTS API app so that API app can be deployed on Fearless Azure.
I know this is done when:

• API app configuration created on Azure

Two ways we could do this (in my brain):

• Page with navigation to separate pages for filing an Exemption or Extension
• One page with selections for which type of disclosure you want to submit that loads a component/modal/etc to input data for that submission

Create login page for external/internal users

Acceptance Criteria:

• Input field for email
• Input field for password
• "Login" button
• "Forgot Password" button/link
• "Register" button/link