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

CS329E- Final Project Presentation

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers. →

CS329E- Final Project Presentation

This presentation culminates tasks involved in building a web application as part of the elements of software engineering program

Avatar for musty-j

musty-j

April 29, 2019

More Decks by musty-j

Other Decks in Programming

Transcript

  1. CS 329E: Software Engineering Group 20 Presentation Group Members: •Miguel

    Arriaga Linguistics & Elements of Computing •Sommer Chavez Linguistics & Elements of Computing •Mustapha Jolaade Petroleum Engineering •Jose Rosales Economics Front End Team: Miguel, Sommer Back End Team: Jose, Mustapha
  2. Project Statistics Total issues: 48 Resolved: 48/48 Total Commits: 61

    11 30 11 9 9 9 14 14 0 5 10 15 20 25 30 35 Jose Rosales Miguel Arriaga Mustapha Jolaade Sommer Chavez Member Statistics Issues Commits
  3. Our Own Critiques: What did we do well? •Free hosting

    by choosing GCP as our host option •Simple website layout and data (books) presentation with excellent linking between pages and icons •Good data visualization •Automation of repeated routines using makefile •Extensive use of Flask library for back end and data base management • I n
  4. Our Own Critiques: What did we learn? •We learned applications

    of the following tools: ✔Flask ✔SQLAlchemy ✔PostgreSQL ✔Slack • Linking database to website post-hosting on GCP • Linking tables on PostgreSQL • Pagination and search capabilities
  5. Our Own Critiques: What can we do better? •Cleaner pipeline

    on Gitlab •Better tracking; more issues and commits •Use normalization to better organize data, reducing errors and saving time •Incorporate APIs on the front end to include more features and fancier UI •Incorporate APIs on the backend to enlarge database and enrich user experience
  6. Our Own Critiques: What puzzled us? •GitLab continuous integration for

    a larger team •Data presentation using PostgreSQL •How does GCP access the database once the website is hosted? •Why web application deployment had password authentication issues •Why concepts and functionality of these tools were taught after the project was due
  7. Group 22 Critiques: What did they do well? •Kudos on

    tackling a real life problem; the web application presents information on world immigration to better inform the public • A simple layout even with so much information to be displayed •Cool features in front end - great use of Javascript and Boostrap. For us, their web application could be a great model for excellent but basic HTML and CSS design
  8. Group 22 Critiques: What can they do better? •Images were

    distorted with poor resolution •Disproportion in issues (52) vs. commits (402) •No technical Wiki report Some puzzling features/methods •Nature of their database •Tools used for data cleaning •Geographical representation of data •Is the web application at risk of being outdated?