List view
- Building - Linting - Docker - Unit testing - Integration testing
Due by June 2, 2017•6/6 issues closedEverything related to the third demo.
Due by August 25, 2017•53/53 issues closedEverything related to the second demo.
Due by July 28, 2017•30/30 issues closedEverything related to the first demo of the project.
Due by May 26, 2017•16/16 issues closedAll the admin related to the setup of the team and getting stuff together. This includes electing all the contact persons, code reviewer, team leader, creation of the team landing page on the CS website, creation of the Github repo, integration with different technologies in order to speed up team preformance, etc.
Due by May 14, 2017•2/2 issues closed- A README.txt file should be created that consists of the Team name, Team members, and the names of the projects that we tender for in our preference order as well as a backup project. - For each of the three projects that we wish to tender for, a tender document (written in LateX) should be created. The PDF's of these documents should then be uploaded to the appropriate slot on the CS website by Monday, 15 May 2017 at 08:00. Each PDF should contain the following (from the specification document): • A title page with project name, project client, team name, names of team members and team photo. • A high level description of the project including the technologies you would like to use to address the project needs. Illustrate with a deployment diagram. • A brief description of the development methodology you intend to follow with par- ticular reference to team meetings and the role the client will play during the de- velopment. • More detail about the team members with particular reference to their current skills and knowledge. Describe how the skills needs to for the implementation of the project will be fulfilled by the members.
Due by May 14, 2017•13/13 issues closed