Peer review: Weekly team meetings are held to review each team work done members’ for that week and each member gives his/her feedback and suggestions. Instructor/TA Reviews: Reviews from the instructor and TAs as and when various documents have been submitted have proved useful for the development. project’s Client Meetings: Weekly meetings with the client helps get feedback from them about what is acceptable for the project and what should be reworked. 4.2. Methods, Tools and Facilities Table 7: Tools used for the Project Tools Usage Provider Github A version control system which acts as repository for the code Github checked in by different team members, allowing us to keep track of changes made. Bootstrap Used to design better UI for the website Open Source Google drive All documents required for the project are shared with team Google members through the drive so that everyone can team’s download and review it. Intellij IDEA Backend development of the project JetBrains Visual Tool used to create UML diagrams Visual paradigm paradigm MySQL Database Open Source Microsoft All documents for the project were created using MS Office; Microsoft office Word, PowerPoint, and Project in particular. Brackets Frontend development of the project Brackets WhatsApp Communication within the team was facilitated through a WhatsApp Messenger Whatsapp group. HeidiSQL Tool that enables fast and easy management of the database HeidiSQL Skype Used to communicate with DEN student Microsoft Jira To log time and effort spent on each task of the project by USC different members of the team Winbook Used to identify and prioritize win conditions of all the USC stakeholders Project All final documentation regarding the project is stored on the USC Website website. Balsamiq Used to create project prototype design Balsamiq
Peer review: Weekly team meetings are held to review each team members’ work done for that week and each member gives his/her feedback and suggestions. Instructor/TA Reviews: Reviews from the instructor and TAs as and when various documents have been submitted have proved useful for the project’s development. Client Meetings: Weekly meetings with the client helps get feedback from them about what is acceptable for the project and what should be reworked. 4.2. Methods, Tools and Facilities Table 7: Tools used for the Project Tools Usage Provider Github A version control system which acts as repository for the code checked in by different team members, allowing us to keep track of changes made. Github Bootstrap Used to design better UI for the website Open Source Google drive All documents required for the project are shared with team members through the team’s drive so that everyone can download and review it. Google Intellij IDEA Backend development of the project JetBrains Visual paradigm Tool used to create UML diagrams Visual paradigm MySQL Database Open Source Microsoft office All documents for the project were created using MS Office; Word, PowerPoint, and Project in particular. Microsoft Brackets Frontend development of the project Brackets WhatsApp Messenger Communication within the team was facilitated through a Whatsapp group. WhatsApp HeidiSQL Tool that enables fast and easy management of the database HeidiSQL Skype Used to communicate with DEN student Microsoft Jira To log time and effort spent on each task of the project by different members of the team USC Winbook Used to identify and prioritize win conditions of all the stakeholders USC Project Website All final documentation regarding the project is stored on the website. USC Balsamiq Used to create project prototype design Balsamiq