Project Status - robertAHC/SSW695_Lost-Found GitHub Wiki

Project:Lost and Found - Status Update

Sprint 1

Date: 2024-02-21 - 2024-02-28

Major Project Feature Summary:

Status Symbol
Completed ✅

Major Project Feature % completed to date

  • Form and Landing Page 100%

Current Project Status Summary: ✅

The team has successfully created the database for our project. The front-end team has created a basic form and landing page layout. The team has also discussed the AWS services to be used in this project and has finalized them. Additionally, every member of the backend team was able to successfully connect to the database remotely.

Team Status Summary:

The team will continue to work on the needed front-end pages and work with the back-end team to create the needed connections/communication between the front and back.

Team Goals for the upcoming week:

describe what are the goals of the team in the upcoming week, for example:

  • Connect the front end and back end to the AWS service discussed.
  • Finalized the user stories assigned for Sprint 1.
  • Brainstorm/discuss the upcoming user stories for Sprint 2.

Individual Team Member Status:

  • Robert: Working on the backend and leading the team. Robert helped the team troubleshoot the issues with the database connectivity.

    Next week: Help Aayushi with the user's stories for Sprint 1.

  • Aayushi: Working on backend.

    Next week: Continue working on finalizing the remainder of user stories for sprint 1.

  • Meet: Developing the front end.

    Next week: Continue Developing the needed front-end pages needed for Sprint 1.

  • Ishan: Developing the front end.

    Next week: Continue Developing the front end, making it more efficient

  • Jashil: Discussed AWS Service.

    Next week: Will connect AWS service with the backend and front team and resolve issues of connections.

Past week team activities:

  • 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

  • Working group meeting (ALL) - 02/19/2024
  • Working group meeting (ALL) - 02/26/2024
  • 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:

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.

Other Comments:

No other comments