User Tools

Site Tools


labtests

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
labtests [2010/10/20 19:21] roumanilabtests [2010/11/24 19:10] (current) roumani
Line 2: Line 2:
 ====== Lab Tests ====== ====== Lab Tests ======
  
-[[https://www.cse.yorku.ca/~roumani/course/4413/labtest1/q.html|{{44test.jpg|}}]]+[[https://www.cse.yorku.ca/~roumani/course/4413/labtest2/q.html|{{44test.jpg|}}]]
 <html><!-- <html><!--
 This page will be updated a few days before each labtest. This page will be updated a few days before each labtest.
 --></html> --></html>
  
-===== Lab Test #=====+===== Lab Test #=====
  
 ==== Policies ==== ==== Policies ====
Line 21: Line 21:
 ==== Scope ==== ==== Scope ====
  
-The test will cover projects 0 and 1.+The test scope include everything covered in class with the exception of CGI and Perl
  
 ==== Format ==== ==== Format ====
  
-The test involves adding features to the projects. You are expected to analyze the requirement, design a solution, implement it, and then submit it. You can base your development on our posted //reference implementations// or on your own implementations of the projects.+The test involves adding features to Project #2. You will first be asked to submit your implementation of of Project 2. Next, you will be asked to add a feature to the project or to modify a functionality in it. You are expected analyze the required change, 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. Your work is marked based on correctness and on meeting the various software engineering guidelines, design patterns, and best practices.
Line 33: Line 33:
 The best way to prepare for the test involves: The best way to prepare for the test involves:
  
-  * Reviewing the posted implementations +  * Reviewing the posted material 
-  * Reviewing the posted notes +  * Reviewing your own implementation of Project 2
-  * Reviewing the posted variations +
-  * Familiarization with the posted resources+
  
 <html><!-- <html><!--
-===== Lab Test #=====+===== Lab Test #=====
  
 ==== Policies ==== ==== Policies ====
  
-    * The test is 80-min long and will be held in Prism.+    * The test is 80-min long and will be held in **CSEB-3057**.
     * You will login to one of machine in the lab using your 8-character ''cs'' username.     * You will login to one of machine in the lab using your 8-character ''cs'' username.
     * Bring a photo ID.     * Bring a photo ID.
     * No questions are allowed during the test.     * No questions are allowed during the test.
     * You may not communicate with anyone, inside or outside the lab, by any mean 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 versionsand network traffic may be monitored.+    * There may be several test versionsand network traffic may be monitored.
     * 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.      * 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 ==== ==== Scope ====
  
-The test will cover everything up to the prior week. This means custom functions and tags (Lab #2), xml technologies, and Web Service clients+The test will cover projects 0 and 1.
  
 ==== Format ==== ==== Format ====
  
-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. +The test involves adding features to the projects. You are expected to analyze the requirement, design a solution, implement it, and then submit it. You can base your development on our posted //reference implementations// or on your own implementations of the projects. 
 Your work is marked based on correctness and on meeting the various software engineering guidelines, design patterns, and best practices. 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 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 involves: 
-</html>+ 
 +  * Reviewing the posted implementations 
 +  * Reviewing the posted notes 
 +  * Reviewing the posted variations 
 +  * Familiarization with the posted resources 
 + 
 +--></html>
  
labtests.1287602477.txt.gz · Last modified: 2010/10/20 19:21 by roumani

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki