Lecture Review Week 8

Database --- This week's lecture continued from the lecture in week 6 - domain calculus. It's quite like tuple calculus, but this deals with the columns. It takes the form of

{ <> | 3y relation(x,y)}

All variables in <> are free variables. All others are not, and they need to be quantified by an existential or universal quantifier.


Business Law --- This week is on Product Liability. It's sort of an extension of tort of negligence and and sales of goods. You will have to proof the 4 essences of negligence. There are two ways for the remedies for this. First is under negligence, the second is under a breach of contract.


Business Correspondence --- This was a fun lecture, the first for oral presentation. There are five steps in the oral presentation process. This lecture concentrated on the first three.

First, is to analyze the audience and prepare the presentation in accordance to the audience you have. Try to give the presentation in a way that will benefit the audience and things that they will be interested in. The venue and time of the presentation is also important to take into account.

Second, apply ABC. Analyze the topic, Brainstorm content ideas, Choose your information. While brainstorming, don't judge the ideas that come up, jot everything down.

Third, draft your speech. The introduction must be captivating and motivating. Get the audience attention right from the start. Use transitional phrases to order the points, have mini-summaries to stress the main points, and double mini-summaries to do transitions between speakers. Conclusion is to summarize the whole presentation. Use the same phrasing as it was used in the blueprint during introduction. Any pamphlet you wish to hand out should be done at the end of the conclusion so as not to distract the audience by letting them read the pamphlet during your presentation.


Artificial Intelligence --- One hour test which I mostly couldn't do, just as I expected. After which a short lecture to wrap up first-order logics.


Software Engineering --- It's the first lecture by the second lecturer. This week focus was on defensive programming, which simply means maintaining the constraints that you have set up during the design phase. Things like 1-1, 1-*, 0..1-*, should be enforced during the coding. It's quite intuitive to know which part of the program to start working from.