Project: Lost and Found - Status Update

End of Sprint 1

Date: 2024-02-28 - 2024-03-06

Major Project Feature Summary:

Status	Symbol
Completed	User Story #1 (Create a missing item report) ✅
Completed	User Story #2 (Add details about the missing item report) ✅
Completed	Preliminary database Created and landing page ✅
In progress	Connection between front & back end established

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.

Current Project Status Summary: ✅

The team has successfully completed the assigned user stories for sprint 1. These include the ability to have a basic template where the user can create a missing report and add small details about this missing item. This is a significant milestone as it proves that we can now have a working infrastructure between the front and back end and have confidence that we can communicate with the database and do basic table inserts.

Team Status Summary:

Now that the team has completed the tasks assigned to Sprint, the goal is to focus on the following:

• The team to brainstorm/discuss the upcoming user stories for Sprint 2.

Team Goals for the upcoming week:

• Investigate how we can host our basic application so that everyone has access to it.
• Discuss and assign the user's stories for Sprint 2.
• Investigate and start implementing some basic security rules. For instance, encrypt users' passwords.
• Brainstorm/discuss the upcoming user stories for Sprint 2.

Individual Team Member Status:

• Robert: Reviewed the code posted by Aayushi.

  Next week: Planning to investigate the needed security algorithms/architecture to start brainstorming how our data can be protected and secured. In addition to assisting with the upcoming user stories for Sprint 2. Will potentially Work on the login and signup backend logic.

• Aayushi: Released the latest software update that takes care of Sprint 1.

  Next week: Continue working on the upcoming user stories for sprint 2.

• Meet: Developed the front end for the missing item report. Attempting to fully Work on login and signup page.

  Next week: Continue Developing the needed front-end pages needed for Sprint 2. Will help Robert to integrate the forms (login and singup)

• Ishan: Developed the front end for the missing item report. Attempting to fully Work on login and sign-up page.

  Next week: Continue Developing the front end. Will help Aayushi on report missing items and found item features.

• Jashil: Discussed AWS Service.

  Next week: Will help Aayushi set up S3 Bucket.

Past week team activities:

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