Difference between revisions of "COMP345 fall 2016 intermediate project presentations"
From Dr. Joey Paquet Web Site
(→Schedule (November 10-11, 2016)) |
(→Assignment statement) |
||
(5 intermediate revisions by one user not shown) | |||
Line 1: | Line 1: | ||
==Assignment statement== | ==Assignment statement== | ||
− | For this "intermediate project delivery ", you have to demonstrate a '''running software''' (i.e. C++ code that you can compile and execute to demonstrate some intended project features). The '''baseline''' for this delivery of the mandatory features of the game. See the [[Media: | + | For this "intermediate project delivery ", you have to demonstrate a '''running software''' (i.e. C++ code that you can compile and execute to demonstrate some intended project features). The '''baseline''' for this delivery of the mandatory features of the game. See the [[Media:gradingfinalproject.COMP345.paquet.2016.2.pdf|grading scheme]] for a complete check list and grading scheme that will be used during the project demonstration. |
===Additional notes=== | ===Additional notes=== | ||
Line 37: | Line 37: | ||
|| 8h15 || || 8h15 || | || 8h15 || || 8h15 || | ||
|- | |- | ||
− | || 9h00 || | + | || 9h00 || TEAM 19 || 9h00 || TEAM 3 |
|- | |- | ||
− | || 9h45 || | + | || 9h45 || TEAM 18 || 9h45 || TEAM 4 |
|- | |- | ||
− | || 10h30 || | + | || 10h30 || TEAM 21 || 10h30 || TEAM 20 |
|- | |- | ||
− | || 11h15 || TEAM 6 || 11h15 || | + | || 11h15 || TEAM 6 || 11h15 || TEAM 17 |
|- | |- | ||
|| 12h30 || TEAM 1 || 12h30 || TEAM 10 | || 12h30 || TEAM 1 || 12h30 || TEAM 10 | ||
Line 49: | Line 49: | ||
|| 13h15 || TEAM 7 || 13h15 || TEAM 12 | || 13h15 || TEAM 7 || 13h15 || TEAM 12 | ||
|- | |- | ||
− | || 14h00 || TEAM 11 || 14h00 || | + | || 14h00 || TEAM 11 || 14h00 || TEAM 16 |
|- | |- | ||
|| 14h45 || TEAM 2 || 14h45 || TEAM 13 | || 14h45 || TEAM 2 || 14h45 || TEAM 13 |
Latest revision as of 08:27, 1 December 2016
Contents |
Assignment statement
For this "intermediate project delivery ", you have to demonstrate a running software (i.e. C++ code that you can compile and execute to demonstrate some intended project features). The baseline for this delivery of the mandatory features of the game. See the grading scheme for a complete check list and grading scheme that will be used during the project demonstration.
Additional notes
- The preceding description is the baseline for this assignment, i.e. failure to demonstrate these features by the execution of a single integrated and compiled program will result in major grade deductions.
- Other features are allowed to be present in the build that you are presenting. However, your demonstration should focus on demonstrating the baseline features for this assignment. You will not receive bonus marks for additional features. You will not have mark deductions for additional features that are unfinished at the time of the presentation. However, you will receive mark deductions if additional features prevent the proper presentation of baseline features.
Instructions for scheduling the presentation
- read ALL the instructions on this page carefully. Failure to follow the instructions may result in your request to be discarded.
- send an e-mail to paquet@cse.concordia.ca with subject "COMP345: project demonstration scheduling", and with the following information in the body of your e-mail (ALL this information is NECESSARY) :
- your team number, the list of all your team members, including student IDs
- a list of ALL available time slots given in decreasing order of preference
- I will allocate time slots in a first-come-first served basis and give you a confirmation by e-mail
Other useful information
- all team members do not need to attend the presentation
- plan your presentation to last for at most 20 minutes
- the intent of the presentation is that you must demonstrate that your application is working according to what I asked in the assignment description
- if your application is not working, you have to make sure that you can effectively demonstrate what is currently working
- it is your responsibility to make sure that your project can be demonstrated in the laboratory
- any request for a time slot outside of the proposed schedule will be disregarded
- only the first request is processed, any further request from the same group is discarded
- all demonstrations should occur in the laboratory
Schedule (November 10-11, 2016)
time | Thu, nov 10th | time | Fri, nov 11th |
---|---|---|---|
8h15 | 8h15 | ||
9h00 | TEAM 19 | 9h00 | TEAM 3 |
9h45 | TEAM 18 | 9h45 | TEAM 4 |
10h30 | TEAM 21 | 10h30 | TEAM 20 |
11h15 | TEAM 6 | 11h15 | TEAM 17 |
12h30 | TEAM 1 | 12h30 | TEAM 10 |
13h15 | TEAM 7 | 13h15 | TEAM 12 |
14h00 | TEAM 11 | 14h00 | TEAM 16 |
14h45 | TEAM 2 | 14h45 | TEAM 13 |
15h30 | TEAM 14 | 15h30 | TEAM 5 |
16h15 | TEAM 8 | 16h15 | TEAM 9 |