I'm a undergraduate, and studying 'Software Design And Analysis' for my current semester.
As part of the course, I was handed over a case study from which I had to make out the visual form of the resulting
Use Case Diagram, with the necessary
Use Cases and `Actors.
The case study is about
Purchasing Flight Ticket System. A part of the case study read as follows,
Consider your neighboring travel agent from whom you can purchase flight tickets. To book a ticket you need to provide details about your journey i.e. on which date and at what time you would like to travel. You also need to provide your address ...
Now, according to what I knew at that time, I was associating Uses Cases with Functional Requirements - the behavioral aspect of the application. So when I read, "on which date and at what time you would like to travel", I was thinking in my head, "as a user, I would like to have the option to specify the date, time, address". When the evaluating and class discussion came to, I was told that when specifying use cases, I do not ever have to specify the needed attributes and such.
I was confused because,
- The user expects the application to behave like this. Wouldn't it be nice to explicitly mention in the Use Case Diagram that this should happen, that is, it should take the date, time, address as input
- I actually made my original assumption by making 'Get Date', 'Get Time', 'Get Address'as Use Cases, and including them in 'Get Details'.
Is this always true? Do we ever need to specify the attributes and such that will be used ( in an abstract or informal way )?
Thanks for your time!
P.S. Not asking for help with homework. The task was ungraded and is about 1-2 weeks old. If this violates the rules, please feel free to remove.