This shall be the last weekly review for this semester since the examinations will only be testing on topics till this week, and some of the modules have already finished the lecture series.
Database --- The last topic of this module is Normalization. The motivation for this is to remove anomalies in the relations by decomposing the table to smaller tables. For this module, we only need to learn 2NF, 3NF, and BCNF.
Relations in BCNF are certainly in 3NF and 2NF as well. Here's the conditions for each of the three cases:
2NF: for functional dependency in the relation like this {A}->{B}
A is not a proper subset of the candidate key or
B is a part of any candidate key
3NF: for functional dependency in the relation like this {A}->{B}
A is a super key or
B is a part of some candidate key
BCNF(Boyce Codd Normal Form): for functional dependency (F.D.) in the relation like this {A}->{B}
A is a super key
Apart from identifying the different normal forms, obviously, u need to know how to decompose the original relations. The first algorithm breaks the relation R, down to BCNF.
First identify the F.D. that violates BCNF, and we calculate the closure for the LHS of this F.D.
{LHS}+ = {some attributes}
Remove the attributes from R to form R1, and another R2 which consists of the remaining attributes in R union with LHS. Then check for both R1 and R2 that F.D.1 and F.D.2 satisfy with BCNF. If any of them does not satisfy, break that relation further until it satisfy.
This algorithm is not dependency preserving.
Another algorithm is to break R into 3NF:
First, you have to calculate the minimal cover for F.D. the method is in Lecture Review 10. Then re-combine the minimal cover having the same LHS to get the extended minimal cover.
With this extended minimal cover, we create R1, R2, ...., with each of the dependencies. Then we check that none of the relations is contained in another relation. Remove the one that is contained. Then check that at least one of the R contains the candidate key, if not, create another relation with only the candidate key.
Artificial Intelligence --- The last topic is machine learning. It's probably one of the easier topic for this module. For this topic, there are a series of test cases. From these cases, we are to construct a decision tree to predict the outcome for other values.
The decision tree is constructed with some form of algorithm calculating the information gain from choosing the different attributes as the root node. However, it seems more intuitive to construct it by observation at times. The chosen attribute should reduce the entropy of the test cases the most.
Software Engineering --- We continued with testing of the software. This week is white box testing. To do this form of testing, we have to consider the internal functioning of the codes. Looking at the codes, we draw the Control Flow Graph (CFG), then use test cases to test each of the possible routes, varying each time by one single path.
Wednesday 9 April 2008
Tuesday 1 April 2008
Lecture Review Week 10
Database --- This week is the last second chapter of the semester. And since I've posted this after the tutorial, it seems that functional dependency ain't that difficult.
Given a relation scheme R, with attributes A, B, C, D, E, and a set of functional dependency F = { {A->B}, {C->D}, {B,D->A}, {D->B,E}}. The key concept here is to be able to find the closure of the different attributes. From there, find the super key, candidate key and the minimal cover for the relation.
{A}+ = {A,B,}
{B}+ = {B}
{C}+ = {C,D,B,E,A}
{D}+ = {D,B,E,A}
{E}+ = {E}
Therefore, the super keys will be {C}, and anything that contains C and {C} is a candidate key.
To find minimal cover,
step 1: Break the RHS in F to get F'.
F' = { {A->B}, {C->D}, {B.D->A}, {D->B}, {D->E} }
step 2: Break the LHS in F' to get F'', refer to the closure for each of the attributes to see which attribute on the LHS should be kept.
F''= { {A->B}, {C->D}, {D->A}, {D->B}, {D->E} }
step 3: Remove redundant implications from F'' to get F'''
F'''= { {A->B}, {C->D}, {D->A}, {D->E} } in here {D->B} is removed because it can be formed by transitivity from { {A->B}, {D->A} }
In care and skill, the director has to exercise what he knows and within their ability for the benefit of the company, then he should be fine. The degree of skill is dependent on the director's qualification.
In statutory duties, it is what is stated by law that the director should do. To list out the duties is gonna take forever..
This focuses on the pronunciation of words must be accurate, the tone of the talk must not be monotonous. Apart from being able to articulate your ideas across the audience, you must be watch out for the postures, hand movements, positioning of yourself when using visual aids and so on. Try to be natural and talk to the audience. Maintaining eye contact for a while instead of looking everywhere in the audience. Quite standard but not easy to do. Practice makes perfect.
The crux of the lecture lies in constructing a Bayesian network. Using the different conditional probability given, we have to determine which variables are dependent to each other and which are independent and which are conditional independent. From this way, we can effectively reduce the space needed to keep the probability of the different variables by breaking them up into different tables and not all store on one table.
The meaning of testing the system is to try to break the system. If we manage to break the system, then we will need to debug and fix this problem. Therefore values that we want to choose are the values at the boundary.
Given a relation scheme R, with attributes A, B, C, D, E, and a set of functional dependency F = { {A->B}, {C->D}, {B,D->A}, {D->B,E}}. The key concept here is to be able to find the closure of the different attributes. From there, find the super key, candidate key and the minimal cover for the relation.
{A}+ = {A,B,}
{B}+ = {B}
{C}+ = {C,D,B,E,A}
{D}+ = {D,B,E,A}
{E}+ = {E}
Therefore, the super keys will be {C}, and anything that contains C and {C} is a candidate key.
To find minimal cover,
step 1: Break the RHS in F to get F'.
F' = { {A->B}, {C->D}, {B.D->A}, {D->B}, {D->E} }
step 2: Break the LHS in F' to get F'', refer to the closure for each of the attributes to see which attribute on the LHS should be kept.
F''= { {A->B}, {C->D}, {D->A}, {D->B}, {D->E} }
step 3: Remove redundant implications from F'' to get F'''
F'''= { {A->B}, {C->D}, {D->A}, {D->E} } in here {D->B} is removed because it can be formed by transitivity from { {A->B}, {D->A} }
In care and skill, the director has to exercise what he knows and within their ability for the benefit of the company, then he should be fine. The degree of skill is dependent on the director's qualification.
In statutory duties, it is what is stated by law that the director should do. To list out the duties is gonna take forever..
Business Correspondence ---
This focuses on the pronunciation of words must be accurate, the tone of the talk must not be monotonous. Apart from being able to articulate your ideas across the audience, you must be watch out for the postures, hand movements, positioning of yourself when using visual aids and so on. Try to be natural and talk to the audience. Maintaining eye contact for a while instead of looking everywhere in the audience. Quite standard but not easy to do. Practice makes perfect.
Artificial Intelligence ---
The crux of the lecture lies in constructing a Bayesian network. Using the different conditional probability given, we have to determine which variables are dependent to each other and which are independent and which are conditional independent. From this way, we can effectively reduce the space needed to keep the probability of the different variables by breaking them up into different tables and not all store on one table.
Software Engineering ---
The meaning of testing the system is to try to break the system. If we manage to break the system, then we will need to debug and fix this problem. Therefore values that we want to choose are the values at the boundary.
Tuesday 25 March 2008
Lecture Review Week 9
Database --- This week's lecture was rather difficult to understand. What in the world is relational algebra.. Weren't algebra supposed to be some letter that represent numbers?
Anyhow, there are eight operations in relational algebra. Selection, projection, union, intersection, difference, cartesian product, natural join and renaming operator.
Projection is equivalent to the selection clause in SQL. As there could be duplicate tuples, the rows with duplicate are removed - Distinct. Projection is represented by PI
Anyhow, there are eight operations in relational algebra. Selection, projection, union, intersection, difference, cartesian product, natural join and renaming operator.
Projection is equivalent to the selection clause in SQL. As there could be duplicate tuples, the rows with duplicate are removed - Distinct. Projection is represented by PI
- (R)
Selection correspond to the Where clause. Since it always selects the whole tuple, all the tuples are distinct, thus there won't be a need for distinct keyword. Selection is represented by SIGMA
Union is the combined of the different relations, removing duplicate tuple. Intersection is the duplicate tuples in the relations being considered. Set difference is the tuples that appear in the first relation but not in the second relation.
Cartesian product gives all the possible combination of the tuples between the first and the second relation. No duplicate is possible. Theta-join does a cartesian product of the two relations on some conditions given.
Natural join joins two relations with relations of the same name and projects only one of the attribute. Renaming allows attributes to be renamed, similar to the keyword -As in SQL.
A company is a legal person but do not have the senses like a natural person. The two primary organs of a company are the board of directors and shareholders. The directors are people who run the company in accordance to the Companies Act. The qualification of a director is just that you have to be above 21 years old and is a natural person.
Business Correspondence ---
Contents must be audience centred, difficult to understand terms and abbreviations must be explained.
Use catchy phrases with memory devices and word painting techniques. Give your points in words that give the same sound - alliteration. Repeats your catchy phrase to make an impression. Make comparison using simile, metaphor. Other techniques include allusion, counterpoint, hypothesis and rhetorical question
Artificial Intelligence --- The lecture continues on Logics. To infer from first order logic, there are three ways, forward chaining, backward chaining, and resolution. Basically, I still don't understand forward and backward chaining. For resolution, it is trying to form a proof by refutation / contradiction. By adding the negation of the statement to be proven to the knowledge base, you try to derive that the statement is unsatisfiable. This will therefore prove that the statement is true.
Software Engineering --- This week's lecture basically converts state diagrams into codes and see what should be done to enforce that the states are not violated. Converting from designs to codes are usually quite intuitive and nothing much can be said about this lecture. Anyway, the test is done after the mid-term test, and I really can't concentrate well thereafter. Just hope the test is not too badly done like the other two modules.
Tuesday 18 March 2008
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.
{
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.
Thursday 6 March 2008
Lecture Review Week 7
Database --- Two tests in 2 hours, it's been fun.
Business Law --- It's a new topic on tort of negligence, and the tutorial question that my group will have to present is on this topic. Don't really understand the lecture much, but after reading up on the topic, this is what I think the topic is about.
To prove that someone was negligent to you, you have to show that the person owes you a duty of care. For example, when you walk on the street, you have to be careful not to walk into them, causing them injuries. While the standard of care may differs in different cases, the reasonable man test still applies for all of them, just that the man will be specialist of that particular profession that is undergoing the trial.
Apart from the duty of care, the negligence must have caused damage to the other party. This cause will also be accessed based on whether the damage is foreseeable and not too remote or far-fetched.
For defenses against negligent, there are two ways mentioned. First is that the injured party had volunteered to the risk or that he had consented the risk he is undertaking. This is a complete defense. Another is that the injured party was partly to blame for his own injury, therefore the injured party can only claimed part of the damages that the defendant is responsible for.
Business Correspondence --- The lecture was quite interesting and is on inter-cultural communication. This lecture wasn't to be tested in the exam but was still good to have.
As the topic has suggested, it's about understanding how the different cultures are like and that things that we do, other cultures will do it differently. When talking to my superior, I'll try to keep eye contact but some other culture may not as this is a sign of respect. There are just too many examples, so I shan't go into details.
Artificial Intelligence --- This lecture is on first-order logic, and it was mostly covered before in previous semesters. The AND, OR, NOT, =>, <=> and so on. But there's one part that I don't really understand is the sign '|=' which represents entail. When it's said that a knowledge base entails a statement says P i.e.
K.B. |= P,
it means that the K.B. is actually a subset of the statement P. At first, I thought that it was the other way round, but now, i think it does makes sense. The entails is saying that the statement P is implied from the knowledge base through some logics, so it's quite intuitive that P should be a bigger set or the set K.B.
Software Engineering --- This lecture is the last lecture by the first lecturer, and it concludes the design part of the module. How do we draw a state-chart? Actually, you just have to imagine in your mind how the software will work, and what the different states will be will automatically come to you. Then from this states, you go through the different ways that the state may change and draw the arrow out. Then there you have it, the state-chart.
Business Law --- It's a new topic on tort of negligence, and the tutorial question that my group will have to present is on this topic. Don't really understand the lecture much, but after reading up on the topic, this is what I think the topic is about.
To prove that someone was negligent to you, you have to show that the person owes you a duty of care. For example, when you walk on the street, you have to be careful not to walk into them, causing them injuries. While the standard of care may differs in different cases, the reasonable man test still applies for all of them, just that the man will be specialist of that particular profession that is undergoing the trial.
Apart from the duty of care, the negligence must have caused damage to the other party. This cause will also be accessed based on whether the damage is foreseeable and not too remote or far-fetched.
For defenses against negligent, there are two ways mentioned. First is that the injured party had volunteered to the risk or that he had consented the risk he is undertaking. This is a complete defense. Another is that the injured party was partly to blame for his own injury, therefore the injured party can only claimed part of the damages that the defendant is responsible for.
Business Correspondence --- The lecture was quite interesting and is on inter-cultural communication. This lecture wasn't to be tested in the exam but was still good to have.
As the topic has suggested, it's about understanding how the different cultures are like and that things that we do, other cultures will do it differently. When talking to my superior, I'll try to keep eye contact but some other culture may not as this is a sign of respect. There are just too many examples, so I shan't go into details.
Artificial Intelligence --- This lecture is on first-order logic, and it was mostly covered before in previous semesters. The AND, OR, NOT, =>, <=> and so on. But there's one part that I don't really understand is the sign '|=' which represents entail. When it's said that a knowledge base entails a statement says P i.e.
K.B. |= P,
it means that the K.B. is actually a subset of the statement P. At first, I thought that it was the other way round, but now, i think it does makes sense. The entails is saying that the statement P is implied from the knowledge base through some logics, so it's quite intuitive that P should be a bigger set or the set K.B.
Software Engineering --- This lecture is the last lecture by the first lecturer, and it concludes the design part of the module. How do we draw a state-chart? Actually, you just have to imagine in your mind how the software will work, and what the different states will be will automatically come to you. Then from this states, you go through the different ways that the state may change and draw the arrow out. Then there you have it, the state-chart.
Monday 25 February 2008
Lecture Review Week 6
Database --- This lecture is like a revision from the pre-requisite module. The truth is what you see inside the database, and not what is true in the real world. Things that don't make sense may be true, so don't use your knowledge to determine whether a statement is true.
Business Law --- This is on the sale of goods act. It's a contract to shift ownership of personal belongings from seller to buyer after the buyer paid money to the seller. Goods can be classified into three types - Specific goods where the very goods to be sold is confirmed at time when the contract is made. Unascertained goods where the goods to be sold is out of a bulk amount and not yet confirmed exactly which item in the bulk is to be sold. Future goods are goods that are not yet available at time when contract is made.
The ownership passes with the intention of the two parties in specific goods and for unascertained goods when they are ascertained. Once ownership is passed, the risk is also passed at the same time, meaning whatever that happens to the goods thereafter will be borne by the buyer. If the intent was not shown when the contract is made, the ownership passing will depends on the five rules listed in s18.
Business Communication --- Step 5 - step 8 of proposal writing is the actual part of writing the proposal. Step 5 is to organise the information you wish to present in a systematic way. Step 6 is to write your first draft, Step 7 to KISS (keep it short & simple) the reader and step 8 is to create visual impact to attract the reader's attention. This can be done by using a good font and formating of the document.
Artificial Intelligence --- To continue with more searching, this lecture goes on to constraint satisfaction problem. The most common question for this type of problem is the map colouring, which asks what is the least number of colours that you need to use to colour the whole map, and no two neighbouring states can have the same colour. This question can be easily represented in the form of a constraint graph.
Of course, when you choose which state to start colouring from, you will have to check for the state with the most constraints, in the graph representation will be the node with the highest degree.
You can also use other method like forward checking to check in advance the consequence of colouring the state. This is done by keeping track of the remaining legal value of unassigned nodes, if there is a state that will have no legal value, then it would signify a bad move.
Arc consistency is the chain reaction from making an assignment. When you remove a value from a state because the value is impossible, then it could cause other states to have other removal of their possible values.
Software Engineering --- Continuing into the design for the software, more notations are added to the domain modeling and use-case. Then there's something called the interaction diagram, which shows how the user will interact with the software. Sort of resembles a time-line, showing the different activities that take place when the user use the software.
Business Law --- This is on the sale of goods act. It's a contract to shift ownership of personal belongings from seller to buyer after the buyer paid money to the seller. Goods can be classified into three types - Specific goods where the very goods to be sold is confirmed at time when the contract is made. Unascertained goods where the goods to be sold is out of a bulk amount and not yet confirmed exactly which item in the bulk is to be sold. Future goods are goods that are not yet available at time when contract is made.
The ownership passes with the intention of the two parties in specific goods and for unascertained goods when they are ascertained. Once ownership is passed, the risk is also passed at the same time, meaning whatever that happens to the goods thereafter will be borne by the buyer. If the intent was not shown when the contract is made, the ownership passing will depends on the five rules listed in s18.
Business Communication --- Step 5 - step 8 of proposal writing is the actual part of writing the proposal. Step 5 is to organise the information you wish to present in a systematic way. Step 6 is to write your first draft, Step 7 to KISS (keep it short & simple) the reader and step 8 is to create visual impact to attract the reader's attention. This can be done by using a good font and formating of the document.
Artificial Intelligence --- To continue with more searching, this lecture goes on to constraint satisfaction problem. The most common question for this type of problem is the map colouring, which asks what is the least number of colours that you need to use to colour the whole map, and no two neighbouring states can have the same colour. This question can be easily represented in the form of a constraint graph.
Of course, when you choose which state to start colouring from, you will have to check for the state with the most constraints, in the graph representation will be the node with the highest degree.
You can also use other method like forward checking to check in advance the consequence of colouring the state. This is done by keeping track of the remaining legal value of unassigned nodes, if there is a state that will have no legal value, then it would signify a bad move.
Arc consistency is the chain reaction from making an assignment. When you remove a value from a state because the value is impossible, then it could cause other states to have other removal of their possible values.
Software Engineering --- Continuing into the design for the software, more notations are added to the domain modeling and use-case. Then there's something called the interaction diagram, which shows how the user will interact with the software. Sort of resembles a time-line, showing the different activities that take place when the user use the software.
Friday 15 February 2008
Lecture Review Week 5
Database --- This lecture covers conceptual modeling. It's more diagrams than words showing relationships between entities
Business Law --- The conclusion of contract laws this week covers the discharge from contracts. This is done in 4 ways. Firstly, when the contract is completed exactly and precisely, you are automatically discharged from the contract. It's 'ALL OR NOTHING', unless it's a divisible contract that states when you completed the contract to certain extent, you get paid partially.
Second way is ending the contract by agreement. Third way is by frustration, where neither party is at fault that the contract cannot be completed. In this case, the deposit must be refunded, no more outstanding sum of money will be payable but you can be paid for the expanses made so far till the point when there is a frustration.
The fourth way is by breaching the contract. Of course, this means there's a case. You can be sued for damages for breaching, but the amount of damages must be kept as low as possible for the wrong-doer. Damages is not profit, but a form of compensation. If damages is not enough, then Specific Performance may be used to make up for the inadequency.
Business Communication --- Proposal is an offer to furnish goods and services, research a subject, or to provide a solution to a problem. They can be divided into four types, solicited internal, usually requested by your boss to provide a solution to a problem, unsolicited internal, which you initiate to offer a solution to your boss (bootlicking?!), solicited external and unsolicited external.
Proposal writing can be divided into eight steps.
Step 1) Analyze RFP, Request for Proposal. Content requirement that gives technical function requirement, legal requirement which states terms and conditions, ownership of work, administration information which gives point of contacts, due date and how many copies of the proposal required, format guideline which states the language, font, page layout for the proposal.
Step2) Do research, understand the problem and needs of the public through market research. Do product research by coming out with viable solutions to the problem. Client research writing a targetted proposal.
Step3) Design a prototype,
Step4) Focus the proposal, arouse the interest of the reader
Artificial Intelligence --- One more searching technique introduced. This will be used in the the first project for the module. I wonder why people already finished this project even before this lecture.. Alpha-Beta pruning is a technique that that searches for a highest 'Minimax' value from the different states possible. The idea here is to assume the opponent is optimal, thus you can omit some paths which you know will lead to a worse state. However, if the opponent is noob, and will not choose his optimal path, then this technique may not be optimal.
This pruning depends alot on the order of expansion of nodes, sometimes, there may not be pruning at all.
Software Engineering --- Wow, this lecture basically just expand the Use-case Diagram and Domain Model to contain more detail planning. This will be the design for the software that you are going to build.
Business Law --- The conclusion of contract laws this week covers the discharge from contracts. This is done in 4 ways. Firstly, when the contract is completed exactly and precisely, you are automatically discharged from the contract. It's 'ALL OR NOTHING', unless it's a divisible contract that states when you completed the contract to certain extent, you get paid partially.
Second way is ending the contract by agreement. Third way is by frustration, where neither party is at fault that the contract cannot be completed. In this case, the deposit must be refunded, no more outstanding sum of money will be payable but you can be paid for the expanses made so far till the point when there is a frustration.
The fourth way is by breaching the contract. Of course, this means there's a case. You can be sued for damages for breaching, but the amount of damages must be kept as low as possible for the wrong-doer. Damages is not profit, but a form of compensation. If damages is not enough, then Specific Performance may be used to make up for the inadequency.
Business Communication --- Proposal is an offer to furnish goods and services, research a subject, or to provide a solution to a problem. They can be divided into four types, solicited internal, usually requested by your boss to provide a solution to a problem, unsolicited internal, which you initiate to offer a solution to your boss (bootlicking?!), solicited external and unsolicited external.
Proposal writing can be divided into eight steps.
Step 1) Analyze RFP, Request for Proposal. Content requirement that gives technical function requirement, legal requirement which states terms and conditions, ownership of work, administration information which gives point of contacts, due date and how many copies of the proposal required, format guideline which states the language, font, page layout for the proposal.
Step2) Do research, understand the problem and needs of the public through market research. Do product research by coming out with viable solutions to the problem. Client research writing a targetted proposal.
Step3) Design a prototype,
Step4) Focus the proposal, arouse the interest of the reader
Artificial Intelligence --- One more searching technique introduced. This will be used in the the first project for the module. I wonder why people already finished this project even before this lecture.. Alpha-Beta pruning is a technique that that searches for a highest 'Minimax' value from the different states possible. The idea here is to assume the opponent is optimal, thus you can omit some paths which you know will lead to a worse state. However, if the opponent is noob, and will not choose his optimal path, then this technique may not be optimal.
This pruning depends alot on the order of expansion of nodes, sometimes, there may not be pruning at all.
Software Engineering --- Wow, this lecture basically just expand the Use-case Diagram and Domain Model to contain more detail planning. This will be the design for the software that you are going to build.
Tuesday 5 February 2008
Lecture Review Week 4
Week 4 of lectures has concluded early today.
Database --- Going into more advanced SQL,, there is the Group By att1, att2, though it there must be no ambiguity between the names of the attributes. The Having keyword is used for aggregate functions.
Nested queries are not recommended, and should be avoided as far as possible as nested queries might be quite misleading. In evaluating nested queries, you think of it as evaluating it in a nested for loop. Nesting are done in the Where line, as Where is the condition for the outer query. Results of inner query is not allowed to be brought out to the outer query.
View is a query with a name, after making the view, the view will be like another table and you can query the view as you would to any table. View is always up to date, any change in the original table will be reflected in the view.
Business Law --- Misrepresentation is a false statement and is of material fact that is made by one part to another, and induces this other part to enter into a contract. To show that it is a misrepresentation, all these four ingredients must be present.
Silence does not amount to misrepresentation, meaning that if the salesperson heard you saying to yourself about something wrong, and did not correct you, it won't be counted as a misrepresentation.
You are not induced into the contract if you had relied on your own judgement or individual investigation, knew of the false statement, or never knew of its existance.
There are three types of misrepresentation, fraudulent, negligent, wholly innocent. It is fraudulent when you know that the statement is false, without belief in its truth, or recklessly not caring whether it's true or not. It is negligent if the false statement is made without reasonable ground, and wholly innocent if it is made with reasonable grounds but the statement still turn out to be false.
Remedies to first two types are damages and/or recission, while for innocent misrepresentation is only recission. Recission is giving back and taking back.
Silence does not amount to misrepresentation unless there is a change in circumstances, or you told the truth but not the whole truth.
Next part was on illegal contracts, either illegal by statute or by common law. Illegal contracts are void contracts. Therefore it does not exist. To claim damages for this type of contract, you have to establish the case without relying on the illegal contract, or the parties are not equally at fault, or the plaintiff repents before the contract is substantially performed.
Contract in Restraint of Trade are prima facie void unless it can be proven that it protects properties of the person who enforced the restraint. For restraints in business, the length of restraints must be reasonable, and must not be contrary to public interest.
Business Communication --- In the continuation of User-Manual Writing, we discussed the six guidelines for task writing. 1) Task names should be action oriented, by using strong verbs and go direct to the point. 2) Organise the tasks logically, you won't want to read a manual which teaches you how to uninstall before installing do you? 3) Determine the elements for each task, 4) Write steps as actions, 5) Group steps under sub-task heading, this will make the manual more readable as related tasks are grouped into one. 6) Be consistent with options, notes and tips.
Tasks can be ordered in two ways, functional and sequential. Functional ordering is more used for reference as it focus on what the software can do. Sequential is more useful in teaching novice user as it focus on what the user wants to do with the program.
Here's the eleven task elements: Task name, user, explanation of task, start state, goal state, steps, results, screens, options, notes, tips. The essential elements are task names, explanation, steps, results, screens and notes.
Database --- Going into more advanced SQL,, there is the Group By att1, att2, though it there must be no ambiguity between the names of the attributes. The Having keyword is used for aggregate functions.
Nested queries are not recommended, and should be avoided as far as possible as nested queries might be quite misleading. In evaluating nested queries, you think of it as evaluating it in a nested for loop. Nesting are done in the Where line, as Where is the condition for the outer query. Results of inner query is not allowed to be brought out to the outer query.
View is a query with a name, after making the view, the view will be like another table and you can query the view as you would to any table. View is always up to date, any change in the original table will be reflected in the view.
Business Law --- Misrepresentation is a false statement and is of material fact that is made by one part to another, and induces this other part to enter into a contract. To show that it is a misrepresentation, all these four ingredients must be present.
Silence does not amount to misrepresentation, meaning that if the salesperson heard you saying to yourself about something wrong, and did not correct you, it won't be counted as a misrepresentation.
You are not induced into the contract if you had relied on your own judgement or individual investigation, knew of the false statement, or never knew of its existance.
There are three types of misrepresentation, fraudulent, negligent, wholly innocent. It is fraudulent when you know that the statement is false, without belief in its truth, or recklessly not caring whether it's true or not. It is negligent if the false statement is made without reasonable ground, and wholly innocent if it is made with reasonable grounds but the statement still turn out to be false.
Remedies to first two types are damages and/or recission, while for innocent misrepresentation is only recission. Recission is giving back and taking back.
Silence does not amount to misrepresentation unless there is a change in circumstances, or you told the truth but not the whole truth.
Next part was on illegal contracts, either illegal by statute or by common law. Illegal contracts are void contracts. Therefore it does not exist. To claim damages for this type of contract, you have to establish the case without relying on the illegal contract, or the parties are not equally at fault, or the plaintiff repents before the contract is substantially performed.
Contract in Restraint of Trade are prima facie void unless it can be proven that it protects properties of the person who enforced the restraint. For restraints in business, the length of restraints must be reasonable, and must not be contrary to public interest.
Business Communication --- In the continuation of User-Manual Writing, we discussed the six guidelines for task writing. 1) Task names should be action oriented, by using strong verbs and go direct to the point. 2) Organise the tasks logically, you won't want to read a manual which teaches you how to uninstall before installing do you? 3) Determine the elements for each task, 4) Write steps as actions, 5) Group steps under sub-task heading, this will make the manual more readable as related tasks are grouped into one. 6) Be consistent with options, notes and tips.
Tasks can be ordered in two ways, functional and sequential. Functional ordering is more used for reference as it focus on what the software can do. Sequential is more useful in teaching novice user as it focus on what the user wants to do with the program.
Here's the eleven task elements: Task name, user, explanation of task, start state, goal state, steps, results, screens, options, notes, tips. The essential elements are task names, explanation, steps, results, screens and notes.
Wednesday 30 January 2008
Lecture Review Week 3
Database --- This week started with the integrity constraints of the tables. Integrity constraints are rules for which to keep the data. Every table will require a Primary Key to ensure that the specified attribute(s) is always different. The attribute can be set to Not Null, so that no entry can be added if that attribute is empty. It can also be set to Unique, to ensure that the specific attribute does not repeats. Primary Key is essentially Unique and Not Null. The next constraints is Foreign Key, this allows the attribute to reference to other tables, and acts like pointers. The keywords to allows changes to be made in the table being referenced and then changing automatically in the referencing table are "On Delete/Update Cascade/No Action/Set Default/Set Null". The last is Check, which checks that the attribute will satisfy the given conditions as stated in the check statement.
Second half of the lesson focus on simple SQL statements. Create Table t1, creates a table, then within the parenteses put the required field of attributes for the table, with its domains and integrity constraints. Drop Table t1 deletes the table t1 created earlier. Alter Table t1 Add attribute domain will expand the table by another column. Insert Into relation_name(att, att) Values () using single quotes for the values. The att, att represents the order you want to add, can be omitted and the default order will be used. To view the whole table use select * from t1. To delete entries, use Delete From t1 where 'conditions'.
Business Law --- In the continuation of contract law lecture, there was discussion on contracts with minors - people under the age of 21, with mentally disordered and drunkards, and with companies. For minors, there could be three types of contract, first is a valid contract, which is beneficial to the minor or is necessity to the minor. Second type is voidable contract, which includes leases and partnership. Third type is void contract, which means the contract never existed in the first place. This includes money lent to minor and goods which are not a necessity to minors. For the contracts with mentally disordered and drunkards, there can only be voidable contracts.
The next part includes the terms of contracts. Conditions are the important terms in a contract, warranties are the minor term of the contract, innominate terms are the terms that you have to wait and see to see whether the breach was a breach of conditions or warranties. Exemption clauses can be included in contracts to exclude the liability of one of the party. Exemption clauses must be in contractual document and not in a mere receipt. If a person signs a contractual document, he is bound by its term even if he does not read (ignorant is not bliss). If a person is induced to sign by misrepresentation, then he won't be bound by the exemption clause. An ambiguous clause is invalid. Exemption clause made after the contract is sign is invalid, however, if there are past dealings and the person is aware that such a clause exists, then he will be bounded by it. Exemption clause does not discharge you from responsibility from death or injury. It can only exempts you from other losses.
Business Communication --- The first lecture on User Manual. It's quite instinctive to perform most of the steps. First, Analyze the users, what are the needs, who will use the software. Second, Design a task list, write out all the tasks that can be done using the softwares. Third, Develop a draft. Fourth, Review and Test the draft, and last Finalize the manual.
When writing the manual, treat the reader as an idiot of the software. Therefore when you write the step by step instructions, they must really lead to the desired outcome. Screenshots are added to aid user identify start state and end state.
The layout of the user manual should also be attractive. This are influenced by 4 factors - Alignment, Contrast, Proximity, and Repetition. Alignment makes the manual neater. Contrast between size of words shows different level of importance, different colours can be used to show that the words are related. Putting things of the same nature together makes it easier for reader to see that they are related, this is proximity, and reusing the same template for over and over again is repetition.
Artificial Intelligence --- This lecture was on more searching techniques. Choosing a search strategy depends on the problem. With more number of goals states, the problem is easier to solve. Other factors are distribution of goal states, the type of search tree (finite or infinite), repeated states, and the need for optimality.
The best first search uses an evaluation function f(n) to estimate the desirability. then order the nodes in fringe in decreasing order of desirability. Greedy Best First Search is a special case which uses a heuristic function h(n) which is an estimate of the cost from n to the goal. This search is Not Complete, Time of O(bm), Space of O(bm), and is not optimal since it doesn't explore for other possible cheaper route.
Another special case is the A* Search. The evaluation function f(n) = g(n) + h(n) where g(n) is the cost so far and h(n) is the estimated cost of n to goal. The h(n) here is an admissible heuristic function which means that the estimation is always lower than the actual cost. Therefore A* is optimal. The time is exponential and space is keeping all nodes in memory.
A recursive best first search keeps the 2nd best f-value seen so far, and backtracks when children reaches a value that exceeds the f-value. My guess for RBFS is it is complete, and not optimal
Software Engineering --- How do you draw a Use Case Diagram? First draw a stick figure of a person, and this is the actor. Then you give him a roll of what he does. A straight line represents association of actor with use case. Dashed arrow with the keyword '<>' specifies the behaviour defined for the base use case. A triangle arrow is a taxonomic relationship between a more general use case and a specific use case. Dashed arrow with '<>' gives a relationship shared between two base use cases.
Second half of the lesson focus on simple SQL statements. Create Table t1, creates a table, then within the parenteses put the required field of attributes for the table, with its domains and integrity constraints. Drop Table t1 deletes the table t1 created earlier. Alter Table t1 Add attribute domain will expand the table by another column. Insert Into relation_name(att, att) Values () using single quotes for the values. The att, att represents the order you want to add, can be omitted and the default order will be used. To view the whole table use select * from t1. To delete entries, use Delete From t1 where 'conditions'.
Business Law --- In the continuation of contract law lecture, there was discussion on contracts with minors - people under the age of 21, with mentally disordered and drunkards, and with companies. For minors, there could be three types of contract, first is a valid contract, which is beneficial to the minor or is necessity to the minor. Second type is voidable contract, which includes leases and partnership. Third type is void contract, which means the contract never existed in the first place. This includes money lent to minor and goods which are not a necessity to minors. For the contracts with mentally disordered and drunkards, there can only be voidable contracts.
The next part includes the terms of contracts. Conditions are the important terms in a contract, warranties are the minor term of the contract, innominate terms are the terms that you have to wait and see to see whether the breach was a breach of conditions or warranties. Exemption clauses can be included in contracts to exclude the liability of one of the party. Exemption clauses must be in contractual document and not in a mere receipt. If a person signs a contractual document, he is bound by its term even if he does not read (ignorant is not bliss). If a person is induced to sign by misrepresentation, then he won't be bound by the exemption clause. An ambiguous clause is invalid. Exemption clause made after the contract is sign is invalid, however, if there are past dealings and the person is aware that such a clause exists, then he will be bounded by it. Exemption clause does not discharge you from responsibility from death or injury. It can only exempts you from other losses.
Business Communication --- The first lecture on User Manual. It's quite instinctive to perform most of the steps. First, Analyze the users, what are the needs, who will use the software. Second, Design a task list, write out all the tasks that can be done using the softwares. Third, Develop a draft. Fourth, Review and Test the draft, and last Finalize the manual.
When writing the manual, treat the reader as an idiot of the software. Therefore when you write the step by step instructions, they must really lead to the desired outcome. Screenshots are added to aid user identify start state and end state.
The layout of the user manual should also be attractive. This are influenced by 4 factors - Alignment, Contrast, Proximity, and Repetition. Alignment makes the manual neater. Contrast between size of words shows different level of importance, different colours can be used to show that the words are related. Putting things of the same nature together makes it easier for reader to see that they are related, this is proximity, and reusing the same template for over and over again is repetition.
Artificial Intelligence --- This lecture was on more searching techniques. Choosing a search strategy depends on the problem. With more number of goals states, the problem is easier to solve. Other factors are distribution of goal states, the type of search tree (finite or infinite), repeated states, and the need for optimality.
The best first search uses an evaluation function f(n) to estimate the desirability. then order the nodes in fringe in decreasing order of desirability. Greedy Best First Search is a special case which uses a heuristic function h(n) which is an estimate of the cost from n to the goal. This search is Not Complete, Time of O(bm), Space of O(bm), and is not optimal since it doesn't explore for other possible cheaper route.
Another special case is the A* Search. The evaluation function f(n) = g(n) + h(n) where g(n) is the cost so far and h(n) is the estimated cost of n to goal. The h(n) here is an admissible heuristic function which means that the estimation is always lower than the actual cost. Therefore A* is optimal. The time is exponential and space is keeping all nodes in memory.
A recursive best first search keeps the 2nd best f-value seen so far, and backtracks when children reaches a value that exceeds the f-value. My guess for RBFS is it is complete, and not optimal
Software Engineering --- How do you draw a Use Case Diagram? First draw a stick figure of a person, and this is the actor. Then you give him a roll of what he does. A straight line represents association of actor with use case. Dashed arrow with the keyword '<
Wednesday 23 January 2008
Lecture Review - Week 2
Database --- Half the lecture was spent on unfinished part of the introduction, the other half is on tables (the one that stores data). Seems like nothing much has been taught.. Headache for my project.
Business Law --- This lecture's on contract law. The two types of contract are verbal and written contract. All contracts are agreements but not all agreements are contracts. Contracts consist of three elements -
1. Offer and Acceptance,
2. Intention to create legal relations,
3. Considerations.
On point 1 -
Offer + Acceptance = Contract made
Invitation to Treat -> Offer + Acceptance = Contract made
Invitation to Treat is asking someone to make an offer to do something, examples include Goods on display for sale. When you shops, you are offering to buy the item at the stated price, and the cashier can accept or refuse to sell you, not the other way round. All news paper advertisements are also Invitation to Treat.
You have to revoke your offer before the other party accepts, no revoking after that. When there is a counter-offer to the original offer, the orignal offer is forgotten. In instantaneous contract, contract is only made when the offeror has received the acceptance while in contracts by post, contract is made when the offeree has posted the acceptance.
On point 2 -
You have intention to sue the other party in case of breach of contract. Domestic and social agreements are presume to have no intention as the agreement is based on mutual trust. After separation of husband and wife, there are intentions to sue. In commercial agreements, there are intention to make a legally enforceable contract.
On point 3 -
Consideration is some benefit accruing to one party or some detriment suffered by the other. Suffering must be after the contract is made, anything before is not counted. Consideration must be real and recognised by law (e.g. money), but need not be what the market value is. Consideration must not be for something within your own duty.
Payment of smaller sum will not discharge you from a larger debt, unless it is agreed by the creditor and consideration is made. Valid consideration is payment before due day by creditor's request, payment at different place at creditor's request, and payment with a delivery of a chattel (a movable article of personal property).
Business Communication --- Second lecture on Business Correspondence, introducing another acronym STARS standing for Specific, Thoughtful, Affirmative, Respectful, Simple.
In writing letter, you have to be thoughtful for the reader. Prevent using negative words, basically you should not put on an air when you write and while doing that, make the reader as happy as you can, and when the reader is happy, any request made will be accepted.
Artificial Intelligence --- I was so lazy to attend the lecture, so I had the webcast lecture instead. Kinda not able to concentrate well on webcast due to the many distractions at home, but lucky this lecture was on searching algorithms on trees which was taught a year ago.
The bad thing about this module is I have no idea how to do tutorial 1 which commences this week, how would I find the answer? Maybe from AIMA, the name of the recommended textbook.
Software Engineering --- Don't really understand the lecture, nonetheless I'll still try to write something about it.
It seems to me that the lecture is trying to give us an overview of what we'll be handing in for the project submission 1, and 2. Starting from the requirement, we then analyse the requirement before coming out with the design.
Requirements are what the system should be able to do. There are functional requirements which describe system services or functions, and non-functional requirements, which identify quality attributes and different constraints.
By prioritising requirements, we can separate them into 3 levels, from those that are absolutely needed, to highly desirable which means should be met, to the lowest level which could be implemented but not necessary.
The next part was on use case diagram, which comprises of all the possible interactions the user can have when performing the task.
Business Law --- This lecture's on contract law. The two types of contract are verbal and written contract. All contracts are agreements but not all agreements are contracts. Contracts consist of three elements -
1. Offer and Acceptance,
2. Intention to create legal relations,
3. Considerations.
On point 1 -
Offer + Acceptance = Contract made
Invitation to Treat -> Offer + Acceptance = Contract made
Invitation to Treat is asking someone to make an offer to do something, examples include Goods on display for sale. When you shops, you are offering to buy the item at the stated price, and the cashier can accept or refuse to sell you, not the other way round. All news paper advertisements are also Invitation to Treat.
You have to revoke your offer before the other party accepts, no revoking after that. When there is a counter-offer to the original offer, the orignal offer is forgotten. In instantaneous contract, contract is only made when the offeror has received the acceptance while in contracts by post, contract is made when the offeree has posted the acceptance.
On point 2 -
You have intention to sue the other party in case of breach of contract. Domestic and social agreements are presume to have no intention as the agreement is based on mutual trust. After separation of husband and wife, there are intentions to sue. In commercial agreements, there are intention to make a legally enforceable contract.
On point 3 -
Consideration is some benefit accruing to one party or some detriment suffered by the other. Suffering must be after the contract is made, anything before is not counted. Consideration must be real and recognised by law (e.g. money), but need not be what the market value is. Consideration must not be for something within your own duty.
Payment of smaller sum will not discharge you from a larger debt, unless it is agreed by the creditor and consideration is made. Valid consideration is payment before due day by creditor's request, payment at different place at creditor's request, and payment with a delivery of a chattel (a movable article of personal property).
Business Communication --- Second lecture on Business Correspondence, introducing another acronym STARS standing for Specific, Thoughtful, Affirmative, Respectful, Simple.
In writing letter, you have to be thoughtful for the reader. Prevent using negative words, basically you should not put on an air when you write and while doing that, make the reader as happy as you can, and when the reader is happy, any request made will be accepted.
Artificial Intelligence --- I was so lazy to attend the lecture, so I had the webcast lecture instead. Kinda not able to concentrate well on webcast due to the many distractions at home, but lucky this lecture was on searching algorithms on trees which was taught a year ago.
The bad thing about this module is I have no idea how to do tutorial 1 which commences this week, how would I find the answer? Maybe from AIMA, the name of the recommended textbook.
Software Engineering --- Don't really understand the lecture, nonetheless I'll still try to write something about it.
It seems to me that the lecture is trying to give us an overview of what we'll be handing in for the project submission 1, and 2. Starting from the requirement, we then analyse the requirement before coming out with the design.
Requirements are what the system should be able to do. There are functional requirements which describe system services or functions, and non-functional requirements, which identify quality attributes and different constraints.
By prioritising requirements, we can separate them into 3 levels, from those that are absolutely needed, to highly desirable which means should be met, to the lowest level which could be implemented but not necessary.
The next part was on use case diagram, which comprises of all the possible interactions the user can have when performing the task.
Monday 21 January 2008
Lecture Review - Week 1
Introductory Lectures
Database --- This lecture has nothing much this week, spent more than half the time telling us what to expect. Gonna have a project in group of 5, and because I took the S-paper version of the module, we'll be preparing to give some presentations during class. The remaining time was spent on lecture 1, which unfortunately I have already watched the breeze lecture which was much more interesting and faster than the lecturer. Maybe the next lecture will be better cause I'll attend the lecture with no preparations.
Business Law --- It's a fun lecture. Interesting lecture made possible by a veteran lecturer who taught the module for 28 years... Apart from the materials in the lecture notes, learning which court you have to go to for the different amt of compensation you are demanding, she included many personal stories to share with us.
Business Communication --- This is basically just like the english lessons I used to have during secondary schools. This first lesson was about business correspondence. When you write a letter that includes good news, you jump straight to the point and breaking the good news to the intended reader. This is called the direct approach. When the letter is about bad news, you use the packaging approach, giving the bad news as little emphasise as possible. The last approach taught was the indirect approach. It's one where you used when the content is of little / no interest to the reader, and you have to try to get the reader to be interested. So you have to use the GIRO method standing for Gaining Attention, Increasing desire, Reducing resistance, Orchestrating action. Quite funny how people keep coming up with this type of acronym to help easy remembering, but which will cause lots of confusion at the same time.
Artificial Intelligence --- It seems to be another interesting module. The lecturer claimed that he is not an A.I. expert, so we can probably expect an easier paper from him. We'll be having 2 projects for this module. First is a mini-project to write an Intelligent Agent to play some chess game, on a 6 by 6 chess board. Can be done alone or in pair, so if I feel like I can do it, I'll probably be doing it alone. The final agent will be used to play against other agents done by other people, and if you win, you will score higher for that project. The final project details won't be out till later this week. Can't quite recall what was taught in the lecture, but the tutorial will be starting this week for this module, now I'll need to do some self-study again.
Software Engineering --- This is a CS module, targeting Computer Science students like myself, but this sem, there are more Computer Engineers from FoE, so the lecturer decided that the project can be done in C++ too, instead of only JAVA. Group of four, but I haven't decided who to work with. Most likely gonna be joining force with my primary school friend, Billy, once again after the project which we did in primary school some twelve years ago. The first lecture taught the different stages of software engineering.
Database --- This lecture has nothing much this week, spent more than half the time telling us what to expect. Gonna have a project in group of 5, and because I took the S-paper version of the module, we'll be preparing to give some presentations during class. The remaining time was spent on lecture 1, which unfortunately I have already watched the breeze lecture which was much more interesting and faster than the lecturer. Maybe the next lecture will be better cause I'll attend the lecture with no preparations.
Business Law --- It's a fun lecture. Interesting lecture made possible by a veteran lecturer who taught the module for 28 years... Apart from the materials in the lecture notes, learning which court you have to go to for the different amt of compensation you are demanding, she included many personal stories to share with us.
Business Communication --- This is basically just like the english lessons I used to have during secondary schools. This first lesson was about business correspondence. When you write a letter that includes good news, you jump straight to the point and breaking the good news to the intended reader. This is called the direct approach. When the letter is about bad news, you use the packaging approach, giving the bad news as little emphasise as possible. The last approach taught was the indirect approach. It's one where you used when the content is of little / no interest to the reader, and you have to try to get the reader to be interested. So you have to use the GIRO method standing for Gaining Attention, Increasing desire, Reducing resistance, Orchestrating action. Quite funny how people keep coming up with this type of acronym to help easy remembering, but which will cause lots of confusion at the same time.
Artificial Intelligence --- It seems to be another interesting module. The lecturer claimed that he is not an A.I. expert, so we can probably expect an easier paper from him. We'll be having 2 projects for this module. First is a mini-project to write an Intelligent Agent to play some chess game, on a 6 by 6 chess board. Can be done alone or in pair, so if I feel like I can do it, I'll probably be doing it alone. The final agent will be used to play against other agents done by other people, and if you win, you will score higher for that project. The final project details won't be out till later this week. Can't quite recall what was taught in the lecture, but the tutorial will be starting this week for this module, now I'll need to do some self-study again.
Software Engineering --- This is a CS module, targeting Computer Science students like myself, but this sem, there are more Computer Engineers from FoE, so the lecturer decided that the project can be done in C++ too, instead of only JAVA. Group of four, but I haven't decided who to work with. Most likely gonna be joining force with my primary school friend, Billy, once again after the project which we did in primary school some twelve years ago. The first lecture taught the different stages of software engineering.
Subscribe to:
Posts (Atom)
