WIC

CS 462 is the Writing Intensive Course (WIC) of the capstone series. The WIC learning outcomes are evidenced by the same work that evidences the ABET ones, so you don’t write anything for WIC alone: the writing happens through ordinary software engineering activities, namely design decisions, sprint evidence, and reviews.

Learning Outcomes

Students in WIC courses will [1]:

1. Analyze disciplinary concepts through writing.
2. Create at least one original, extensive, and meaningful written work that adheres to disciplinary norms including specified audience, purpose, and genre.
3. Integrate feedback after critical evaluation during the revision process of written work.

How CS 462 Does the Writing

The extensive written work is the winter RFC: an individual design document argued from cited sources, written as a draft, reviewed in writing by two other students, and revised with a response-to-feedback note; its winter length floor is on the RFC page, and the instruction team grades the final against the rubric. Around it sits the informal writing: your contribution line and the team’s judgment layer in every sprint note, and your two written peer reviews. Where each outcome is evidenced, per student, is on the outcome mapping page.

References

[1] “WIC Learning Outcomes, Criteria, and Rationale | Writing Intensive Curriculum, Oregon State University.” Accessed: Sep. 15, 2026. [Online]. Available: https://wic.oregonstate.edu/propose-assess-wic-courses/wic-learning-outcomes-criteria-and-rationale