User Tools

Site Tools


tests

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
tests [2007/11/01 01:52] roumanitests [2008/08/29 19:37] (current) roumani
Line 1: Line 1:
 ====== Lab Tests ====== ====== Lab Tests ======
  
-[[https://www.cse.yorku.ca/~roumani/course/4413/labtest2/LT2.html|{{44test.jpg|}}]]+[[https://www.cse.yorku.ca/~roumani/course/4413/labtest3/eSubmit.cgi|{{44test.jpg|}}]]
  
 ====== Lab Test #1 ====== ====== Lab Test #1 ======
 +
 +
  
  
 ===== Policies ===== ===== Policies =====
  
-    * The test is 80-min long and will be held at 11:30 am on Thu Oct. 4 in Prism.+    * The test is 80-min long and will be held in Prism.
     * Bring a photo ID.     * Bring a photo ID.
     * No questions are allowed during the test.     * No questions are allowed during the test.
Line 27: Line 29:
  
  
-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 will lead to lower marks because (1) you will lose the marks allocated for the answer, and (2) your program may have errors or shortcomings that would have been identified had you compiled and ran your code. You must therefore manage your time carefully to achieve an optimal trade off.+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 will lead to lower marks because (1) you will lose the marks allocated for the answer, and (2) 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 ===== ===== Preparation =====
Line 34: Line 36:
  
 ====== Lab Test #2 ====== ====== Lab Test #2 ======
 +
 +
  
  
 ===== Policies ===== ===== Policies =====
  
-    * The test is 80-min long and will be held at 11:30 am on Thu Nov. 1st in Prism.+    * The test is 80-min long and will be held in Prism.
     * Bring a photo ID.     * Bring a photo ID.
     * No questions are allowed during the test.     * No questions are allowed during the test.
     * Seating may be preassigned and there may be several test versions.     * Seating may be preassigned and there may be several test versions.
     * The test is open-book in the sense that you have full access to your home directory, this course site, and indeed the whole Internet.     * The test is open-book in the sense that you have full access to your home directory, this course site, and indeed the whole Internet.
 +
  
  
 ===== Scope =====   ===== Scope =====  
  
-The test will cover everything that was covered after Lab Test#1. This includes CSS, Servlets, MVC/JSP, and XML technologies. Notehowever, that XSL is not required in this test, i.e. if you are asked to transform XML you can do it using a Java program or XSL. +The test will cover everything that was covered after Lab Test#1. This includes CSS, Servlets, MVC/JSP, and XML technologies, including XSL. 
  
 ===== Format ===== ===== Format =====
Line 57: Line 61:
   - The method by which you obtained the answer (a program or a procedure)    - The method by which you obtained the answer (a program or a procedure) 
  
-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 will lead to lower marks because (1) you will lose the marks allocated for the answer, and (2) your program may have errors or shortcomings that would have been identified had you compiled and ran your code. You must therefore manage your time carefully to achieve an optimal trade off.+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 will lead to lower marks because (1) you will lose the marks allocated for the answer, and (2) 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 ===== ===== Preparation =====
  
 The best way to prepare for the test is to do the labs. Indeed, you are assumed to have reviewed your lab programs before the test and stored them in your home directory. This way, you can easily and quickly adapt them during the test to solve the test questions.  The best way to prepare for the test is to do the labs. Indeed, you are assumed to have reviewed your lab programs before the test and stored them in your home directory. This way, you can easily and quickly adapt them during the test to solve the test questions. 
 +
 +
 +====== Lab Test #3 ======
 +
 +
 +
 +===== Policies =====
 +
 +    * The test is 120-min long and will be held in Prism.
 +    * Bring a photo ID.
 +    * No questions are allowed during the test.
 +    * Seating may be preassigned and there may be several test versions.
 +    * The test is open-book in the sense that you have full access to your home directory, this course site, and indeed the whole Internet.
 +
 +===== Scope =====  
 +
 +The test will cover XML technologies plus everything that was covered after Lab Test#2. This includes XML/XSL, JavaScript, Web Services, and Cryptography.
 +
 +===== 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 obtain an answer. You submit two things:
 +
 +  - The answer you obtained
 +  - The method by which you obtained the answer (a program or a procedure) 
 +
 +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 will lead to lower marks because (1) you will lose the marks allocated for the answer, and (2) 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 =====
 +
 +Go over the lectures notes and the assigned readings from the textbook. In addition, examine and enhance the related programs in the //Resource Directory//.
tests.1193881922.txt.gz · Last modified: 2007/11/01 01:52 by roumani

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki