Project Roadmaps and Statuses

• Rewriting from scratch

• Complete wireframes

• Create Handbook API (courses, programs, majors, minors)

• MVP for SENGAH

• Unfortunately, we are quite behind schedule with no realised wireframes for any other pages beside the landing page. Trimester 3 has not been kind to anyone.

• Even so the landing page is in need of some changes with the menu and footer responsiveness not on par with industry standard.

• Content Syndication (CS) has is completed with clear objectives as to what is needed to be edited and maintained for the CMS.

• With internal showcase over we look to implementing the other wireframes and completely removing all hard coded data from the frontend and serve purely from the back-end. This will allow an easy transition into editing the content via CMS.

• We have decided to go with the professional style-sheet for the design of our CMS and taking on suggestions from our directors go for an admin style page like Django’s.

• I plan at least to continue in this role until a new lead is chosen so that the next lead does not waste their time trying to play catch up as I did at the beginning of the year.

• Complete implementation of wireframes before end of January.

• And in parallel create and implement the architecture for our CMS. Handling of bugs and errors left for the team after as they look towards the first few stages of alpha release. (Of course we will still be undertaking TDD but any bugs that block for a significant amount of time will be left to next years team).

• Frontend:

  • Most components' layouts are finished

  • Not all buildings' assets are present

• Backend:

  • Logic mostly present

  • Lots of hardcoding, which need to be removed e.g. current term selection should be dynamic

  • Scraper not properly working but looking to collaborate with Notangles' scraper

• 2020

  • Frontend connecting to backend

  • Functional caching system

  • GraphQL backend

• 2021

  • Collaborate with Notangles to share scraper

  • Adapt backend to use Notangles' data

  • Finish off frontend (building data)

  • Connect frontend to backend

  • More documentation e.g. API endpoints

• Stretch goals

  • More responsive design

  • Allow students to communicate with the app to mark rooms which they’ve personally occupied as booked (i.e. not just rely on timetable data)

Deployed and given to careers for review and feedback

• UI/UX fixes dependent on review from Careers

• Deployed and containerised

• Basic functionality (timetable planning) is mostly there

• Generally unusable on mobile

• Some small bugs/issues with the UI to address

• New Python scraper is almost done and ready for migration

• Auto-timetabling algorithm and front-end mostly done

• Social-timetabling design and front-end have been prototyped

• Start of T2

  • Complete the new scraper and integrate it with Freerooms

• Start of T3

  • Fix UI bugs/issues

  • Basic mobile website support

  • Connect the auto-timetabling front-end and back-end

  • Select and use a database for the account system

• 2021

  • Add UI features (e.g. tabs, history, exporting, weeks view, etc)

  • Social-timetabling (add friends and plan together)

  • Documentation in Confluence and code comments

  • Comprehensive testing, especially on the back-end

• 2021-2022

  • Expansion and integrations (gcal, other projects, other unis, etc)

  • Mobile app (React Native)

NFC, moving app out of Expo to hopefully fix the NFC issue

• Get NFC Working - when you tap your student card against the phone while the app is open, it should be able to detect the card and extract the zID