Update Requirements, Design and Approach authored by Sourabh Roy's avatar Sourabh Roy
......@@ -75,4 +75,7 @@ Discussions with various Module Owners and CSP is in progress and below requirem
<ul> <li>User with Owner role and Admin or Creator permission will be able to create a group and can also delete a group</li> <li>User with Owner role and Viewer permission can only view the list of groups and member inside a group</li> <li>Search functionality is also provided to users to easily search a group or user</li> </ul>
<h2>4. Admin Application Deployment Approach</h2>
<p>Deployment approach is yet to be finalized. A few options discussed are as below:</p>
<ol> <li>AWS Elastic Beanstalk/App Service</li> <li>Serverless (NGINX containerized deployment) (preferred)</li> </ol>
\ No newline at end of file
<ol> <li>AWS Elastic Beanstalk/App Service</li> <li>Serverless (NGINX containerized deployment) (preferred)</li> </ol>
<h2>5. Assumptions</h2>
<p>This section defines the assumptions made for the user acceptance process</p>
<ol> <li>The project assumes only UI (frontend development). All API’s are to be provided by the individual module owners</li> <li>Instance specific IDP will be used for authentication and all APIs are expected to validate the roles and access before returning the results</li> <li>This project will not update or create any new API’s or any backend code</li> <li>End deliverable for this project is going to be Angular 9 code which can be deployed to any CSPs</li> </ol>
\ No newline at end of file