MusicBuddy Presentation

Our group presentation for CS329e Software Engineering

Transcript

1. MusicBuddy.me The Journey to Create the Ultimate Music Website
2. Group Members • Drew Hillhouse • Pearson Daniels • Justin Kim • Jason Giang • Kyle Katzen
11. Problems • Poor Git understanding • Time management • Poor scheduling / scheduling conflicts • Inefficient meetings • Poor research into required tools to build website • Every phase required editing old code to accommodate new technology ◦ Ex. HTML pages were not set up properly for bootrstap • Many, many, many, many, many bugs that required many, many, many hours to debug
12. Issue Tracking • We had 66 issues over the course of our project. • Once one was completed, we closed it and assigned it to the person who did it. • We had 10 bugs and 15 features and the rest were completing project requirements. • All issues were eventually resolved
13. Flask Implementation • We went through and created a function in the app.py for every html that we had used. • And we changed every href to an html to a call to the function in flask. Problems: • We never figured out how to get the functions to work in the html that was created with javascript.
14. musicbuddy.me Critique What we did well: • Provided a simple structure that is easy to understand and navigate for all users • Embedding Spotify players on the tracks pages so users can have a preview of songs to determine if they want to listen to the full version
15. musicbuddy.me Critique cont. What we can do better: • Style individual pages more possibly with a background • Provide more information on individual pages such as links to YouTube videos or Wikipedia pages • Using convention with coding so we don’t run into unnecessary problems What puzzles us: • Hosting on Digital Ocean
16. cs329e-cartoons.me Critique What they did well: • Very simple structure of the pillars makes pages easy to read and understand • Dynamic slideshow that actively changes the size of the slideshow borders to match the dimensions of the current picture was really well done • Making clickable links change when scrolled over helps users know what is interactive or not What we learned from their website: • Simple is great when it gets the job done in an efficient manner
17. cs329e-cartoons.me Critique cont. What they can do better: • Countries with only one cartoon/show could have the show centered in the page, rather than all starting from the left side (Japan, France, etc.) • Some of the arrows for slideshows were not in line with the pictures (Japan) • The Simpsons page links a YouTube video that has been blocked What puzzled us about their website: • Nothing in particular
18. What We Learned • Many of us became familiar with new tools (javascript, css, jquery) • Server management, domain hosting, and Flask were new concepts for all of us • Use of Git allowed us to familiarize us with issue tracking and version control • We all taught each other what others lacked • Importance of code modularity and reusability in order to implement technologies at a later time