10.1. The Catalog Search Use Case
My phone rang. I picked it up. Sam started talking immediately.
"Hello. I think I'd really like to get the in-store catalog in operation. Some of the customers have been asking for it. The printed listing of what CDDiscs we have in inventory works OK, but they'd like to be able to search for which CDDiscs have a particular song."
"Sounds fine. Let's get together and discuss the details," I suggested.
"I don't have much time, but I don't want to hold you up. I'm heading to the Caribbean in half an hour," Sam said in a hurried tone.
"All right. We need to work on the details," I replied.
"No time for details. I just want it searchable," he said.
"OK, I'll start to work on it. Can I get in contact with you if I have a question?" I asked.
"No. We'll be on a remote island without phones. But I trust you'll do the right thing," he replied.
"I'll tell you what; can I create a simple use case description and have you approve it before you go?" I queried.
"Yeah, go ahead, but make it quick. My taxi leaves in half an hour," he stated.
"Can I go with you?" I asked. "I hate to work on a project without the client available."
"Maybe some other time. I trust you'll make the right decisions," he replied.
I expanded the original Search_catalog use case to multiple use cases. This is an example of a hierarchical set of use cases. Search_catalog is at the top, and the following use cases fall underneath, each providing a detailed manifestation of the original ...