IT 432
Spring 2025
Craig Miller
- Home
- Basic Information
- Grades and Policies
- Schedule
Weekly Notes
Assignments
- Assignment 1
- Assignment 2
- Assignment 3
- Assignment 4
- Midterm Report
- Assignment 5
- Assignment 6
- Culminating Project
- Final Report
Grade Determination
| Assignment | Weight |
|---|---|
| Six preparatory assignments (10 points each) | 30% (60 points) |
| Weekly Experience Summaries | 10% (20 points) |
| Midterm Report | 10% (20 points) |
| Culminating assignment | 20% (40 points) |
| Summary Report | 30% (60 points) |
Students receiving more than 90% of possible points are guaranteed at least an A-, more than 80% at least a B-, more than 70% at least a C-, and more than 60% at least a D.
The weekly experience summaries are posted accounts of work reviewing the weekly content. They are posted on D2L.
The preparatory assignments occur on a weekly basis for the first 7 weeks of class.
The culminating assignment is a more open-ended assignment that captures the major concepts of the course. It is due the final (10th) week of class.
The summary report is a submission due during final week. It includes original explanations, reflections or experiences on the major concepts for the course. It takes the place of a final exam.
The midterm report is a reduced version of the summary report focussing on one concept.
All assignments and reports must consist of original, individual work.
Policies
Students are expected to attend weekly (in person or by zoom). However, asynchronous attendance (watching recordings) will be supported on an as-needed basis.
Registration in the on-campus section requires a minimum attendance of 3 sessions in person. Registration in the synchronous (flex) session requires a minimum attendance of 3 sessions by zoom. For those with a time conflict, an alternate meeting time during the week can be arranged.
Failure to achieve the minimum attendance will result in a drop of a whole grade for each absence less than the minimum.
The goal of the labs is to practice concepts taught in the class. Submissions must have code that use constructs and conventions taught in class. Code with other constructs and conventions, such as that offered by online resources and AI agents, are subject to receiving no credit.
You are expected to do your own assignments. However, some collaboration with other students is allowed and even encouraged. The following types of collaboration are allowed:
- Discussing strategies for solving a problem
- Explaining why a Web page does not work
- Reviewing and testing someone else's Web pages
- Using HTML and JavaScript code provided by the instructor and texts
The following types of collaboration and copying are not allowed:
- Copying someone else's JavaScript code
- Copying code from an online source including an AI agent
- Literally telling someone what code to write
Engaging in these last two types of collaboration will be considered a violation of the university's policy on academic integrity. Violators will receive a 0 for the corresponding assignment and will be reported as required by the policy.
Late assignments will be accepted up to three days late with a one point penalty. Assignments submitted more than 3 days after the due date will not be accepted without documentation of a serious emergency.
Additional assignments for extra credit will not be offered.
All grade challenges must be submitted in writing and include an explanation why the given score or grade should be reconsidered.