Evaluating process: Difference between revisions
Mr. MacKenty (talk | contribs) No edit summary |
Mr. MacKenty (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
You must evaluate if the sequence of activities (or instructions) will result in the required outcomes. This evaluation can be logical, arithmetic, or both. | You must evaluate if the sequence of activities (or instructions) will result in the required outcomes. This evaluation can be logical, arithmetic, or both. | ||
'''A common scenario is evaluating the order of conditionals. You must become very good at tracing conditional expressions.''' | |||
You should remember your order of operations. | You should remember your order of operations. | ||
Revision as of 15:32, 14 July 2017
Evaluating process[1]
You must evaluate if the sequence of activities (or instructions) will result in the required outcomes. This evaluation can be logical, arithmetic, or both.
A common scenario is evaluating the order of conditionals. You must become very good at tracing conditional expressions.
You should remember your order of operations.
In mathematics and computer programming, the order of operations (or operator precedence) is a collection of rules that reflect conventions about which procedures to perform first in order to evaluate a given mathematical expression.[2]
Do you understand this?[edit]
Standards[edit]
- Evaluate whether the order in which activities are undertaken will result in the required outcome.