Samuel Gonzalez

All 21 user stories for the project have been implemented. Here I’ll walk through them and how they are displayed. The website features a navigation menu with an “About” section, where users learn about the app and purpose. On the top right of the navigation menu, users have the option to register (“Sign Up”) or log into their existing accounts with their stored account data. If a user wants to view the list of movies available, they may select the “Movies” option in the navigation bar and once there, they could search for their movie’s title of interest via the search bar. Whether a user is logged-in or not, they could add to cart, accessing their cart in the “Cart” navigation bar option. Additionally, a user can add to their shopping cart, log out, and return to their saved selections if they’d like to purchase in the future. However, before purchasing from the cart, the user must log in or register an account. The cart also allows users to delete the movies placed in their cart if they are not interested anymore. If a user is feeling something towards a movie, they can also leave a review by navigating to the “Movies” option in the navigation bar, select their movie, and add a comment in the open text box. The reviews left by users could be seen by all users and removed by the author, the intention of public reviews is to help the user in their decision of whether or not they’d like to purchase. Additionally, reviews are flexible and could be updated at any time by the author, therefore giving users flexibility to change their mind. Reviews may also be reported by users if they are, for example, inappropriate. Admins can later view reported reviews and act accordingly. Regarding the movie description, each movie (navigating to “Movies”->select movie) comes with a brief description of its plot, giving users details of the movie to help their purchase decision. We also value order history, therefore in the “Orders” navigation bar option, users can look at their past orders containing the movie(s) purchased, price, date, and time; this is intended so the user can track their purchases and expenses. Movies Store was deployed on the internet via PythonAnywhere (https://sammyhi.pythonanywhere.com), so users can access Movie Store from any web browser with an internet connection. The client-server architecture used enables the user to not have to store anything on their machine, the server side handles the user storage via a database. The Movie Store features a responsive and quick Graphical User Interface (GUI), which is adapted to work flexibly across resolutions from a desktop browser to a mobile device. The page also allows super user/admin permissions. An admin may access their portal via the admin path (...com/admin/) and could view user information for admin purposes. Admins may delete, create, update or view movies and user information as needed such as reviews, orders, or users themselves. Admins may also assign permissions to their users such as super user, deactivation (instead of deleting accounts), or give staff access. Reporting user reviews is available to all users, but they cannot report their own. Admins can check what reviews were reported via a checkbox in /admin/, by which user reported the review, admins could un-report reviews, and admins have the option to delete the review. All users can see if a review was reported, but without knowledge of who reported it or a way to modify the report.

The methodology for this development project didn't follow a strict regiment, rather a relatively quick timeline of short sprints over the course of 4 days. Each day I would dedicate about 2-4 hours to writing code and documenting my process via video. Each of these sprints, led and reviewed by myself, would include a three-step process: read documentation prior to writing a single line of code (to ensure understanding), write code, and debug. Debugging took the most time, and in retrospect, most debugging was avoidable had I taken more time on understanding code better before writing. By the fourth day I deployed onto Python Anywhere. The project was straightforward and followed ordered procedures and practices outlined by “Django 5 for the Impatient:” by D. Correra & G. Lim. Most of my questions I had while writing code were answered well by the book and I rarely had to research online. If I had a question that wasn’t answered by the book, then I’d do a browser search on the framework, syntax, or tool I was using.