Web Project - abndnc/CS5590-0003 GitHub Wiki

Student Portal – CS 490/590

Project Title – Student Portal Gu-Roo (Based on the word Guru) – Stores projects and plans ideas

Team Members – Daylan Quinn, SangJin Hyun, Ahn Nguyen, and Manideep Nadimpelli

*Motivations -Appeals to us as students –viz. accessing information in a simple and intuitive manner and can access simply through school email or one of a student’s choice.

*Significance – Similar to motivations. Students can access their information at their leisure and create projects and add classes, a daily occurrence with students and their classes.

*Objectives – A portal allowing students to create projects and assign courses based on their needs. User friendly and a simple UI to meet these goals. *Features – Adding projects, adding courses, user login with email, and indicator for course registration alongside ongoing projects available from courses (could be dubbed UI design).

*Approaches/Methods – Designation

1.) Manideep: Developed the registration/login and setup Mongo DB connection. Create collections connect to angular using Node.js. MEAN process et al. Create validations using emails. API review and construction.

2.) Daylan: API usage construction and tailor/review code construction.

3.) Ahn: PowerPoint presentation and review of Git profile et al.

4.) SangJin: Report writeup for the project -- review of database and user roles and fluidity of the project.

5.) Unit Work: Discussed the user info saved to Mongo DB. Communication, client, and server. Discuss working outline of the project and brainstorm ideas – two primary choices were a banking application or a student portal. We decided on the latter. Working API discussion was on Google API or a YouTube one. Based on the project outline, neither of those fit our needs. Consensus on GitHub API +1 more. Teamwork designations.

6.) Zoom meeting times: M:3:00pm – 5:00pm; W:12:00pm - 1:30pm; R:3:00pm – 3:30pm + after class time discussions on different dates.

Working screens from the project through discussion in Zoom: (Insert Screenshots et al.)

API Call:

Route:

Routing:

Services:

Output: • LogIn:

• Registration:

• Dashboard:

• Courses:

• Project:

• Attendance

• User Profile

• Weather Forecast:

• Logout:

References:

“HTML Tutorial.” Tutorialspoint, www.tutorialspoint.com/html/index.htm.

Node.js, www.w3schools.com/nodejs/default.asp

Issues/Setbacks: Database correction between the MEAN setup so communication network was sound. Deciding on which APIs were applicable to our project. Database connectivity issues. Setting up said connection with the project and fixing connections.

Conclusions:

The ability to implement MEAN stack takes some effort between sourcing communication with server, database, and backend connections while creating the student portal. Much of the process lies in creating an idea, implementing a sound design, and experimenting with what works and does not work. One instance was deciding between a banking application or student portal – we chose the latter. Problems like connection issues and management of resources arise and adapting new solutions or creating new ones is key to a successful project -i.e. can we use this API – does it meet the needs of the project? Dividing labor of who does what is no easy feat, and there were some problems with assignment that we sorted out. Lastly, reaching a stopping point with a project. There isn’t really a perfect application as there are bugs or some UI fixes that can be made, but a reasonable application that is user friendly was a main goal of the project.