Differences

This shows you the differences between two versions of the page.

--- labtests [2009/10/13 13:02] – roumani
+++ labtests [2009/11/24 04:13] (current) – roumani
@@ Line 1: / Line 1: @@
 ====== Lab Tests ======
-[[https://www.cse.yorku.ca/~roumani/course/4413/F09/labtest1/askNot.cgi|{{44test.jpg|}}]]
+[[https://www.cse.yorku.ca/~roumani/course/4413/F09/labtest2/q.html|{{44test.jpg|}}]]
+<html><!--
 ===== Lab Test #1 =====
@@ Line 24: / Line 24: @@
   * Source files
-  * A file named ''answer.txt'' in which you explain your approach
+  * A file named ''answer.txt'' in ''WebContent''
+Your work is marked based on correctness and on meeting the various software engineering guidelines, design patterns, and best practices.
+The file ''answer.txt'' contains a self assessment of your submission. In it, you must indicate, for every feature in the requirement, whether your webapp implements that feature or not, and if so, whether the implementation works or not. Even if a feature is not implemented, or implemented incorrectly, you will receive part marks if you articulate how you plan to implement it.
-Your work is marked based on correctness as well as meeting the various software engineering guidelines, design patterns, and best practices.
-Partial credit will be awarded to incomplete submissions provided they are accompanied by a file named
 ==== Preparation ====
@@ Line 41: / Line 39: @@
   * Reading Chapters 6 and 10 (filters and events) in the Servlets Specs
-Note that since you can bring your textbook to the test and that you have access to the Specs, the word "Reading" above refers more to "understanding" and "knowing where things are" rather than "memorizing".
+Note that since you can bring your textbook to the test, and that you have access to the Specs, the word "Reading" refers more to "understanding" and "knowing where things are" than to "memorizing".
-Note also that since you will have access to you home directory during the test then you are advised to create a number of basic programs, xhtml, and jspx files in it so you can easily and quickly adapt them during the test rather than start from scratch.
+Note also that since you will have access to you home directory during the test, you are advised to have a number of basic programs, xhtml, and jspx files in it so you can easily and quickly adapt them during the test rather than start from scratch.
+-->
+</html>
-<html><!--
 ===== Lab Test #2 =====
@@ Line 56: / Line 56: @@
     * You may not communicate with anyone, inside or outside the lab, by any mean during the test.
     * Seating may be preassigned; there may be several test versions; and network traffic may be monitored.
-    * The test is open-book and you have full access to your home directory and to the Internet. In particular, you have access to this site and to its //Resource Directory//.
+    * The test is open-book and you will have full access to your home directory, the course web site, and all the resources linked to from the course site.
 ==== Scope ====
-The test will cover everything after LT#1 and up to the prior week. This means CGI (in Perl) and JEE Webapps (Servlets, JSP, MVC). Note, however, that custom JSP tags are not in scope; only EL and JSTL are.
+The test will cover everything up to the prior week. This means custom functions and tags (Lab #2), xml technologies, and Web Service clients.
 ==== Format ====
-The test involves hands-on problem solving: you will be presented with a problem and asked to solve it. You are expected to devise a solution, implement it, and then submit it.
+The test involves three questions, one on custom tags and functions, one on xml (xsd and xsl), and one on building a clients of a given wsdl. You are expected to analyze the requirement, design a solution, implement it, and then submit it.
+Your work is marked based on correctness and on meeting the various software engineering guidelines, design patterns, and best practices.
-Note that even though this is a lab test, you may treat it as a paper test; i.e. write programs and submit them without even attempting to see if they compile. Doing so will allow you to finish faster but may lead to lower marks because your program may have errors or shortcomings that could have been identified had you compiled and ran your code. You must therefore manage your time carefully to achieve an optimal trade off.
+The file ''answer.txt'' contains a self assessment of your submission. In it, you must indicate, for every question, whether or not you were able to complete the requirement. Even if a feature is not implemented, or implemented incorrectly, you will receive part marks if you articulate how you plan to implement it.
-==== Preparation ====
-The best way to prepare for the test is to do the labs (labs 2-4) and review the lecture notes posted in the Calendar along with the cross-listed book sections. It also helps to have a number of basic template servlets and JSP files in your home directory so you can easily and quickly adapt them during the test to solve the test questions.
-===== Lab Test #3 =====
-==== Policies ====
-    * The test will be held at 8:30 am on Friday Feb 20.
-    * The test is 120-min long and will be held __**in Prism**__ (not in a lecture room).
-    * You will login to one of machine in the lab using your 8-character ''cs'' username.
-    * Bring a photo ID.
-    * No questions are allowed during the test.
-    * You may not communicate with anyone, inside or outside the lab, by any mean during the test.
-    * Seating may be preassigned; there may be several test versions; and network traffic / command history may be monitored.
-    * The test is open-book and you have full access to your home directory and to the Internet. In particular, you have access to this site and to its //Resource Directory//.
-==== Scope ====
-The test will cover everything after LT#2. This means advanced JSP, advanced Servlets, Web Services, and XML technologies.
-==== Format ====
-The test involves hands-on problem solving: you will be presented with a problem and asked to solve it. You are expected to devise a solution, implement it, and then submit it.
-Note that even though this is a lab test, you may treat it as a paper test; i.e. write programs and submit them without even attempting to see if they compile. Doing so will allow you to finish faster but may lead to lower marks because your program may have errors or shortcomings that could have been identified had you compiled and ran your code. You must therefore manage your time carefully to achieve an optimal trade off.
-==== Preparation ====
-The best way to prepare for the test is to review the lecture notes posted in the Calendar along with the cross-listed book sections. It also helps to have a number of basic template programs in your home directory so you can easily and quickly adapt them during the test to solve the test questions.
--->
-</html>