icon picker
Week 3

light
Week 4 plan, feedback and review
Clear sample data
Tasks
0
Functionality
Task name
Responsible member
Status
1
Design Homepage
Define layout requirements and user interface elements.
Karma Phuntsho
CG
chungdu gyeltshen
OB
Om Bikram
Pragadh Shrestha
Sonam Wangmo
Done
2
Create wireframes and obtain stakeholder approval.
Karma Phuntsho
CG
chungdu gyeltshen
Pragadh Shrestha
OB
Om Bikram
Sonam Wangmo
Done
3
Develop responsive design for various screen sizes.
CG
chungdu gyeltshen
OB
Om Bikram
Pragadh Shrestha
Sonam Wangmo
Done
4
Login Function
Implement user authentication logic.
Karma Phuntsho
CG
chungdu gyeltshen
OB
Om Bikram
Pragadh Shrestha
Sonam Wangmo
Done
5
Develop frontend components for login and logout.
Karma Phuntsho
CG
chungdu gyeltshen
OB
Om Bikram
Pragadh Shrestha
Sonam Wangmo
Done
6
Integrate login functionality with the database.
Karma Phuntsho
CG
chungdu gyeltshen
OB
Om Bikram
Pragadh Shrestha
Sonam Wangmo
Done
7
Profile Page
Define user profile data requirements.
Karma Phuntsho
CG
chungdu gyeltshen
OB
Om Bikram
Pragadh Shrestha
Sonam Wangmo
Done
8
Create profile page layout and design.
Karma Phuntsho
CG
chungdu gyeltshen
OB
Om Bikram
Pragadh Shrestha
Sonam Wangmo
Done
9
Implement profile page functionality and user data storage.
Karma Phuntsho
CG
chungdu gyeltshen
OB
Om Bikram
Pragadh Shrestha
Sonam Wangmo
Done
There are no rows in this table
Test Plan 3
0
Functionality
Test Crietria
Member
Status
1
Design Homepage
Consistent branding and visual appeal.
Karma Phuntsho
Done
2
Proper navigation and user-friendly layout.
CG
chungdu gyeltshen
Done
3
Login Function
Successful login with valid credentials.
OB
Om Bikram
Done
4
Appropriate error messages for invalid login attempts.
Sonam Wangmo
Done
5
Profile Page
Display of accurate user information.
Pragadh Shrestha
Done
6
Edit profile details and verify updates are saved.
YC
Yuan Cao
Done
7
Ensure only authorized users can view profile
Karma Phuntsho
Done
8
There are no rows in this table

Iteration 1 feedback

Encountering problems with error messages lacking clarity and informativeness when login attempts fail.
The page does not respond properly in mobile and tablet modes.
The dashboard layout is not only user-friendly but also exceptionally well-organized, simplifying the process of finding the information I require.
Allowing any user to access the admin dashboard without requiring a login should be avoided for security reasons.
Homepage is user friendly and designed exceptionally well
I love the new Profile Page design! It's so easy to customize my profile, and the layout is clean and intuitive.
The Profile Page is fantastic, but I wish there was an option to add more details about my preferences and requirements. It would make property recommendations more accurate.

Iteration 1 Review

During Iteration 2 of the project, the development team learned valuable lessons when working on the login function and the admin dashboard page. These lessons helped improve our understanding and approach to these critical components. Here are the lessons learned:
Homepage Design:
Lesson Learned: During the design of the homepage, the team discovered that users responded positively to a clean and intuitive layout. We found that emphasizing high-quality property images and incorporating a simple navigation structure significantly improved the overall user experience.
Login Functionality:
The team identified that users appreciated a seamless login process. Users were more likely to engage with the platform when they could easily access their accounts without encountering complex authentication procedures.
Secure Sign-out:
Through user feedback and testing, the team recognized the importance of a clear and accessible signout option. Users valued a straightforward way to log out securely and appreciated a system that ensured the protection of their account information.
Profile Page Customization:
The team discovered that users highly valued the ability to customize their profiles. Positive feedback indicated that users appreciated the opportunity to personalize their experience on the platform.
General Lessons
Learned how to implement pair programming
Team collaboration is the key
User Feedback is invaluable
Continuous improvement is essential
Testing and timely delivery is important

Acceptance Test
Test Case: Successful Login
Objective: To verify that users can successfully log in to the application using valid credentials.
Steps:
Navigate to the login page of the application.
Enter valid username and password.
Click on the "Login" button.
Expected Result: User should be redirected to the profile upon successful login.
Test Case: Invalid Credentials
Objective: To ensure that users cannot log in with invalid credentials.
Steps:
Navigate to the login page of the application.
Enter invalid username or password.
Click on the "Login" button.
Expected Result: User should receive an error message indicating that the login attempt was unsuccessful.
Test Case: Logout Functionality
Objective: To verify that users can successfully log out of the application.
Steps:
Navigate to the profile after successful login.
Locate the logout option.
Click on the "Logout" button.
Expected Result: User should be logged out of the application and redirected to the login page.
Acceptance Test for Profile Page:
Test Case: Update Profile Information
Objective: To confirm that users can update their profile information.
Steps:
Navigate to the profile page after successful login.
Locate the section for updating profile information (e.g., name, email, etc.).
Make changes to the desired fields.
Click on the "Save" or "Update" button.
Expected Result: Changes made to the profile information should be saved and reflected accurately in the database.
Test Case: Invalid Data Entry
Objective: To ensure that users cannot save invalid data in the profile page.
Steps:
Navigate to the profile page after successful login.
Attempt to enter invalid data (e.g., invalid email format, exceeding character limit).
Click on the "Save" or "Update" button.
Expected Result: User should receive an error message indicating that the data entry is invalid, and changes should not be saved until valid data is provided.
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.