Project: Lost and Found - Status Update

Beginning of Sprint 2

Date: 2024-03-06 - 2024-03-20

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: ✅

• Sprint Break Dates: 2024-03-11 - 2024-03-15
• The team met and discussed the user's stories for Sprint 2. The team was able to select the user's stories for this sprint. These include working on the following features:

1. User story #5 (Update item found). 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. User story #6 (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. User story #12 (Log in). This feature aims to allow the user to log into their account and use the latest feature (create missing reports, adding details to reports).
4. User story #13 (Develop signup back-end logic). The end goal is to have a fully working logic that checks for the user in the database and allows the user to log in to the application.
5. User story #9 (Encrypt Password)—Tentative. If the team has enough time, the goal for this sprint is to add an encryption algorithm to secure the password inserted on the login page.

Team Status Summary:

Now that the team has discussed and agreed upon which user stories to work on for sprint 2, the team plans to continue working on those assigned tasks between this week and the next one.

Team Goals for the upcoming week:

• Present a small demo of the current features (in progress/done) that the team was able to come up this far.
• Continue working on the currently assigned user stories.
• Investigate how we can host our basic application so everyone can access it.
• Investigate and start implementing some basic security rules. For instance, how can we encrypt a user's password?

Individual Team Member Status:

• Robert: Started working on the needed code to log into the web application. The goal is to be able to communicate with the database and check for user's credentials to let them into the web application.

  Next week: Continue working on the development of the login logic. Planning to investigate the needed security algorithms/architecture to start brainstorming how our data can be protected and secured.

• Aayushi: Continued working on the development of adding an image to the missing item report.

  Next week: Work on the development of the user stories that deal with updating the status of a missing item.

• Meet: Developed the login form and shared it with the team on Git Hub.

  Next week: Will work with the team to create the table that displays all the missing items.

• Ishan: Will provide assistance developing the front-end table used to display all the missing items.

  Next week: Will continue to work on this task next week as well.

• Jashil: Worked with Aayushi on the integration of S3 Bucket.

  Next week: Continue to help Aayushi set up and integrate S3 Bucket.

Past week team activities:

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