In P06, you created a model, and you created a view. Now create a controller to bring them together.
OR
Document your team members' contributions to the project, and your basic approach on your Team's wiki page, and have a link there to your Team's javadoc and downloads for P07. Also, be sure that your team's code is checked into the same SVN repository you used for P06.
Wiki pages | ||||
---|---|---|---|---|
07S_CFT_T01 | 07S_CFT_T02 | 07S_CFT_T03 | 07S_CFT_T04 | 07S_CFT_T05 |
07S_CFT_T06 | 07S_CFT_T07 | 07S_CFT_T08 | 07S_CFT_T09 | 07S_CFT_T10 |
The team leader of your group should submit, on WebCT, a gzipped tar file or a zip file containing a directory called P07 that contains your deployment environment.
The team leader and primary wiki editor should verify that the wiki page has:
The team leader should also double check that
The team leader (along with the entire team) should also verify that if/when you download the tarball and adjust any global.properties values as appropriate, that there are tasks in the Ant file that successfully
Finally, the team leader, User Interface Team and Tomcat Administrator should verify that when you go to that Tomcat instance and use the the application, that the application actually works as it should.
Item | Explanation | Point Value |
---|---|---|
Application is a useful, bug free application that can be used to solve the Common Free Time problem. |
Common sense—a reasonable non-technical person can be given a link to the application (and a username/password if needed) and can use it to solve the problem of finding common free time. | 50 |
All rubric items below this line are identical to those from P06 | ||
tarball or zip files submitted on WebCT and available on download page | Source code submitted on WebCT should match what is available on the download page | 10 |
Design of View | View is well designed, easy to use, attractive, and validates with either HTML 4.0.1 strict, XHTML 1.0 strict, or XHTML 1.1 | 20 |
Design of Model | Design a model with objects and methods that are reasonable and fit well with the user interface delivered | 20 |
Choice of tests | Choose reasonable tests that cover the basic functionality of the methods specified for the object. Tests should pass for this submission. | 10 |
Header comments | Source code follows the Javadoc style guideline on the Wiki for these header comments. | 10 |
Internal comments | Each file is well commented with internal comments explaining what the code is doing. | 10 |
Submission structured as a .tar.gz or .zip file | When untarred or unzipped, the result should be a single directory containing a well-structure development environment. |
10 |
Use of Ant | There should be a build.xml file in the submission that will compile your code when it is unpacked, and do all of the following:
|
20 |
Wiki is complete |
|
10 |
SVN Repository Setup | SVN repository is setup correctly and can be access by TA and Instructor as well as team members | 10 |
General correctness, style, and following instructions |
See GeneralSubmissionStandards and also review this entire file (P06.html) to be sure you have followed all instructions | 20 |
Total | 150 |