Passing-on / Getting code
It is essential that you get your code to the team that will be evaluating your project by 5 April 2017 . . Contact the team you are evaluating ASAP to get their code. Ideally, a person from that team should meet with a person from your team and (1) get you the Git URL or provide a zip of the code, (2) make sure that you know how to use it, and (3) answer some of your questions. This is advantageous to the other team as the higher quality your understanding is, the more likely it is your evaluation will be informed. A more informed evaluation leads to a better response. Teams that do not pass on their code to their evaluating team before or on 5 April 2017, may get a 0 for the M11 assignment.
If you never got anything to work implementation-wise, pass to the other team UI mockups, or drawings that they can use to evaluate your UI conception. Remember this a usability evaluation, not a functionality one. You can also instruct them to look at your xml classes only, or even just open the ui files in the gui builder without any other functionality.
To complete this milestone, you must form a usability evaluation plan, execute it, submit a usability report to the team whose prototype you evaluated, and then react to the usability report you receive on your own project.
Passing-on / Getting code It is essential that you get your code to the team that will be evaluating your project by 5 April 2017 . . Contact the team you are evaluating ASAP to get their code. Ideally, a person from that team should meet with a person from your team and (1) get you the Git URL or provide a zip of the code, (2) make sure that you know how to use it, and (3) answer some of your questions. This is advantageous to the other team as the higher quality your understanding is, the more likely it is your evaluation will be informed. A more informed evaluation leads to a better response. Teams that do not pass on their code to their evaluating team before or on 5 April 2017, may get a 0 for the M11 assignment.
If you never got anything to work implementation-wise, pass to the other team UI mockups, or drawings that they can use to evaluate your UI conception. Remember this a usability evaluation, not a functionality one. You can also instruct them to look at your xml classes only, or even just open the ui files in the gui builder without any other functionality.
To complete this milestone, you must form a usability evaluation plan, execute it, submit a usability report to the team whose prototype you evaluated, and then react to the usability report you receive on your own project.