Decision-Making in Support Systems

The video tutorial explains decision support systems using graphical methods like decision tables and trees. It uses a dinner scenario to illustrate how different conditions lead to various actions. The tutorial covers creating a decision table, analyzing outcomes, and visualizing decisions with a tree. It concludes with key takeaways on decision-making processes.

What is the primary purpose of using graphical methods in decision support systems?

• To confuse the decision-maker

• To visually represent decision-making processes

• To make decisions more complex

• To eliminate the need for decision-making

In the dining out scenario, what are the two conditions considered for decision-making?

• Food price and service quality

• Menu variety and portion size

• Restaurant location and ambiance

• Food promptness and taste

What action might be taken if the food is late and tastes terrible?

• Recommend the restaurant to friends

• Write a positive review

• Do nothing

• Complain and avoid the restaurant

If the food arrives on time but doesn't taste good, what is the likely action?

• Complain to the manager

• Tell friends to avoid the place

• Write a negative review

• Do nothing

What is a decision table used for in decision support systems?

• To eliminate unnecessary decisions

• To graphically represent decision outcomes

• To list all possible decisions

• To organize conditions and corresponding actions

Why might some columns be omitted in a decision table?

• Because they are too complex

• Because they represent actions that are not taken

• Because they are not visually appealing

• Because they are redundant

What is the main advantage of using decision trees over tables?

• They are easier to draw

• They provide a more detailed analysis

• They visually represent the decision-making process

• They require less data

In a decision tree, what do the branches represent?

• Steps in a process

• Different decision-makers

• Unrelated decisions

• Possible outcomes of a decision

What should be done if a decision tree becomes too complex?

• Simplify by combining similar outcomes

• Add more branches

• Ignore the complexity

• Start a new tree

Why is it unnecessary to write 'do nothing' as a separate action in a decision table?

• Because it is implied when no action is taken

• Because it is not a valid action

• Because it complicates the table

• Because it is always the default action