March 3, 2015 2 Comments
Below is a photo from New Mongolian BBQ, a favorite dinner place for the family. This is a really interesting example of an ambiguous requirement as demonstrated by an ambiguous API. As part of the instructions at the start of the line, a patron is suggested to use two bowls – one for meat, and one for vegetables.
When the patron gets to the end of the line for the their Mongolian to be cooked and they are presented with this spot for two sets of waiting customers. The first question that comes to mind is I have two bowls.
The two immediate options that I see for what this means is
- Customers front and back, bowl 1 and bowl 2.
- Customer 1 and customer 2
Judging from the customers choosing randomly from the two options above. I generally opt for bowl 1/bowl 2 if there aren’t any bowls already up when I arrive.
So how do we take the ambiguous requirement and make it mostly obvious to most patrons? My suggestion would be to place a thick line to separate the two customer spots. This would rely on human nature to want to have their bundled things bundled together. If you look carefully at the picture, this might be the intent since there is already a slightly larger gap between the front and back.
Any other suggestions on how to resolve this ambiguous requirement? Any similar simple but confounding ambiguous requirements issues that you have found? Post a comment below.