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.

No comments: