Peter Reiher
Department of Computer Science
AD
5.0
Overall Rating
Based on 1 User
Easiness 3.0 / 5 How easy the class is, 1 being extremely difficult and 5 being easy peasy.
Clarity 5.0 / 5 How clear the class is, 1 being extremely unclear and 5 being very clear.
Workload 2.0 / 5 How much workload the class is, 1 being extremely heavy and 5 being extremely light.
Helpfulness 5.0 / 5 How helpful the class is, 1 being not helpful at all and 5 being extremely helpful.

TOP TAGS

  • Tolerates Tardiness
  • Would Take Again
GRADE DISTRIBUTIONS
23.3%
19.4%
15.6%
11.7%
7.8%
3.9%
0.0%
A+
A
A-
B+
B
B-
C+
C
C-
D+
D
D-
F

Grade distributions are collected using data from the UCLA Registrar’s Office.

ENROLLMENT DISTRIBUTIONS
Clear marks

Sorry, no enrollment data is available.

AD

Reviews (1)

1 of 1
1 of 1
Add your review...
Quarter: Winter 2020
Grade: A
March 31, 2020

For Secure Software Development.

Truly a great class - it’s essentially CS 136 Part 2: practical project time. There are no exams, and few lectures. Most lectures are designated as team time - where you meet with your team and work on your project/reports.

The entire class revolves around proposing, designing, and building a piece of software in a secure fashion. You do this in a group of 4-5. Your grade is entirely based on the reports you write, and the project demo.

First, you write a short project proposal. Then, you write a detailed design document, mainly focusing on security. These are done in weeks 1 and 2, respectively. Then, you work on the project. You’re expected to complete the project by the end of Week 7, at which point you’ll demo it. Then, you conduct a security review of your project, and write a report on it. After that, you have a week to fix bugs/issues you found. From there, you do a security review of another team’s project, and write a report. Finally, you have one final report which details your final implemented design - including all the security fixes you made after your own security review.

It really is a great class. Reiher and the TAs are always available and willing to help, and encourage you to try new ideas and challenge yourself. It’s very much student-driven: it’s entirely up to you what you make, and how you split up your time building your app/service (procrastinate at your own peril). The only requirement Reiher makes for project proposals is that they have some significant security element (say, processing payments, or storing passwords).

I feel like this class and CS 136 should be mandatory for graduation - they’re that valuable in my opinion. 136 gives you baseline theoretical knowledge of computer security, and small practical applications in the labs. This 188 gives you a complete real-world experience in building a secure piece of software. Reiher is knowledgeable, helpful, and has put together a truly practical class. Take this if it ever is offered while you’re at UCLA.

Helpful?

0 0 Please log in to provide feedback.
Quarter: Winter 2020
Grade: A
March 31, 2020

For Secure Software Development.

Truly a great class - it’s essentially CS 136 Part 2: practical project time. There are no exams, and few lectures. Most lectures are designated as team time - where you meet with your team and work on your project/reports.

The entire class revolves around proposing, designing, and building a piece of software in a secure fashion. You do this in a group of 4-5. Your grade is entirely based on the reports you write, and the project demo.

First, you write a short project proposal. Then, you write a detailed design document, mainly focusing on security. These are done in weeks 1 and 2, respectively. Then, you work on the project. You’re expected to complete the project by the end of Week 7, at which point you’ll demo it. Then, you conduct a security review of your project, and write a report on it. After that, you have a week to fix bugs/issues you found. From there, you do a security review of another team’s project, and write a report. Finally, you have one final report which details your final implemented design - including all the security fixes you made after your own security review.

It really is a great class. Reiher and the TAs are always available and willing to help, and encourage you to try new ideas and challenge yourself. It’s very much student-driven: it’s entirely up to you what you make, and how you split up your time building your app/service (procrastinate at your own peril). The only requirement Reiher makes for project proposals is that they have some significant security element (say, processing payments, or storing passwords).

I feel like this class and CS 136 should be mandatory for graduation - they’re that valuable in my opinion. 136 gives you baseline theoretical knowledge of computer security, and small practical applications in the labs. This 188 gives you a complete real-world experience in building a secure piece of software. Reiher is knowledgeable, helpful, and has put together a truly practical class. Take this if it ever is offered while you’re at UCLA.

Helpful?

0 0 Please log in to provide feedback.
1 of 1
5.0
Overall Rating
Based on 1 User
Easiness 3.0 / 5 How easy the class is, 1 being extremely difficult and 5 being easy peasy.
Clarity 5.0 / 5 How clear the class is, 1 being extremely unclear and 5 being very clear.
Workload 2.0 / 5 How much workload the class is, 1 being extremely heavy and 5 being extremely light.
Helpfulness 5.0 / 5 How helpful the class is, 1 being not helpful at all and 5 being extremely helpful.

TOP TAGS

  • Tolerates Tardiness
    (1)
  • Would Take Again
    (1)
ADS