User Story: Admin User Operations | User Story ID: US-004
Task: Edit User Backend API | Task ID: BE-T-004
Role: Backend Developer
Tech Stack: Springboot / .NET WebApi / Node
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 parent 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.
Backend Task Details:
Task 1: User Model
Create a model class as a User. Refer to the parent SRS for the attributes and method definitions.
Task 2: User Controller
This class controls the add/edit/delete/view user operations.
Create a controller called UserController to edit the users. Refer to the parent SRS for the attributes and method definitions API endpoint specification.
Task 3: Postman / Swagger
Use Swagger/ Postman to test your API endpoints. Refer to the API endpoint specifications given in the parent SRS document.
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 Backend API | Task ID: BE-T-004
Role: Backend Developer
Tech Stack: Springboot / .NET WebApi / Node
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 parent 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.
Backend Task Details:
Task 1: User Model
Create a model class as a User. Refer to the parent SRS for the attributes and method definitions. Task 2: User Controller
This class controls the add/edit/delete/view user operations. Create a controller called UserController to edit the users. Refer to the parent SRS for the attributes and method definitions API endpoint specification. Task 3: Postman / Swagger
Use Swagger/ Postman to test your API endpoints. Refer to the API endpoint specifications given in the parent SRS document.