Student Profiles
Compiled by Rourke Amiss using information from team members
Students should create and logs into their profile. After successful completion of this the student will be directed to the Student Profile Page. The Student Profiles is to give the Student an interface to display their information and achievements associated with them, accessible by other users and recruiters. It contains information that is used to identify the Student, such as their name, profile photo, contact details and academic record.
- FR1: Student Profile page must have the name and surname of the Student.
- FR2: Student Profile page must have the contact information of the Student, either an email address and/or phone number.
- FR3: Student Profile page must have a Profile Photo of the Student
- FR4: Student Profile page must have bio that details the Student
- FR5: Student Profile page must have the ability for a Student to update/change any applicable information on the page.
- FR6: Student Profile page must be accessible by other Students and Companies that have requested for access.
- FR7: Student Profile page must have addable tags such that users and companies can identify the Student's interests (including employment status).
- The Student Profile page should allow students to add any personal interests and abilities.
- The Student Profile page should allow Students to add professional information, including qualification and employment preference.
- The Student Profile page should allow Students to link other socials (Instagram, Linkedin) on their Profile.
- Student Profile page should allow Students to link their COS 301 Capstone Project
- All features should me user friendly
- Performance - All features should work as expected.
- The Student Profile is to be created and maintained solely by the Pascal team and no other teams.
- No user may edit another Students profile other than their own.
- A company/recruiter must request for access to relevant information they will need from the Student.
- Kept track of the project and made sure team was working on correct features
- Helped with Bug Fixes
- Organized and monitored integration with other teams
- Formulate features from the given requirements.
- Formulating all the technical requirements for the Student Profiles.
- Functional Requirements
- Non-Functional Requirements
- Compiled the SRS
- Compiled the wiki
- Signed off on the Acceptance Criteria
- Responsible for creating the API for the Student Profiles feature.
- This entailed creating an endpoint to retrieve the student profile, edit the data of a particular student and delete a student profile.
- See the pdf below for example queries and a brief overview of the student profiles api:
- I have also implemented unit tests to test the three main endpoints namely editStudent, getStudent and deleteStudent:
- Planning of Data base schema
- Implementation of Data Base Schema
- Sql calls in repository layer
id user id used to uniquely identify any user email email user signs up with password user's password passwordSalt password salt for encryption name user's full name dateOfBirth user's date of birth companyId only appliable to componies when they sign up. store realtion to compony table created Date account was created suspended If user's profile has been suspended validated If user is a validateduser
userId linked from user table studentNumber student number of user profilePicture link to UserProfileFile for picture bio user's bio employmentStatus if user is employed openToOffers if user is open tob job offers
userId linked from user table tag user tag
userId linked from user table type type of social media link link to social media
userId linked from user table location Preffered location of user
userId linked from user table email addition emails of user
fileId unique id of file userId linked from user table filePath file path in Firebase fileCategory type of file fileExtension type of file
userID linked from user table degreeType type of Degree degreeName Name of Degree
- Responsible for the wireframes and mockups designs of the user interface
- Helped with implementing some of the UI components
- 11 March 2022 (09:30 - 10:05)
- 14 March 2022 (13:30 - 14:02)
- 16 March 2022 (11:30 - 12:32)
- Kept an eye on my teams pull requests in case there was code that didn’t make sense or if any of the tests failed, to keep the pipeline intact.
- Discussed the protocols that need to be taken ,with the rest of the Dev Ops, if the Pipeline broke.
- If an issue was identified when reviewing a pull request a meeting would take place between myself and the coder to discuss the issue at hand and how we can go about correcting it.
- Operation Protocols
- Operations Performed:
- Responsible for implementing the service layer and the business logic of the backend.
- Backend for Student Profiles
- Helped with Demo 1 documentation creation
- Consulted on smaller design decisions with the lead designer
- Created frontend based on given designs
- Implemented mobile responsiveness for the frontend
- Created API calls to populate the frontend with API data
- Final Implementation of Student Profile:
- Most of the service layer for this is complete, need to finalize and test
- Most of the API layer it finished, need to finalize and test
- Service layer of Edit needs to be linked to API, this has been started but need to finalize and test
- Edit Page needs to be designed
- Edit Page needs to be linked to API
- Its possible that next year more information will be needed, that information will then need to be added
- Link the student page with the UP servers allows for automatic pulling of data without the student needing to upload
All acceptance criteria should be completed.
- The Student’s name and student number must be present.
- The Student’s contact details must to be present.
- Student data must be pulled dynamically from the API