[Ownaginatios]

Software Engineering 2FA3 is the second semester part II to SFWR ENG 2DM3. Rather than 2DM3, which was more about the theory, 2FA3 is more about application of discrete mathematics to designing solid mathematically correct software.

Unlike most courses, this course starts out a little difficult, and then gets easy (it's even fun!).

The first thing learned is the very heavy math stuff - axioms. It's basically an extension of the stuff learned at the beginning of 2DM3. The axioms covered are mostly quantification axioms, which are useful for describing programs. Popular ones covered include the trading rule, range-split axiom and everything to do with FOR ALL and THERE EXISTS. Also differences between models, theories and formulas.

After that it moves on to mathematical induction (presented in a much easier-to-follow way than in 2DM3), some more set theory, well-foundedness, and then finally into mathematically writing a program using the hoare-triple layout. None of it is too difficult, but writing programs (especially with decisions and loops) has a steep learning curve. Once you get over that though, it's not too bad. Oh, and these programs aren't programs on a computer; they're equations. This course has no actual programming (aside from some bonus assignments).

Once that's all out of the way, the fun part comes - finite state automata, push down automata, pattern matching, and a brief touch on turing machines. Finite state automata is overlap with 2DA4, so they're not difficult to understand (it also overlaps with 2AA4 and 2MX3 a bit). Pushdown automata are not as intuitive... but also not too hard to follow.

The assignments are actually pretty fun for this stuff cause you get to be creative and design machines .

Anyway, the course breakdown is as follows:

Assignments 40% (10% each)
Midterm 20%
Final 40%

The first two assignments weren't too bad, but required a lot of thought. The last two were relatively easy. The midterm also wasn't too bad, but make sure you study hard for it.

The professor for this class is Dr. Ridha Khedri, and he's really good. All his slides are very organized and follow the book in such a way that it isn't just a rehash. One important thing you should know though is that Dr. Khedri isn't the kind of person you want to push around. If you are polite and respectful in his class, he'll respect you.

The exam (at least for my year) was very easy, that is, if you went to ALL classes and did ALL the assignments. The questions came directly from on the board examples and from the assignments.

Also, if you're good at programming, Dr. Khedri tends to give out small bonus assignments (i.e. make a simple program that can recognize patterns) every so often. They're usually worth an extra mark or two on the assignment or the midterm, so they're worth doing if you have time.

Good luck!

are the books required for this course? there are two books that the prof recommends... are both of these required or even one of them?

That really depends on your learning style. He does go over everything in class, but it can get tremendously boring at times and go right over your head.

The books are pretty much identical to his slides, except they go into much more detail. I found myself using them a lot since I tended to sleep through a lot of classes :p.

Aside from that, they're pretty interesting. I'd say it really depends on how you learn - if you feel just listening is good enough, then just take good notes and read the lecture slides. Otherwise get the books.

Also, Protip: If Khedri solves a problem on his slides make sure to write it down. His midterm/exam is pretty much just a rehash of those.

A lot has changed in the time this review has been posted. As the course has been taken over by Zucker, it is quite different from before.

Word of advice: get to know the prof. Do the extra homeworks, and sit in the front row of class. Then he learns your name, and is slightly more positive towards you. Zucker is like an adorable old man who got the job for that reason. As well as he knows the material, sometimes it's hard for him to properly teach it, and he has this way of doing so by pretending not to know the answer and letting you guess.

GO TO TUTORIAL. It was the only way I really learned anything in this class. The lectures were good for the theory, but when it came to actual homework, it didn't always help. The TAs do their best to explain the material but make sure you copy down what they say. Forgetting to write a sentence can get you 0 on the entire question, so learn the format for what they require.

As helpful as external questions are, learn the ones from the homework and his notes, and possibly the text book, because they will probably pop up on the midterm or final.

This course isn't something you can just wing; you need to know the material, and know it well. You can do really well in this class, and I think some people got 12s, but the average was probably a 7 in the course. A lot of people failed the midterm with the average being 45 % after a 5% bellcurve, but the majority passed the class. He's flexible in how he weighs the different material with marking schemes down below:

Option 1:
10 % Homework
30 % Midterm
60 % Final

Option 2:
15 % Homework
5 % Midterm
80 % Final

Option 3: (If MSAF Midterm)
20 % Homework
80 % Final

TLDR: Go to class and tutorials, and despite the small weightage of the homework, always do them. It can be beneficial