Syllabus

Common Questions

Course Description

The software engineering landscape is shifting rapidly, and this course is designed to ensure you're leading the charge. In AI-Assisted Software Development and Intelligent Applications, you will master the two most critical skills for the modern developer: using AI to supercharge your own productivity and engineering the next generation of AI-powered software. We will dive deep into full-stack development, showing you how to leverage AI tools across the entire software life cycle — from initial system design and rapid coding to automated testing and cloud deployment — while teaching you how to architect and integrate intelligent models directly into your own applications. By the end of the term, you won't just be a faster coder; you will be a high-level engineer capable of building complex, AI-native systems from the ground up.

Official Course Description: This course examines the dual role of artificial intelligence in modern software development: as a transformative tool for developer productivity and as a core architectural component of next-generation software. Students will master AI-assisted development workflows to optimize the entire software development life cycle, leveraging intelligent tools for requirements analysis, code generation, debugging, and automated testing. The course provides rigorous, hands-on experience in full-stack development, teaching students how to architect and integrate large language models (LLMs) and AI agents into scalable applications. By utilizing industry-standard tools for version control, CI/CD, and cloud deployment, students will gain a comprehensive understanding of building, managing, and maintaining AI-native software at every stage of its life cycle.

Additions To Syllabus Made During Semester

Course Learning Outcomes

By the end of the course, students should be able to:

Course Instructors

Prerequisites

CS 200 and CS 300 required. Students should have taken or be concurrently enrolled in CS 400.

Course Credits

Lectures (Meeting Time and Location)

Lecture recordings will not be provided. In-person attendance is expected.

Instructional Modality

Computer & Tool Expectations

Communication Tools

  1. Canvas: Grades and announcements are posted on Canvas.
  2. Email: Please attend office hours with questions before emailing instructors.
  3. Office Hours:
    • Louis Oliphant: Tuesday 2:30–3:30 PM, Wednesday 10–11 AM, Thursday 11 AM–12 PM, all in Morgridge Hall 5538.
    • Kaiser Pister: After class, Monday and Wednesday, in Morgridge Hall 5534.
    • Teaching Assistants: held at the tables just outside Morgridge Hall room 5538. TA hours vary week to week — see Tools → Scheduler (scheduler.hub.cs.wisc.edu (opens in new tab)) for this week's schedule and location.

Grading Breakdown

Your overall grade is based on the following:

Graded Component Details

Quizzes: Lecture Activities: Projects: Exams:

AI Use Policy

This course takes the opposite stance from most CS courses: Claude Code is a required, expected tool on every project. You are not just permitted to use AI — you are expected to use it as your primary development driver, the same way you'd use a compiler or a debugger.

The line we care about isn't "did you use AI." It's: can you explain, defend, and verify what it produced? This is the whole point of the Elephant-Goldfish Model workflow taught starting in Lecture 4 — design docs written before any code, a "Goldfish test" where a fresh AI session with no context has to be able to understand your design from your documentation alone, and a "mean code review" where you direct AI to tear apart your own finished code looking for problems. These exist so you demonstrate real understanding of what gets built, not just submit whatever the model outputs first.

Acceptable: using Claude Code (or another AI tool) to design, implement, debug, test, and review your project code, provided you can explain how it works, why it was built that way, and what its limitations are if asked in office hours or during a code review; and logging your AI sessions as required for each project.

NOT Acceptable: submitting AI-generated code you cannot explain, defend, or reproduce the reasoning behind; using AI on quizzes or written exams (which are closed-AI, closed-book); having a non-partner (human or AI acting on their behalf) do your share of a paired project's work; failing to log your AI sessions as required.

Using AI in a way that violates this policy is academic dishonesty, even though AI usage itself is expected and required in this course.

Academic Integrity

Standard UW-Madison academic integrity policy applies. The AI Use Policy above supplements it for AI-specific scenarios in this course.

Letter Grades

