Skip to content

Home

Jump to bottom
Zoraiz Qureshi edited this page Apr 26, 2020 · 4 revisions

Welcome to the CMS wiki!

Team:

The project is currently being developed by a team of LUMS students (Hammad Nasir 22100278, Zoraiz Qureshi 21100130, Hamza Bin Aqeel 21100126, Farrukh Rasool 21100297, Hamza Farooq 21100197) under their advisor Dr. Suleman Shahid, Assistant Professor, Department Of Computer Science, LUMS, and it is also a constituent component of their course "CS-360 Software Engineering".

Background:

The Co-Curricular Activities Department (henceforth CCA) at LUMS acts independently, and in coordination with the IST and administration to assist the various student led societies at LUMS. The purpose of the project is to deliver a fully functional system to the CCA through which it can streamline internal communication, alongside CCA-society interactions, instead of managing the entire process through email. The portal will offer two varying interfaces for users in the CCA, and for societies at LUMS to ease communication between them.

The CCA reflects the need for a proper management system to concurrently manage the 42 societies at LUMS, which is difficult at present due to the lack of a system devoted solely to the goal of an improved communication channel. Similarly, through the portal the students will find it easier to send their form submission requests to the CCA using a defined routine.

The modus operandi of getting events approved at LUMS, alongside all its specifications, is through society email accounts and an indefinite number of reminder visits to the CCA. Our product will minimize the issue of event request being missed out and delayed by allowing society portals to function with an active notification system on parallel fronts.

Product Functionality:

The various components of the system along with their functionalities are mentioned here briefly for an overview of the product functionality:

  1. Authentication System: Society and CCA: Contains default society accounts which are linked to email IDs of societies at LUMS and CCA User accounts (Admin and Member) which will be managing the system for years to come.
  2. Form Maker: A customizable form maker with logic jumps to assist CCA in creating / editing / deleting static forms e.g. for event approval and auditorium booking.
  3. Form Submission Manager: Form submissions alongside all supporting documents needed by the CCA can be created, edited and made on the portal by a society through their dashboard.
  4. Request List Manager: Submitted forms or also 'requests' to the CCA would be managed by the system. Review submission progress, reply with issues by attaching notes, automatical approval of submitted forms via email.
  5. Internal Task Management: Manages allotment of tasks and sub-tasks among CCA members and form requests.
  6. Account Manager: Add / edit / delete accounts for both Society and CCA Admin/Member accounts, change password, create custom task statuses.
  7. Approval Email Automation: Redirect emails towards the President and the Patron of the society for approval before CCA starts processing.
  8. External Document Upload for Audit: An automated system of filing which sequentially stores documents to be viewed by auditors directly, as requested by CCA. CMS Breakdown

Front-end Dependencies:

  • ReactJS
  • Redux
  • Material UI (Core, Icons, Lab)
  • Redux Toolkit
  • Formik
  • formik-material-ui
  • mui-datatables
  • react-beautiful-dnd (Drag and Drop)
  • Yup
  • react-textarea-autosize

Back-end Dependencies:

  • NodeJS
  • ExpressJS
  • MongoDB
  • JWT
  • Mongoose
  • cookier-parser
  • @hapi/joi
  • express-validation
  • morgan
  • mongoose-plugin-autoinc

Internal Development Documents:

API Specification Document Commit Process and Restrictions Commit Format and Guidelines JS Code Conventions

Clone this wiki locally