CSE4413

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Lab Tests ======

[[https://www.cse.yorku.ca/~roumani/course/4413/F09/labtest2/q.html|{{44test.jpg|}}]]
<html><!--
===== Lab Test #1 =====

==== Policies ====

    * The test is 80-min long and will be held in Prism.
    * 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 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. 

==== Scope ====

The test will cover everything up to the prior week. This means up to beans, filters, and listeners.

==== Format ====

The test involves building a webapp that meets a given requirement. You are expected to analyze the requirement, design a solution, implement it, and then submit it. Specifically, you submit a ''war'' file of your webapp and it should include two things:

  * Source files
  * 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. 

==== Preparation ====

The best way to prepare for the test involves:

  * Completing the first Lab, L1, and its explorations
  * Reviewing the refinements done in lecture
  * Reading Chapters 1, 2, 6, and 8 in the textbook
  * 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" 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, 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>

===== Lab Test #2 =====

==== Policies ====

    * The test is 80-min long and will be held in Prism.
    * 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 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. 

==== 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. 

==== 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. 
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.