Objective
Our objective is to create a JavaScript based chatbot that uses natural language processing (NLP) for Brock University. This software is intended to be used by current and future Brock students. There are two categories of questions that the software will provide answers to: (1) specific course information and (2) general information regarding Brock University.
-
Specific course information: • A description of the course • Required prerequisites • Course delivery details (the instructor, time and location of lectures, labs, seminars, etc)
-
General information regarding Brock University:
• Important university dates (non-penalty course withdrawal, exam dates, break dates, etc) • Department information • Transit details • The university’s main page events and news, as well information regarding the campus
To develop this software, we have a team of 8 people using SCRUM methodology. The chatbot will aim to provide users with human-like responses to their queries without the need of human agents. Not only will this serve a larger group of customers, it will also alleviate human resources that can be used elsewhere. The chatbot application will be integrated into the existing website of Brock University for ease of use by Brock students.
Team Name : Roadmen Bugsy
Team leader: Abdul Rahman Abdullah, 6320493
Aws Al Jumaily, 6459861
Anwar Hashmi, 6584957
Ifti Ahmed, 6559348
Ray Keating, 6510200
Nilaanjann Misra, 6366298
Amots Avigad, 6556591
Austin Goodman, 6314363
GitHub page
https://github.com/A98Rahman/COSC4P02Project
Schedule
Sprint Review: Bi-weekly Friday 4:30-4:45
Daily Scrum: Monday 4:30, Friday 4:30 (unless there is a Sprint Review)
Formal development of the software will commence on 15th January where Product backlog will be developed. After 27th January the first draft of the product backlog will be completed and submitted to the stakeholders. The development will then start in 2-week sprints and will continue until end of April where the software deliverable will be ready to be deployed on the webserver.
e development will then start in 2-week sprints and will continue until end of April where the software deliverable will be ready to be deployed on the webserver.