uclagrades.com

ENGR 212: Intellectual Property Law and Strategy

Prior knowledge of legal doctrines or materials not required. Intellectual property law is not just topic for lawyers. Engineers who have design responsibilities must understand how legal system in some instances protects their designs and in other instances stands as obstacle to what would otherwise be most efficient design choice. Engineers with management responsibilities must understand intellectual property law implications for everything from pricing to strategic partnerships. Examination of intellectual property law, not only by learning fundamental rules associated with patent, copyright, trademark, and trade secret protection, but by studying business strategies that these rules support. Examples and case studies to be taken from across content, technology, and pharmaceutical industries.

4 units, lecture

Loading...

DOUGLAS G LICHTMANSpring 20243691.7% (33)
DOUG G LICHTMANSpring 20268169.1% (56)

A-range % and grade counts cover only each instructor’s latest recorded term, shown in the "Latest Data From" column, combining all sections for the course. A-range % is the share of recorded letter grades (A+ through F) that are A+, A, or A−. Parentheses show the A-range count over the total letter-grade count. P/NP and incompletes are excluded. Records may be incomplete.

Available Academic Terms
Spring 2022 · Spring 2023 · Spring 2024 · Spring 2025 · Spring 2026

This website is not affiliated with UCLA. Grade distribution data from 2021–2022 was sourced through a February 2023 public records request made under the California Public Records Act. 40+ UCLA students paid $131.25 to obtain these records. Grade distribution data from 2022–2023 and 2024–2025 were sourced similarly.

UCLA students can download the data on Google Drive (log into your UCLA Google Account to access): Fall 2021–Summer 2022, Fall 2022–Spring 2023, Summer 2023–Spring 2024, Summer 2024–Spring 2025, Summer 2025–Fall 2025, Winter 2026–Spring 2026

Source code for this site is on GitHub; contributions are welcome and appreciated. Questions, comments, bug reports, and feature requests are welcome at this link.