List of framework used for the application used in this scope:
State a list of rules with the rationale for the design when coding the solution.
| Rules | Rationale |
|---|---|
| All binary assets (image file, videos, pdfs, non-code) must be stored in the "/src/assets/". | Simplify to locate the assets used by the application. |
This table summarize the user role permission of the application, if there is any.
| Features \ Roles | Anonymous | Frontend URL | Remarks |
|---|---|---|---|
| Standard Login API | Only accept calls from the Frontend URL | ||
| Reset Password API | Only accept calls from the Frontend URL | ||
| View Object API | Only accept calls from the Frontend URL | ||
| Create Object API | Only accept calls from the Frontend URL | ||
| Update Object API | Only accept calls from the Frontend URL | ||
| Delete Object API | Only accept calls from the Frontend URL |
This is a listing of all the configuration that can be found for the application.
| Description | Location | Remarks |
|---|---|---|
| Indicate the GCP location of project. | /src/environment.ts | |
| Indicate the components routing configuration. | /src/app/app-routing.module.ts | |
In this section, all the technical specification to support will be listed here.
In this section, provide the link or diagram to show the design of the database.
<<To be replaced with a diagram or hyperlink to the diagram>>
If there is a JIRA used for tracking the Issue, simply add in the URL to the project of the JIRA here. Otherwise, track the changes here.
| Ticket # | Description | Link to supporting Documents | Status | On Production | Reporter | Issue Resolver |
|---|---|---|---|---|---|---|
| 0001 | Cannot Login with xxx@solvay.com | Processing | No | |||