Most people go astray right from the start with use cases.
Perhaps it is the similarity between use case diagrams and dataflow diagrams which leads people to define use cases that are simply functions or menu items. Whatever the reason may be, it is notably the most prevalent mistake that novices make. In simplest terms, I like to regard a use case as a story about some way of using a system to do something useful . The answer, of course, is no. All of the remaining elements are alternate flows in this one use case.