Reel Rating
Aug 2023 - Dec 2023
Class- Software Design
Program- Figma, Google Docs
What is Reel Rating?
Reel Rating is a project for people who want to find new movies. These movies are based on fun adjectives and verbs the person want to look at with the movie. So either ‘Girlboss’ or ‘Speedy’ you can have this search look very quickly towards the use.
This project involved SUNY Oswego students from undergraduate and graduate programs. The undergrad students study Computer Science (CSC) they do the heavy coding and the Graduate students study Human Computer Interactions as their Master’s Capstone Project. This class is to help communicate and talk about how the two talk to each other.
There were five major teams- Requirements, Qualitative Analysis (QA), Graphical User Interface (GUI), Engine, and Usability. The students get to choose there various groups.
PLEASE NOTE: all the information is in the GITHUB link at the beginning
What was my job?
There were a lot of different needs and I had many different roles.
Requirements - Team Lead
Usability - Participant
Accessibility - Team Lead
Presentator
Requirements
My job was the leader of Requirements. This lead the beginning of the project. This was talking consistent with the different stakeholders who were involved in this project. (while also communicating with the professors). Understanding also the individuals who did what in the project.
In Requirements we covered the Technical Writing part. Part of my job was managing the information given to the other teams. Each team needed individual information A few examples are User Flow, Lowfi designs, color hex details, and input/outputs.
Information Requirements wrote:
Software Requirements- https://github.com/PavlAvstin/OZ-CSC-480-HCI-521-Fall-2023-/blob/main/documentation/requirements/requirements.pdf
Accessibility Requirements- https://github.com/PavlAvstin/OZ-CSC-480-HCI-521-Fall-2023-/blob/main/documentation/requirements/accessability.pdf
This information helped create Figma Files (usability), Java/Javascript (Engine), HTML/CSS (GUI), and test (QA).
Once the important part of the Requirements have been written up. I became a key point in helping out in the Accessibility and Presenting part of the project.
Note: I am not fluent in coding in Java/JavaScript. I can talk about them
Usability
-
This team is made of the Human Computer Interaction students. This was to explore the UX/UI side of the webiste.
-
We looked at sites that had similar tactics - TripAdvisor, Netflix, Rate My Professor, Etc
This included more of an exploration of different design techniques to understand our users.
-
Accessability
-
Accessibility looks a lot different on the internet then it does in person. There are rules that need to be followed for different disabilities that are given.
Accessibility on the internet is an ever-evolving and changing item.
-
This was a request and became a requirement from the Stakeholder.
-
WCAG 2.1
(time was Dec 2023) -
How did this fall into the project
Requirements
The research and writing up to following the correct rules. There were time restraints so choosing the best path to help reflect the time that is there.
Since this was a web based project. Requirements needed to remember there are many different elements to include.
Usability
Usability team was to look at a visual element to implement into Figma. From there the layout were handed off to GUI/Engine.
Figma in the Github
QA
QA team tested the information from Requirements on the code. Creating a good formulated plan to pass off if something is wrong. For other elements FAGAN method was used.
With some time restraints we were able to test color and size.
Engine/GUI
When a website is being built it breaks easily. When it is needed to be fixed for accessibility there are some easy with a simple code implementation.
Coding languages used - Java, Javascript, HTML, CSS.
-
Presenting
For this project, this had a presentation team. This was mainly three people planning out how to formulate the story we needed to give. While I was one of the head presenters, it still takes a long time to plan out. There were two major presentations we had to give:
In front of a board for SUNY Oswego.
To display what the class has done for the final project.
Since we had a lot of things we made quickly, I helped create a 40-minute presentation showing and displaying all aspects of this project.