Project: Lost and Found - Status Update

End of Sprint 4

Date: 2024-04-10 - 2024-04-16

Major Project Feature Summary:

Status	Symbol
Connect web application to AWS	Completed ✅
Develop and design the database	Completed ✅
Design the main user interface	Completed ✅
Create a report for a missing Item	Completed ✅
Add details to the missing item report	Completed ✅
Create login page	Completed ✅
Secure Login	Completed ✅
Safeguard Personal Information	Completed ✅
Send summary report to user	Completed ✅
Visual Representation of All Missing Items	Completed ✅
Update item detail	Completed ✅
Search for Missing Item	In progress (95%)
Contact us	Completed ✅
Create the needed test cases/manual	In progress (25%)
Deploy the web application	In progress (75%)

Major Project Feature % completed to date

• Missing item report created.
• Adding details to the missing item report has been created.
• The connection between the front end and back end is in progress.
• Database Created and landing page.
• Login page and backend logic developed.
• Password encryption completed.
• Contact us backend logic is completed

Current Project Status Summary: ✅

• The team was able to complete the following feature this week:

1. The Contact Us page is fully completed and tested. Students can now send quick email requests to the "Lost and Found" team.
2. The ability to update a request is now fully completed.
3. Jashil was able to test the deployment of a basic application. Unfortunately, his account got locked, and it will be unlocked on 4/17/24.
4. The team is creating test cases and reports for the application's features.
5. The team implemented additional security features to prevent unauthorized access.

Team Status Summary:

The team is now in the final process of closing the user stories for sprint 4 this week.

Team Goals for the upcoming week:

• Provide the final presentation
• Complete all the test cases/report
• Deploy the application.

Individual Team Member Status:

• Robert: Completed the Contact Us page. Added security features to prevent access to unauthorized users. Started creating the final presentation.

  Next week: Assist Jashil if needed with the application deployment. Continue working on the final presentation.

• Aayushi: Completed the Update item detail.

  Next week: Will finish testing the Search for Missing Item and will assist Jashil if needed with the application deployment.

• Meet: Started working on the manual test/report

  Next week: Will continue to work on manual test/report.

• Ishan: Started working on the manual test/report

  Next week: Will continue to work on manual test/report.

• Jashil: Was able to deploy a testing application.

  Next week: Currently working on the deployment of our application.

Past week team activities:

• Working group meeting - 04/16/2024
• Working group meeting - 04/09/2024
• Working group meeting - 04/02/2024
• Working group meeting - 03/26/2024
• Working group meeting - 03/18/2024 & 3/19/2024

• The team went over the latest status of the project.

• Working group meeting (ALL) - 03/05/2024

• The team went over the latest status trough zoom and group chat.

• Working group meeting (ALL) - 02/19/2024
• Working group meeting (ALL) - 02/26/2024

• Team Meetings: The team convened multiple times during the week to discuss various ideas and updates on ongoing projects. These meetings likely ensured everyone was on the same page and addressed any concerns or roadblocks.

• Backend Template Discussions: A significant portion of the team's focus was on discussing backend templates for manipulating data and testing purposes. This indicates a focus on refining the backend infrastructure, possibly to enhance efficiency or functionality.

• Work on Landing and Missing Item Pages: The team dedicates effort to working on specific pages, such as the landing page and the missing item page. This suggests attention to user experience and addressing any issues or improvements needed on these pages. Description of activities in the past week, the date, and who was involved

• API Design and implementation (Aayushi & Robert) - 02/27/2024
• Pair programming (Meet & Ishan) - 02/27/2024
• Research on AWS services (Jashil) - 02/26/2024

Team Project Decisions:

3/26/2024 - NNTR 3/19/2024 - NNTR 3/5/2024 - No important decision and/or changes to configurations/architecture was made this week.

Other Comments:

3/5/2024 - N/A

The team's main choice this past week was to select Amazon Web Services (AWS) as the project's cloud infrastructure supplier. The team determined which specific AWS services would best meet the needs of their project after much deliberation and study. Among these services are:

• AWS RDS (Relational Database Service): The team made the decision to manage the project's database using AWS RDS. Managed database services (RDS) make administration duties like patching, backups, and provisioning easier. The team selected RDS in order to take advantage of its scalability and dependability for data management and storage related to their project.

• AWS EC2 (Elastic Compute Cloud): The team decided to use AWS EC2 to host both the frontend and backend components of their application. Because EC2 offers resizable computational capacity in the cloud, the team may adjust the infrastructure's size in response to demand. The group can select the instance kinds, operating systems, and configurations for each virtual server using EC2.

• AWS S3 (Simple Storage Service): The team decided to use AWS S3 to store rough data, including documents, photos, and other files. S3 provides robust and highly scalable object storage that can handle a variety of data kinds. The group can safely store and retrieve project data using S3, which offers advantages like cost-effective storage, access control, and encryption.