At the end of the semester, we will assign final grades based on these thresholds:

Letter grade ranges include decimal points; we round scores to the hundredths place at the end of the semester.

No extra credit is given in this course.

How to Succeed in This Course

The best way to succeed in this course would be to:

Accommodations

Please notify the instructor within the first two weeks of classes:

Please notify your instructor if you suffer from an extended (> 12 days) illness.

Student Grievance Procedure

Any student at UW–Madison who feels that they have been treated unfairly has the right to voice a complaint and receive a prompt hearing of the grievance. The basis for a grievance can range from something as subtle as miscommunication to the extreme of harassment.

Ensuring that all students feel welcome and supported is a top priority of our department. The Department of Computer Sciences has developed procedures to handle complaints or incidents that are student-related, such as bias or mistreatment, or academic, such as a grade dispute or incident with an instructor. Information on the CS reporting procedures can be found here: https://www.cs.wisc.edu/report-an-incident/.

For assistance in determining options, students can also contact the drop-in staff member within the Dean of Students Office at 608-263-5700, within Bascom Hall, Room 70, Monday–Friday, 8:30 a.m.–4 p.m.

Official Statements Required on the Syllabus

Requisites

CS 200 and CS 300 required. Students may be concurrently enrolled in CS 400, or may have already completed it.

Regular and Substantive Student-Instructor Interaction: Substantive interaction is engaging students in teaching, learning and assessment through at least two of the following: direct instruction, providing feedback on student work, providing information about course content, facilitating discussion of course content, or other substantive interaction. Regular interaction is: predictable and scheduled interaction with students consistent with the course length (usually at least weekly but more often in a course of short duration). Regular and substantive student-instructor interaction, as defined by the US Department of Education (Within 34 C.F.R. §600.2), is always a requirement of UW-Madison for-credit learning activities.

Course Evaluations: UW-Madison now uses an online course evaluation survey tool. In most instances, you will receive an official email two weeks prior to the end of the semester when your course evaluation is available. You will receive a link to log into the course evaluation with your NetID where you can complete the evaluation and submit it, anonymously. Your participation is an integral component of this course, and your feedback is important to me. I strongly encourage you to participate in the course evaluation.

Academic Integrity: By virtue of enrollment, each student agrees to uphold the high academic standards of the University of Wisconsin-Madison; academic misconduct is behavior that negatively impacts the integrity of the institution. Cheating, fabrication, plagiarism, unauthorized collaboration, and helping others commit these previously listed acts are examples of misconduct which may result in disciplinary action. Examples of disciplinary action include, but is not limited to, failure on the assignment/course, written reprimand, disciplinary probation, suspension, or expulsion.

Accommodations for Students with Disabilities: The University of Wisconsin-Madison supports the right of all enrolled students to a full and equal educational opportunity. The Americans with Disabilities Act (ADA), Wisconsin State Statute (36.12), and UW-Madison policy (Faculty Document 1071) require that students with disabilities be reasonably accommodated in instruction and campus life. Reasonable accommodations for students with disabilities is a shared faculty and student responsibility. Students are expected to inform faculty [instructors] of their need for instructional accommodations by the end of the third week of the semester, or as soon as possible after a disability has been incurred or recognized. Faculty will work either directly with the student [you] or in coordination with the McBurney Center to identify and provide reasonable instructional accommodations. Disability information, including instructional accommodations as part of a student's educational record, is confidential and protected under FERPA.

Diversity and Inclusion: Diversity is a source of strength, creativity, and innovation for UW-Madison. We value the contributions of each person and respect the profound ways their identity, culture, background, experience, status, abilities, and opinion enrich the university community. We commit ourselves to the pursuit of excellence in teaching, research, outreach, and diversity as inextricably linked goals. The University of Wisconsin-Madison fulfills its public mission by creating a welcoming and inclusive community for people from every background – people who as students, faculty, and staff serve Wisconsin and the world.