Project: Lost and Found - Status Update

End of Sprint 3

Date: 2024-04-02 - 2024-04-10

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	In progress (80%)
Search for Missing Item	In progress (80%)
Check and Update Status of a Missing Item	In progress (80%)
Contact us	In progress (98%)
Create the needed test cases	Not started
Deploy the web application	In progress (10%)

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 was able to complete the following feature this week:

1. (Notify students) With this feature, users can now receive a detailed summary of their email regarding what was reported as missing. In addition, the user is now able to send a quick email to our "Lost & Found" department where we can answer questions (Contact us)

• By the end of this week the following will be completed:

2. (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.
3. (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.

Team Status Summary:

The team is now in the final process of closing the user stories for sprint 3 this week. Additionally, the team discussed who could successfully help/work the user stories for sprint 4.

Team Goals for the upcoming week:

• Have all the user stories for sprint 3 completed and closed.
• Work on the user stories assigned for sprints 4.
• Create Test cases.
• Start deploying the application.

Individual Team Member Status:

• Robert: Completed the notification system. Users can now receive a notification via email regarding their missing report. In addition to quickly communicate to our "Lost & Found" team with questions using our "Contact us" page.

  Next week: Assist the team in deploying the application. As well as creating some test cases using Django.

• Aayushi: Worked on search for missing item and update missing item.

  Next week: Will work on report missing item and update missing item test cases.

• Meet: Worked on the frontend UI changes of user side.

  Next week: Will work on the test cases of update items.

• Ishan: Working on update missing item UI.

  Next week: Will work on frontend changes of list missing item.

• Jashil: Well researched about how can we deploy our Django application on EC2. EC2 instance has been created using Ubuntu OS (can be changed later if required).

  Next week: A small demo of a basic Django app will be deployed and showed to the team internally. Similarly will also try to clone our entire Git repository without missing all the files for our final deployment.

Past week team activities:

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

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.