Originally Posted by usertech
It seems that 'The David' and his followers think that either the phone calls can be made in any order (so pick the top one if you like) or if they can't that its easy to think about which one should be made first by just looking at the items. I don't think that it always turns out that way. Read on.
Choosing which phone call to make first can be a very complex decision. Having made that complex decision the decision would in my opinion be better stored because the reasoning which led to the decision may not be able to be recalled in detail.
To give you a feeling, let's imagine a set of 4 phone calls:
1. You want to ask Bob to a party but you don't want to ask him unless you know that Jill is coming because Bob doesn't get on with your grandmother (more on her in a sec) and will need to have Jill to talk to. So you delay the call until Jill has replied.
2. You need to call up a caterer to ask for food and the amount of food you order depends on whether both Bob and Jill are coming.
3. You need to call your wife to tell her the final arrangements, including who is coming and how they (including the grandmother) are going to be getting to you.
4. You need to call up a taxi for your grandmother but she will only need one if Bob is not coming because if Bob is coming you won't need to call the taxi.
Project: Plan Party, type=sequential.
- Get attendance response from Jill.
- Invite Bob depending on Jill's response.
- Get attendance response from Bob.
- Finalize arrangments (action group, type=parallel)
-- Order food with caterer
-- Transportation (action group, type=sequential)
--- Call taxi for grandmother if necessary
--- Call wife to report party details
Limit context view to available actions.