Continuation Syllabus
AI Usage Policy
1. Purpose of This Policy This policy defines acceptable and unacceptable uses of Artificial Intelligence (AI) tools (e.g., generative AI, code assistants, large language models) in this course. The goal is to:
(a) Support learning and skill development
(b) Preserve academic integrity
(c) Align with professional computing ethics
(d) Meet accreditation expectations
2. Overview of the Tiered AI Policy
AI use in this course is organized into four tiers, based on the size and stakes of the work and how much it needs to visibly reflect your own understanding. The core stance is simple: Use AI freely to build. Prove you understand it to submit.
Tier 1 covers open-ended learning support and carries no restrictions. Tier 2 covers routine, smaller graded work — homework and labs — where a brief acknowledgment is enough. Tier 3 covers larger, higher-stakes work — substantial AI-analysis assignments and projects — where AI use must be disclosed through a short video and may be followed up with a graded oral interview. Tier 4 covers quizzes and exams: no AI tools are permitted, and this is enforced technically, not just on paper. The sections below explain each tier in detail.
Tier | Status | What it covers |
Tier 1 | Fully open — no restric- tion | Conceptual explanation, debugging help, documentation support, and brainstorming. Always allowed, with no disclosure requirement. |
Tier 2 | Open, ac- knowledg- ment only | Routine homework (theory and programming) and labs. AI may gener- ate, refactor, or help debug code, provided the student includes a brief written acknowledgment at submission. No video or oral interview is required by default, though either may still be requested (Section 8). |
Tier 3 | Open, with disclosure + explanation | Larger homework, substantial AI-analysis assignments, and large/capstone projects. AI may generate, refactor, test, or ana- lyze code, provided the student submits a disclosure video and can pass a graded oral interview on the work. |
Tier 4 | Closed — no AI tools | All quizzes and exams. No AI tools of any kind. Enforced technically via Respondus LockDown Browser (or equivalent), not just stated in the syllabus. |
3. Guiding Principles
This policy is designed to support learning, fairness, and professional responsibility. The guiding principles are:
(a) Students must demonstrate their own understanding of the core concepts of the course
(b) AI tools should support learning, not replace thinking or implementation
(c) Students are responsible for all submitted work
(d) Transparency about AI use is required, scaled to the size of the work
(e) Professional Responsibility Students are expected to:
i. Be honest about the use of AI tools
ii. Understand and verify any AI-assisted output
iii. Accept responsibility for submitted work
iv. Using AI without understanding its output violates professional computing ethics.
(a) Transparency and Attribution Any Tier 2 or Tier 3 use of AI must be disclosed at submission — a brief written acknowledgment for Tier 2 (Section 5), a full disclosure video for Tier 3 (Section 6). Undisclosed use of AI is treated as an academic integrity violation, regardless of the work’s tier.
4. Verification and Accountability Oral interviews are conducted by faculty as needed, not on a
fixed schedule, and may apply to any Tier 2 or Tier 3 submission — though they are most likely for
Tier 3 work given its higher stakes. Students are responsible for:
(a) Explaining their submitted code line-by-line if asked
(b) Demonstrating understanding during oral checks or demos
(c) Correcting errors caused by AI misuse
Instructors may:
(a) Request live explanations
(b) Use code similarity analysis
(c) Conduct oral interviews or practical assessments, including the graded oral interview described
in Sections 5.2 and 6.2
5. Tier 1 — Fully Open (No Restriction) Tier 1 covers uses of AI that build understanding
rather than produce graded deliverables. These uses are always allowed, require no disclosure, and
are not restricted in any way.
(a) Conceptual Understanding
i. Explaining concepts (e.g., PCB fields, process states, process scheduling, linked lists)
ii. Clarifying lecture topics
(b) Debugging Assistance
i. Identifying compiler errors or warnings
ii. Explaining code
iii. Suggesting debugging strategies
(c) Documentation Support
i. Improving clarity of comments written by the student
ii. Formatting reports or lab write-ups
(d) Brainstorming Exploring approaches, design alternatives, or study strategies
6. Tier 2 — Open, Acknowledgment Only Tier 2 covers routine, smaller graded work: homework (theory and programming) and labs. AI tools may be used to generate, refactor, or help debug code. This tier is deliberately lighter-weight than Tier 3 — it exists so that small, everyday assignments don’t carry the same overhead as a major project, and so that AI use stays sustainable and equitable across a full course load.
(a) Condition — Brief Acknowledgment Every Tier 2 submission must include a short written
acknowledgment that AI was used, and roughly how. No video is required. Example acknowl-
edgment statement to include in the submission:
“I used an AI tool to help draft/debug this solution. I reviewed and understood the resulting code before submitting it.”
A submission with no acknowledgment where AI was in fact used is treated as an academic
integrity violation, the same as undisclosed AI use at any other tier.
(b) No Video Required, but Not Exempt from Accountability Tier 2 does not require
a disclosure video by default. However, Tier 2 work is not exempt from verification: faculty
may still request a live explanation or select a Tier 2 submission for the graded oral interview
described in Section 8, as needed.
7. Tier 3 — Open, with Disclosure + Explanation Tier 3 covers larger, higher-stakes work: substantial AI-analysis assignments and large or capstone projects. AI tools may be used to generate, refactor, test, or analyze code. This openness comes with two conditions that apply to every Tier 3 submission.
(a) Condition 1 — Disclosure Video Every Tier 3 submission must be accompanied by a short
video explaining the submitted work: what was done, what AI contributed, and why it works.
Length scales with the size of the assignment:
i. Substantial AI-analysis assignments: roughly 2–3 minutes
ii. Large/capstone projects: up to 5 minutes, covering the goal and decomposition, the hardest
component, and a line-by-line walkthrough
Example disclosure statement to include in the video or accompanying notes:
“I used an AI tool to help explain concepts and debug errors. All code and explanations were
reviewed, modified, and understood by me.”
(b) Condition 2 — Oral Interview (Graded, Standing Category) Faculty may call any
student in for a short oral interview on any Tier 3 submission, as needed — not on a fixed
schedule. This is its own assessed component, not merely a disciplinary check, and applies
whether or not AI was used.
A student who cannot explain their own submitted work is treated as not having met the
assignment’s goal, independent of how the work was produced.
8. Tier 4 — Closed (No AI Tools) Tier 4 covers quizzes and exams. No AI tools are permitted
under any circumstances.
(a) Respondus LockDown Browser (or equivalent) is required for 112, 113, and 214
(b) This makes the restriction technically enforced, not just a statement in the syllabus
(c) Using AI tools during a Tier 4 assessment is treated as academic misconduct
9. Rationale This policy reflects real-world expectations in computing and engineering:
(a) Tools may assist professionals
(b) Professionals must understand, validate, and take responsibility for results The four-tier structure also keeps the policy sustainable and equitable in practice: not every assignment needs the same overhead. Reserving the full disclosure video for larger, higher-stakes work keeps the requirement meaningful rather than routine, and keeps the total workload — for students producing videos and for faculty reviewing them — realistic across a full semester. Over-reliance on AI undermines learning and weakens preparation for advanced courses and professional practice.
10. Consequences of Policy Violations Violations may result in:
(a) Reduced or zero credit
(b) Academic integrity reports
(c) Disciplinary action per university policy
11. Student Acknowledgment By enrolling in this course, students acknowledge that they:
(a) Have read and understood this AI usage policy
(b) Agree to comply with its terms
(c) Accept responsibility for their learning and professional conduct
FAQ
1. Can I use ChatGPT or similar tools in this course? Yes. Tier 1 uses (concept explanation,
debugging help, documentation support, brainstorming) are always allowed with no restriction.
Tier 2 uses (routine homework, labs) are allowed with a brief written acknowledgment. Tier 3
uses (substantial AI-analysis assignments, large projects) are allowed with a disclosure video and
possible oral interview. Tier 4 (quizzes and exams) never allows AI tools.
2. Can I ask AI to write code for my assessments? It depends on the tier. For Tier 2
work (routine homework, labs), AI may generate or help debug code, but you must include a brief
acknowledgment. For Tier 3 work (substantial AI-analysis assignments, large projects), AI may
generate, refactor, test, or analyze code, but you must submit a disclosure video and be able to
explain the work if called for an oral interview. For Tier 4 assessments (quizzes and exams), no
AI-generated code or answers are allowed at all.
3. Can I use AI to debug my program? Yes. Light debugging help (interpreting compiler
errors, understanding segmentation faults, suggesting strategies) is a Tier 1 use with no restriction.
If AI substantially helps produce or repair a graded submission, that submission falls under Tier 2
or Tier 3 depending on its size, and the corresponding acknowledgment or disclosure requirement
applies. You must still understand and fix the problem yourself.
4. Do I need to disclose AI use, and how? It depends on the tier. Tier 2 requires a brief written acknowledgment at submission — no video. Tier 3 requires a short disclosure video explaining what was done, what AI contributed, and why it works: roughly 2–3 minutes for substantial AI-analysis assignments, up to 5 minutes for large projects. Tier 1 use requires no disclosure at all.
5. Can I use AI during quizzes or exams? No. Quizzes and exams are Tier 4 — closed to all
AI tools in every course — and this is enforced with Respondus LockDown Browser (or equivalent)
rather than left to the honor system.
6. What happens if I submit AI-generated work without the required acknowledgment or
disclosure, or use AI on a Tier 4 assessment? All of these are treated as academic integrity
violations and may result in zero credit or further disciplinary action per university policy.
7. What is the graded oral interview, and is it just a disciplinary check? It is a standing,
graded assessment component for Tier 2 and Tier 3 work, not merely a disciplinary check. Faculty
may call any student in for a short oral interview on any such submission, as needed — there is no
fixed schedule. If you cannot explain your own submitted work, you are treated as not having met
the assignment’s goal, regardless of how the work was produced.
8. Why is this policy structured in four tiers instead of three? The extra tier separates
routine work from higher-stakes work. Tier 1 keeps the door wide open for AI as a learning aid.
Tier 2 lets you use AI on everyday homework and labs with a light, low-overhead acknowledgment
— keeping the workload realistic for both students and faculty. Tier 3 reserves the fuller disclosure
video and oral-interview accountability for the work that actually carries that weight: substantial
AI-analysis assignments and large projects. Tier 4 keeps quizzes and exams as a clean, verified
measure of what you know without AI assistance.
Key Takeaway
1. AI is a learning aid, not a replacement for you.
2. You are expected to use AI tools responsibly, transparently, and in ways that support — not replace
— your understanding of Computer Science.
3. Our goal is to prepare you for better jobs, not to fail you in your life.
Rubric for programming assignment
Technical Dimen- sions/Weight | Exceeds Expectations (8-10) | Meets Expectations (4-7) | Does not Meet Expecta- tions (1-3) |
Functionality 30% | Program fully functional, meets all requirements. | Program mostly func- tional, meets most requirements. | Program not functional, fails to meet requirements. |
Code Quality 15% | Well-organized, clear, and efficient code. | Mostly organized and readable code. | Disorganized, unreadable code. |
Documentation 10% | Thorough comments ex- plaining code logic and us- age. | Some comments explain- ing code logic and usage. | Minimal or no comments. |
Problem Solving 35% | Effective problem-solving approach. | Reasonable problem- solving attempt. | Ineffective or no problem- solving attempt. |
Testing 10% | Comprehensive testing with clear results. | Some testing with reason- able results. | No testing conducted. |
Rubric for team project
Technical Dimen- sions/Weight | Exceeds Expectations (8-10) | Meets Expectations (4-7) | Does not Meet Expecta- tions (1-3) |
Collaboration 20% | Effective collaboration among team members. Good communication, active participation, and adequate delegation. | Reasonable collaboration among team members. Some communication, participation, and delega- tion efforts. | Poor collaboration among team members. Mini- mal communication, par- ticipation, and delegation. |
Quality of Work 25% | High quality of work evi- dent in most aspects of the project. Deliverables meet or slightly exceed expecta- tions. | Satisfactory quality of work evident in key aspects of the project. Deliverables generally meet expectations. | Poor quality of work evi- dent in most aspects of the project. Deliverables fall significantly short of ex- pectations. |
Presentation 15% | Strong presentation skills. Information is conveyed with clarity and engage- ment. | Adequate presentation skills. Information is conveyed reasonably well. | Poor presentation skills. Information is unclear, disorganized, and unen- gaging. |
Outcome 40% | Strong final outcome achieved. Project goals largely met, and all key deliverables completed. | Satisfactory final outcome achieved. Project goals mostly met, with minor deliverables incomplete. | Poor final outcome achieved. Project goals not met, with numerous deliverables incomplete. |
Rubric for theoretical assignment
Technical Dimen- sions/Weight | Exceeds Expectations (8-10) | Meets Expectations (4-7) | Does not Meet Expecta- tions (1-3) |
Overview 30% | Provides an engaging overview, thoroughly de- fines the scope, and gives a clear sense of purpose | Provides an adequate overview and a general explanation of the scope. Gives a reasonable sense of purpose | Fails to provide an overview and define the scope. Fails to give a reasonable sense of purpose |
Concepts, Reason- ing 25% | Ideas and concepts are logical and work together as a unified whole. Main points are supported with specific evidence. | Main concepts and ideas are visible but not always logical and/or too broad. Support for main points is given but not always suffi- cient and/or focused. | Confused about assign- ment and relevant con- cepts. Lack of support for main points. Illogical pre- sentation of ideas |
Soundness 25% | All necessary analysis and/or sources of infor- mation are clearly stated. All results and references are valid, reliable, spe- cific, and relevant to the assignment | Sufficient information and/or analysis is given but results are not always credible, reliable and/or relevant to the assignment | Analysis and/or sources of information are not clearly specified, not reli- able and/or not relevant to the assignment |
Completeness 20% | Followed all directions and responded to all parts of the assignment. Work is self-contained and com- plete with respect to the stated scope | Most of the directions are followed and most parts of the assignment are ad- dressed. Work covers most of the stated scope and is reasonably self- contained and complete. | Directions are not fol- lowed and/or work is in- complete and does not ad- dress one or more of the points necessary to treat the given topic |
Originality 15% | Content clearly displays evidence of independent and critical thinking | Some ideas display capa- bility of independent and critical thinking or per- spective | Ideas are unrefined and/or fail to demonstrate in- dependent and critical thinking |
Rubric for Quiz
Technical Dimen- sions/Weight | Exceeds Expectations (8-10) | Meets Expectations (4-7) | Does not Meet Expecta- tions (1-3) |
Accuracy 30% | All answers are correct. | Most answers are correct. | Few or no correct answers. |
Completeness 30% | All questions are an- swered. | Most questions are an- swered. | Few questions are an- swered. |
Understanding 30% | Demonstrates a thorough understanding of the ma- terial. | Shows understanding of most concepts. | Lacks understanding of concepts. |
Neatness 10% | Neatly organized and easy to read. | Mostly organized and leg- ible. | Disorganized and hard to read. |
Academic Calender: See next pages
Fall 2026 Semester |
First Day of Classes (15 week and 1st 7-week session) |
Monday, August 24 |
Last Day to Add/Drop Courses (1st 7-week session) |
Friday, August 28 |
Last Day to Add/Drop Courses (15-week session) |
Friday, September 4 |
Labor Day Holiday (No classes) |
Monday, September 7 |
Fall 2026 Convocation |
Wednesday, September 9 |
Last Day to Withdraw with a grade of ‘W’ or Audit a course (1st Friday, September 18
7-week session)
Last Day to Remove Spring 2026 Incomplete Grades for |
Friday, October 2 |
Undergraduates |
Last Day to Apply for Fall (December) 2026 Graduation |
Friday, October 2 |
Graduate Comprehensive Exam |
Saturday, October 3 |
Last Day of the 1st 7-week session Friday, October 9
*Last Saturday class for 1st 7-week session Saturday, October 10
Dean’s List Celebration Saturday, October 10
Midterm Evaluation for Undergraduate Students Monday, October 12 thru Friday, October 16
2nd 7-week Session Begins Monday, October 12
Final grades due for 1st 7-week session Wednesday, October 14
Last Day to Add/Drop Courses (2nd 7-week session) Friday, October 16
Midterm grades due for Undergraduate Students Wednesday, October 21
Undergraduate Advising for Freshmen and Sophomore |
Students (under 60 credits in the Academic Advising Center; |
Monday, October 26 – Wednesday, |
excluding these majors – COSC/CTEC/ENGL/NURS/SOWK) |
December 8 |
Undergraduate Advising for Undergraduate Students with 60 |
or more credits. |
Success fest Wednesday, October 28
Last Day to Withdraw with a grade of ‘W’ or Audit a Course |
(15-week session) |
Friday, October 30 |
Winter and Spring 2027 Registration Opens |
Wednesday, November 4 |
Last Day to Withdraw with a grade of ‘W’ or Audit a Course |
(2 |
nd |
7-week session) |
Friday, November 6 |
Thanksgiving Break (No classes) |
Wednesday, November 25 - Friday, |
November 27 |
Classes Resume |
Monday, November 30 |
Last Day of Classes (2nd |
7-week session) |
Friday, December 4 |
Last Saturday Class (15-week and 2 |
nd |
7-week session) |
Saturday, December 5 |
Last Day of Classes (15-week session) |
Monday, December 7 |
Final Examinations begin (for all undergraduate students) |
Tuesday, December 8 |
Final grades due for 2 |
nd |
7-week session |
Wednesday, December 9 |
Last Day to change Fall 2025 Incomplete grades for Graduate |
students |
Friday, December 11 |
Last Day of Final Examinations and End of Term |
Monday, December 14 |
Final Grades Due for 15-week session by 11:59pm |
Thursday, December 17 |
Fall 2026 (December) Commencement Ceremony |
Friday, December 18