Final Individual Review Ticket - Tanisha Patil

Tanisha Patil Period 4 Yeung APCSP

10/11

	Peer Grade 1 Shreyas	Peer Grade 2 Orlando	Self	Average
Observe Team project quality Runs on cross domain performs all evaluation without crash	0	0	0	0
Individual UI contains input validation	1	1	1	1
Create/Read	1	1	1	1
Update/Delete	0 (has delete)	0 (has delete)	0	0
Code Quality, comments	1	1	1	1
BE review. API handles error conditions	1	1	1	1
BE review GET and POST	1	1	1	1
BE review CREATE and READ data operations	1	1	1	1
BE review UPDATE and DELETE data operations	0	0	0	0
Review ticket	0.5	0.5	0.5	0.5
Runtime links	0	0	0	0
Technical Achievements	0.5	0.5	0.5	0.5
Guides (Blog)	0.5	0.5	0.5	0.5
Video	0.5	0.5	0.5	0.5
Github analytics	0.5	0.5	0.5	0.5
Bonus (personal achievement)	0	0	0	0
Team review (75%)	1	1	1	1
Overall	10	10	10	10

Total

Lack of runtime links due to issues with deployment. (Was forced to deploy on aws seperate from my team due to the format of my flask db - I used an more of an imperative approach. Worked with Mr. Mortenson on deployment but could not get it in time unfortunately) This caused -0.5 for therefore lack of runtime links, and -1 for running across all domains.
No update, causing -2 in both BE and FE category. However, I had a working delete function which displayed in the frontend as a pop up requiring an authentication pin. Update just didn't make sense to create in my scenario.
Total of -3.5 penalty. 13.5 - 3.5 = 10.
10/11
Note: Watch video guide to see project running

Runtime Links

Technical Achievements (Backend Focus): Link to Backend functions github repo (Click here)

READ (Shown as reviews database get requested and formatted appropriately in an html table)
CREATE (Shown as Test6 review was not previously there. When user enters form data, reviews database table updates and in turn is displayed in the html table mentioned above. Additionally form contains validations: All form inputs must be filled, and rate must be an integer from 1 to 5. Working validations are also demonstrated in the video)
DELETE (When "Enter Authentication Pin" button is clicked by user, user is prompted to enter a pin. Entering the wrong pin results in an "Authentication failed message" as displayed in the video. When the correct pin is entered, a popup is displayed on the bottom right of the screen, prompting the user to enter the id of the review that is to be deleted. Once selected, it is seen that a review from the database is deleted and displayed acordingly in the table. The purpose of the authentication ID is to ensure that only administrators of the website are able to delete unwanted/innapropriate reviews on the website and to avoid any user to be able to clear the entire database.)
UPDATE (In progress program)
EXTRA (Average rate function is implemented in the website. Function is called with every change to the database, and the live average can be seen changing when user creates or deletes a review)

Guides for Review (Blog/Video):

Link to video guide: (Click here) Play video in 1.5 playback speed for quick review

Blog Click here for issue)

Github Analytics: (as of 02/26/2023)

Challenges + Solutions:

Deployment: I faced challenges in deployment due to the fact that my flask was in a slightly different format. Because of this I was unable to deploy with my team and had to attempt to do the deployment by myself. Because I wasn't aware of these conflicting issues, I struggled with alloting enough time for myself to work on deployment. Even though deployment was not successful, I was able to research about different deployment services such as oracle cloud and learn more about deployment as a whole. I learned main functionalities and understand the issues with compatibility that may come with deploying.
Delet and Post: The post and delete functionalities were definitely the most difficult for me because I had no knowledge of how to manipulate data in sqlite. Throughout the project, I learned about the many built in commands that sqlite provides and quickly found solutions to the issues I was having.
CORS: I frequently got these errors but with some research and work with my team we were able to find a solution that worked for everyone. In the future I definitely want to look more into this issue.
Continous Delivery: This was a challenge for me last trimester, and I often found myself working on a majority of the project at the last minute. However I found that this trimester I drastically improved and was able to show proof of my contributions every week. I think this is due to our very organized, and well maintained scrum board as well as our team dynamic.

tanishapatil1234 / test-fastpage-tp