User Story: Admin User Operations | User Story ID: US-004
Task: Edit User | Task ID: FE-T-004
Role: Frontend Designer
Tech Stack: Angular 10+/ React 16+
Material Design / Bulma / Bootstrap
Key points to remember:
The id (for frontend) mentioned in the SRS document should not be modified at any cost. Failing to do may fail test cases.
Remember to check the screenshots provided in the SRS document. Strictly adhere to id mapping and attribute mapping. Failing to do may fail test cases.
Strictly adhere to the proper project scaffolding (Folder structure), coding conventions, method definitions and return types.
Adhere strictly to the API endpoints given in the SRS document.
Note:
You should navigate to the admin side dashboard to see the list of users.
Application assumptions:
To navigate to the admin side, you can store a user type as admin in the database with a username and password as admin.
Use admin/admin as the username and password to navigate to the admin dashboard.
FrontEnd Task Details:
Task 1: Add Edit User button
Create a button in the DisplayUser component to edit the user details.
The edit button should render the EditUser component.
Task 2: EditUser Component
Create a component called as EditUser which is used to edit the user details.
Task 3: User Service
Create a service that maps the post request to the EditUser component.
Create a mock API called users.json to test your EditUser endpoints.
You can use postman/swagger to test your API.
Refer to the SRS documents for API endpoints.
Task 4: Add Styles
Enhance the design using a material design library or bootstrap.
Content Description: Epic: User Management | Epic ID: E-001 | Sprint: Sprint-1
User Story: Admin User Operations | User Story ID: US-004
Task: Edit User | Task ID: FE-T-004
Role: Frontend Designer
Tech Stack: Angular 10+/ React 16+
Material Design / Bulma / Bootstrap
Key points to remember:
The id (for frontend) mentioned in the SRS document should not be modified at any cost. Failing to do may fail test cases. Remember to check the screenshots provided in the SRS document. Strictly adhere to id mapping and attribute mapping. Failing to do may fail test cases. Strictly adhere to the proper project scaffolding (Folder structure), coding conventions, method definitions and return types. Adhere strictly to the API endpoints given in the SRS document.
Note:
You should navigate to the admin side dashboard to see the list of users.
Application assumptions:
To navigate to the admin side, you can store a user type as admin in the database with a username and password as admin.
Use admin/admin as the username and password to navigate to the admin dashboard.
FrontEnd Task Details:
Task 1: Add Edit User button
Create a button in the DisplayUser component to edit the user details. The edit button should render the EditUser component. Task 2: EditUser Component
Create a component called as EditUser which is used to edit the user details. Task 3: User Service
Create a service that maps the post request to the EditUser component. Create a mock API called users.json to test your EditUser endpoints. You can use postman/swagger to test your API. Refer to the SRS documents for API endpoints. Task 4: Add Styles
Enhance the design using a material design library or bootstrap.