CS331e Presentation - MarvelDB

Presentation on our Marvel database website for CS331e class

Transcript

1. Marvelous DB Avengers Initiative Madalyn Marabella, Kadie Meroney, Rachel Thornton, Diana De La Torre, Sang Kook
2. Food Mood Critique (Group 9) What did they do well? • Well Designed/Organized • Splash Page • Using Images as Backgrounds What did we learn? • Utilizing images on websites as much as possible helps make it look more polished • Recipe pages are very simple/informative
3. Food Mood Critique (Cont) What can they do better? • Linking together entities • Having more attributes for recipes • Adding more information about recipes (serving size, ect). What puzzles us about their website? • Sorting functionality/visibility • What makes this website different from other recipe websites?
4. Group Members Kadie Meroney Rachel Thornton Sang Kook Diana De La Torre Madalyn Marabella Commits: 8 Issues: 8 Unit Tests: 2 Commits: 20 Issues: 8 Unit Tests: 2 Commits: 35 Issues: 9 Unit Tests: 2 Commits: 24 Issues: 9 Unit Tests: 2 Commits: 57 Issues: 8 Unit Tests: 3
5. What is Marvelous DB? • Marvelous DB is a website that will help devoted fans keep track of their favorite comics, events, and characters by creating an easy to navigate database that makes learning about the Marvel Universe accessible for all fans. • We hope that this website can become a hub for Marvel fans to exercise their obsession and find answers to questions. The heart of our website is to unite the Marvel community in one accessible location.
6. Demo :)
7. Critiques • What did we do well? ◦ Dividing responsibility ◦ NavBar, backgrounds (demo) ◦ Sorting, searching, Avengers font (demo) • What did we learn? ◦ GCP, namecheap, and DNS settings configuration ◦ Tiered application structure ◦ Bootstrap, frontend design ◦ Prioritizing ◦ Communication and collaboration/organizing ourselves
8. Critiques • What can we do better? ◦ Build a proof-of-concept before starting your project (Marvel API) ◦ Pay attention to how your db entities will connect ◦ Marvel image should’ve been linked to homepage • What puzzles us? ◦ Gitlab struggles early on ◦ Unit tests failing locally for some team members ◦ CSS complications and repeating background image