<p>hi guys, i am an incoming freshman majored in EECS. i am planning to start taking UD courses in my sorph year; however, on the "COLLEGE OF ENGINEERING UNDERGRADUATE POLICY SUMMARY", it says that "All students are expected to complete required lower-division courses before beginning upper-division work. Transfer students must complete lower-division requirements within the first two semesters after admission. Any student with junior level status must take any remaining lower or upper division technical courses at UC Berkeley." so does it mean i have to complete every single LD course that is required for the degree before i can start taking UD courses, or i can take it as long as i have completed all the prerequisites for that particular UD courses?</p>
<p>You can take the course as long as you have met the prereqs for that particular course. You don’t have to have taken every single lower division before taking a single upper division. This is actually what a lot of people do. To use EECS as an example, let’s say you’re more CS-inclined… You could complete CS61 series your first year (either by passing out of 61B or taking summer school) and be taking CS upper divs in your second year, while at the same time fulfilling your EE lower divs like EE20 and EE40 in second year.</p>
<p>
</p>
<p>
</p>
<p>Heck, you usually don’t even need to do that. The truth is, many prereqs are not actually necessary as you don’t really need to know the material of those prereqs, and nobody is really going to check anyway.</p>
<p>As an example, consider EE122 (Communications Networks). The prereqs include Math 53 or 54, but the truth is, you don’t actually need to know Math 53 or 54 for that class. Heck, that prereq listing gives it away: what kind of a prereq requirement is “Math 53 or 54” anyway? Math 53 and 54 are completely different classes, covering completely different topics. So how can you make a meaningful requirement for either/or? The answer is that you can’t - it’s a meaningless prereq. Furthermore, nobody is really going to check anyway.</p>
<p>oh i get it now, thanks for the replies</p>