Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Music Madness Presentation

Sponsored · Your Podcast. Everywhere. Effortlessly. Share. Educate. Inspire. Entertain. You do you. We'll handle the rest. →
Avatar for Kayla Mayberry Kayla Mayberry
April 19, 2017
38

Music Madness Presentation

Avatar for Kayla Mayberry

Kayla Mayberry

April 19, 2017

Transcript

  1. Team Members Rebecca Bingham Artist Pages, Lead Tester Roger Craycroft

    Record label pages, Technical report Co-editor Allen Fernandes Splash, About, Navigation Blake Kappel Song Pages, Technical report Co-editor Kayla Mayberry Model pages,Technical report Co-editor
  2. Issue Tracker Status Total Number of Issues: 51 Total Number

    Unresolved: 0 Team Member Issues Rebecca Bingham 19 Roger Craycroft 18 Allen Fernandes 21 Blake Kappel 25 Kayla Mayberry 22
  3. Critique of Music Madness What did we do well? •

    We completed all project phases in a timely manner by establishing regular meeting times • Created a nicely designed website, with working features that performs a useful function • Delegated tasks efficiently, each team member contributed • Understood the tools we used for each project phase
  4. Critique of Music Madness What did we learn? • How

    to manage the project timeline • How to use/implement HTML, Javascript, CSS, Bootstrap, Digital Ocean, and Flask in a web application • How to work with team members to create a successful project
  5. Critique of Music Madness What can we do better? •

    We can enhance styling in our website ◦ Improve layouts ◦ More color to make more pleasing to the eye • Increase amount of data to improve use cases
  6. Critique of Music Madness What puzzles us? • How Flask

    is useful in a more developed project • How DigitalOcean works in more detail ◦ Integration with Apache server ◦ The functionality of the Python virtual environment ◦ The specific ways in which each of the above works together to run and host the website • Learning to implement all the configuration steps on our own, without the step-by-step guide
  7. Critique of CarsCarsCars What did they do well? • The

    user interface looks nice • The splash page is eye-catching • There is extra functionality on the model pages - including search and changing the amount of entries shown • Nice website overall; useful and smooth to navigate
  8. Critique of CarsCarsCars What did we learn from their website?

    • We learned about car brands, the models they produce, and the types of vehicle classes there are ◦ And how they are interrelated • That Mercedes makes a $634,000 6-wheel drive pickup truck • Judging from the extra features mentioned before, we learned we could implement extra functionality that makes the user experience more diverse
  9. Critique of CarsCarsCars What can they do better? • Consistent

    navigation design • Add more car brands • Reformat text descriptions so they do not run off of the bootstrap container
  10. Critique of CarsCarsCars What puzzles us about their website? •

    The navigation is different on the homepage than the rest of the website • The “Show x entries” is sometimes more than the amount of actual entries