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
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
of the following tools: ✔Flask ✔SQLAlchemy ✔PostgreSQL ✔Slack • Linking database to website post-hosting on GCP • Linking tables on PostgreSQL • Pagination and search capabilities
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
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
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
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?