ENGR 201
Systems Engineering
Description: Lecture, four hours; outside study, eight hours. Designed for graduate students. Practical review of major elements of system engineering process. Coverage of key elements: system requirements and flow down, product development cycle, functional analysis, system synthesis and trade studies, budget allocations, risk management metrics, review and audit activities and documentation. Letter grading.
Units: 4.0
Units: 4.0
1 of 1
Most Helpful Review
Fall 2024 - If you're a working professional, be careful, as this class is pretty labor intensive. There are two homework assignments a week, and pretty much all of them are reading a chapter from one of the two textbooks, then writing a 1 page summary and connect the concepts to your work experience. It may not sound bad, but it gets very tedious very fast, and some of the chapters can be quite long, so two a week can be really hard to keep up with. The exams are based mainly around lecture content (with maybe one multiple choice question from the readings), and the lectures are pretty long. Also, because the homework is all reading and summarizing, there's no real way to get practice/feedback on the activities we're expected to do on the exam (such as making Functional Flow Block Diagrams, writing functional/non-functional requirements, defining measures of effectiveness, etc). There is also an individual assignment and group assignment that are assigned after the midterm, and they expect you to have weekly team meetings. The grading is pretty generous, so an A is almost guaranteed as long as you put in the effort to do the work, but the sheer amount of busywork involved in this class would have turned me away from taking it if I had known beforehand.
Fall 2024 - If you're a working professional, be careful, as this class is pretty labor intensive. There are two homework assignments a week, and pretty much all of them are reading a chapter from one of the two textbooks, then writing a 1 page summary and connect the concepts to your work experience. It may not sound bad, but it gets very tedious very fast, and some of the chapters can be quite long, so two a week can be really hard to keep up with. The exams are based mainly around lecture content (with maybe one multiple choice question from the readings), and the lectures are pretty long. Also, because the homework is all reading and summarizing, there's no real way to get practice/feedback on the activities we're expected to do on the exam (such as making Functional Flow Block Diagrams, writing functional/non-functional requirements, defining measures of effectiveness, etc). There is also an individual assignment and group assignment that are assigned after the midterm, and they expect you to have weekly team meetings. The grading is pretty generous, so an A is almost guaranteed as long as you put in the effort to do the work, but the sheer amount of busywork involved in this class would have turned me away from taking it if I had known beforehand.
AD
1 of 1
