In The unified software development process, page 164 Later, when the user interface designers suggest suitable user-interfaces for the use-case, they may be limited by those decisions. The problem is that the descriptions often contain implicit decisions about user-interfaces. It's not my own statement, but that of Jacobson, Booch and Rumbaugh, the founding fathers of UML: A toolbar is not a goal: it's a user-interface element.įrom the engineering practice perspective, use-case should not be used for user-interface design. It's not part of the solution space, i.e. But this cannot be what you mean: exiting a presentation is at best a sub-part of checking a fileįrom the point of view of the purpose, a use-case should represent a user goal.
I am sorry to disapoint you, but I have to tell you that this practice is just plain wrong:įrom the point of view of the semantics, the use-case specialization means that Open presentation is a special form of Check file, and Save file as well, and that the actor could use them interchangeably and independently.
0 kommentar(er)
