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

Austin Musicians

Austin Musicians

Presentation of our website for CS 329 Software Engineering

Kevin Han

April 23, 2019
Tweet

More Decks by Kevin Han

Other Decks in Education

Transcript

  1. Adriana Cardenas Full-Stack I'm a Senior in Biochemistry doing Python

    development. I'm very into the local music scene and love providing better access to it! I can also juggle ‍♀
  2. Christian Gil Full-Stack Hey! My name is Christian and I

    am a Senior in Biomedical Engineering. I love to code and I look forward to continuing my career in software engineering.
  3. Katelynn Whittington Front-end Fourth year Geography/GIS student at The University

    of Texas at Austin. I also have a minor in Geology and an Elements of Computing certificate.
  4. Kevin Han Front-end, Data Senior Biomedical Engineering Student, with focus

    on computational engineering. Life is short, go get your own lemons and make your own lemonade!
  5. • Our homepage is a very captivating splash page that

    sizes dynamically to smaller devices. • We help spread more awareness of smaller artists by showing their band names randomly on the home screen. • We make it easy to see the relationship between an artist, their shows, and the venues they perform at. This minimalist and logical layout doesn’t overwhelm the user and makes navigation understandable and logical. What did we do well?
  6. • One of the biggest things we learned was to

    create a dynamic website. Instead of having a static page for each venue, show, and artist, we implemented jinja to only have a template for shows, venues, and artists, that dynamically changed depending on the information that was inputted from a database. What did we learn?
  7. • The loading of the main venues, shows, and artists

    page is slow because of the loading of the database to the page. Essentially, for each venue, show and artist, we are looking at venues, shows, and artists that relate. This has a run time of O(venue database size * show database size * artist database size). ◦ We could create sets for each model (using Python) that are passed into the html pages, essentially reducing the real-time runtime. What can we do better?
  8. • We could add information about us and the website

    at the bottom of each page (websites like https://www.austintexas.org/ have this) • We could add more css to each page. Currently, most of the pages are black and white, making them look and feel real mundane. Modern websites do a good job of making each page dynamic and attractive. • Make tables in pages more mobile friendly What can we do better?
  9. • How to write files to a Google App Engine

    app ◦ Google Cloud doesn’t allow writing files in production What puzzles us?
  10. • Homepage is very immersive. Pleasant to look at. Especially

    the pictures in the carousel • States main page has an innovative design. A map of the United States and each state links to the state’s individual page • Individual state page layout is simple and informative • Nice embedment of facebook and twitter in each Senator’s individual page What did they do well?
  11. • Simplicity (e.g. color scheme) makes a website look more

    complete and professional What did we learn from their website?
  12. • Fix their main Senator Page table. Sorting is not

    obvious • Have more information for each Senator. (e.g. Top 5 policies) • Fit carousel to page, avoid need to scroll • Mobile compatibility What can they do better?
  13. Unit Tests 1. Check that no Artist column is empty

    2. Check that no Show column is empty 3. Check that no Venue column is empty 4. Check that query for an Artist's genre works and is correct 5. Check that query for a Venue's address works and is correct 6. Check that query for a Show's date and time works and is correct 7. Check that query for a non-existing Venue returns nothing 8. Check that query for a non-existing Show returns nothing 9. Check that query for a non-existing Artist returns nothing