ZFGC
General => Boards => Archive => Other Discussion => Topic started by: MG-Zero on November 09, 2008, 07:30:28 pm
-
Does anyone know the difference between a detail use case and an overview use case? Can't find an answer on google anywhere...
-
In which context?
-
Use cases as in this stuff:
(http://www.agilemodeling.com/images/models/useCaseDiagram.jpg)
-
Those are not necessarily use cases...well okay fine, they probably are, but they seem more like...okay hold on...
I'm not sure what the difference is because I'm far too lazy to look at my notes (yes, I cover use cases in my current class). However, I do know that the UML diagram you have above is not necessarily a formal definition of a use case.
A proper definition of a use case would be something like this:
4. Register
4.1 Actors:
· Unregistered User
· Login Database
· User Info Database
4.2 Goal: Successfully register into [Project Title]'s Network
4.3 Pre-Conditions:
· Unregistered user clicked on “Register†link
4.4 Description:
· [Project Title] displays empty registration form
· Required fields are differentiated by a special symbol
· Unregistered User fills in a minimum of the required fields
· Unregistered User clicks on “Submit†button
· [Project Title] validates submitted form and saves data to Login Database and User Info Database
· [Project Title] indicates registration was successful
4.5 Post-Condition:
· Newly registered user brought to their own profile page
4.6 Variations:
· Newly registered user may optionally fill out the Compatibility Survey immediately
4.7 Exceptions:
· Invalid/missing registration fields
I put it in quotes. Okay, so this is a pretty detailed use case, no? So my theory is that an overview use case is something like what you have in that UML diagram, where it simply lists a bunch of cases, while a detailed use case lists actors, the goal, pre-conditions, description, post-conditions, variations, and exceptions.
BTW if you want to know where that stuff came from, it's from a group project my team and I are working on. I hope it helps.
-
Ehh..a little late now, but thanks anyway >_>
What I posted was a use case diagram btw, different from a use case. But it probably wasnt asking for a diagram anyway so blah xD
-
Ehh..a little late now, but thanks anyway >_>
What I posted was a use case diagram btw, different from a use case. But it probably wasnt asking for a diagram anyway so blah xD
Yeah...it was probably looking for something like the use case I posted. Diagrams don't supply as much information as the detailed use cases. Sorry if I was a bit late.