I need to choose most intuitive, generic and neutral terms, so I am wondering if "case" and "choice" are best ones?
By "case" I mean something (good or bad) what may happen and user can't directly control it. E.g. transport delay, customer decision to buy.
"choice" is something which will happen only if user decides to go this way. E.g. pay for some service or not, go to bus station or call for taxi. (But if bus or taxi will come or not - it's case already, not choice, because user has no control here)
Context - generic planning application, so there are two categories of items listed in the plan.
P.S. I'll try to give more context how this terms are going to be used.
Imagine roadmap diagram with step by step plan of some project. This diagram is build of blocks, like
start -->
[choice] take a loan -->
[case] bank gives a loan -->
[choice] buy 100x teddy bears -->
[case] nothing sold --> [choice] start bankrupting
-or-
[case] 50 sold --> [choice] make discounts
-or-
[case] 100 sold --> [choice] repeat
So these terms are not used as part of sentence. It's just categories of diagram items not really related to the exact content of each item.
I've chosen "case" because in progamming it's common to have multiple conditions block which looks like:
switch valueToTest {
case 'A' -> do smth
case 'B'-> do smth else
}
So in my case I have smth similar - item which describes one of possibilities. But I need it to be understandable for non-programmers also.
P.P.S Ima now thinking also about "occurrence", "occasion" and maybe "instance" as a candidates to replace "case", but not sure if it will be better.
And as "choice" alternative I can think about "option".
For choice user can ask him self "to be or not to be" And for case he will be wondering if it will happen or not.