Work Log for Qi Xuan

Work Log for Qi Xuan

Week 2

Tuesday:

As a team

• Interview Prof Ooi to learn more about the project scope and requirements
• Brainstorm and come up with list of software requirements (user stories)

Wednesday:

As a team

• Meet Prof Ooi to review software requirements
• Refine some of the software requirements

Week 3

Tuesday:

As a team

• Discuss the general flow of the program
• Discuss and come up with schema and ER diagram

Wednesday:

As a team

• Continue discussion and refinement of schema/ER
• Discuss and come up with UI sketches (based on user requirements)
• Discuss and create rough sketch of program's architecture
• Meet Prof Ooi to review progress

Week 4

Tuesday:

As a team

• Discuss and refine some of the user requirements
• Discuss and refine some parts of the UI

Wednesday:

As a team

• Discuss and come up with architecture diagram v1

Individual

• Discuss and come up wth schema/ER v1

Week 5

As a team

• Project setup (Travis, Heroku, Database)

Individual

• Set up Database ddd21cd
• Translate CSV to SQL statements 51e4181
• Coded function for templates to get number of students planning to take module 721a453

Week 6

As a team

• Plan list of features for sprint 2
• Did group code review

Individual

In Pull Request #8: d3e55b0, 964a71a

• Backend code for Security #1: As a user, I want to be able to create a user account, so that I can gain access to the system.
• Backend code for Security #2: As a user, I want to be able to login to the system, so that I can access the system.

Week 7

As a team

• Plan list of features for sprint 3

Individual

• Debugged some frontend and backend features related to module deletion in commits: 7d8411d, b559421
• Started debugging Issue #12: Sessions are shared across all users

Week 8

As a team

• Plan list of features for sprint 4

Individual

Resolved Issue #12 In Pull Request #19 by

• Implementing own sessions handler 1e28941
• Re-modified test cases to accommodate the new sessions. fa82a69

Week 9

As a team

• Plan list of features for sprint 5

Individual

In Pull Request #36:

• Implemented code for High Level #9: "As a user, I want to mark modules as 'starred', so that I can easily access these modules whenever I want." c88be3a, 53113a7

In Pull Request #44:

• Display username in navbar e81d647

In Pull Request #52:

• Breadcrumbs 0620e48

Week 10

As a team

• Plan list of features for sprint 6

Individual

In Pull Request #73:

• Started on Queries #10: "As a user, I want to be able to filter modules by some criteria, so that I can restrict my view of modules to aid in module planning."
• Adding focus areas to module listing page in 76564d In Pull Request #80:
• Populate database with 600 dummy students for demo realism purposes.

Week 11

As a team

• Plan list of features for sprint 7

Individual

In Pull Request #80:

• Edited test cases to test for students dynamically, rather than hard-coded values. 866823

In Pull Request #85:

• Continued with Queries #10: Added filtering to the module listing page.

Week 12

As a team

• Plan list of features for sprint 8
• Settled all pull requests

Individual

In Pull Request #95:

• Added some error handling to database calls to prevent app from crashing after malicious/bad query. fa2b2b

Week 13

As a team

• Project Documentation

Individual

• Final edits to schema and ER diagram.
• Wrote CHANGELOG.md