Requirements,-Design-and-Approach.md

@@ -79,3 +79,8 @@ Discussions with various Module Owners and CSP is in progress and below requirem
 <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>
+<h2>6. Glossary</h2>
+<p>The glossary provides definitions of all the key business terms used in this document.</p>
+<table> <thead> <th>Term</th> <th>Description</th> </thead> <tbody> <tr> <td></td> <td></td> </tr> <tr> <td></td> <td></td> </tr> </tbody> </table>
+<h2>7. Risks and Issues</h2>
+<p>Below are key risks and issues specific to the Admin UI Project:</p>
\ No newline at end of file