Project Status Week 13 - robertAHC/SSW695_Lost-Found GitHub Wiki

Project: Lost and Found - Status Update

End of Sprint 4

Date: 2024-04-17 - 2024-04-24

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 Completed ✅
Contact us Completed ✅
Create the needed test cases/manual report Completed ✅
Deploy the web application 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.
  • Contact us backend logic is completed
  • Provide a summary report to the requester
  • Search for missing item ----

Current Project Status Summary: ✅

  • The team was able to wrap up the tasks left for Sprint 4:
  1. The team was able to deploy the web application using Vercel.
  2. The team created the test report.
  3. Search for missing item has been completed

Team Status Summary:

The team is now ready to show a live demo where we will cover the main features of the system.

Team Goals for the upcoming week:

  • Upload final test report to document branch

Individual Team Member Status:

  • Robert: Created the final presentation. Assisted team with deployment and integration.

    Next week: Work on individual assignments.

  • Aayushi: Completed the Update item detail. Assisted the team with deployment and integration.

    Next week: Work on individual assignments.

  • Meet: Worked on the manual test/report

    Next week: Work on individual assignments.

  • Ishan: Worked on the manual test/report

    Next week: Work on individual assignments.

  • Jashil: Work on the deployment of the tool

    Next week: Work on individual assignments.

Past week team activities:

  • Working group meeting - 04/22/2024 & 04/23/2024
  • 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:

4/22/2024 - The team decided to use Vercel for hosting and deploying our web application 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.