Project: Lost and Found - Status Update

Mid of Sprint 3

Date: 2024-03-27 - 2024-04-02

Major Project Feature Summary:

Status	Symbol
Secure Login	Completed ✅
Safeguard Personal Information	Complete ✅
Report Missing Item	Completed ✅
Search for Missing Item	In progress (50%)
Check and Update Status of a Missing Item	In progress (30%)
Notification System	In progress (20%)
Visual Representation of All Missing Items	Completed ✅

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.

Current Project Status Summary: ✅

• The team is currently in the process of completing the following feature this week:

1. (Update report). This feature aims to provide the opportunity to whoever created the missing report to update from "missing" to found" or potentially update any detail of the selected report.
2. (Search for missing items). This feature aims to display a table of all the missing items, and by adding some search criteria, the user can narrow it down to specific requirements.
3. (Develop signup back-end logic). The end goal is to have a fully working logic that allows the admin to insert a new user into the database.
4. (Notify student) started the development of the Contact Us feature as well as the notification system.

Team Status Summary:

The team is planning on closing the user stories for sprint 3 this week and start discussing what we can work on for sprint 4.

Team Goals for the upcoming week:

• Have all the user stories for sprint 3 completed and closed.
• Start/continue working on the user stories assigned for sprints 3 & 4.
• Investigate how we can host our basic application so everyone can access it.

Individual Team Member Status:

• Robert: Completed the login user stories. Login logic manually tested. Code Committed to Git Hub.

  Next week: Working on the following: Contact us page, notification system, logic needed for inserting new users into the database.

• Aayushi: Started developing the search for the missing item.

  Next week: Finalize the search for the missing item feature and start working on the update missing report feature.

• Meet: Started working on the admin pages.

  Next week: will continue to work on creating intuitive and visually appealing user interfaces for the admin side of the application.

• Ishan: Assist Aayushi with the updates needed for updating missing item report interface.

  Next week: Assist Robert with the integration of the Contact Us page.

• Jashil: Was assigned to research how to deploy our application using AWS.

  Next week: Show a demo to the team internally. The goal is to see if we are able to deploy a small application "hello world".

Past week team activities:

• 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.