I am a little concerned with the statements on scenarios stating "How". A
Use Case deals with "What" the system is doing, the scenario describes in
steps of What is happening not "How".
The "How" deals with design, "How are we doing the What".
-----Original Message-----
From: Smoly Walter MET
To: 'Eric D. Tarkington'
Cc: Rose Forum (E-Mail)
Sent: 11/28/00 2:40 AM
Subject: AW: (ROSE) Bar Bet #1
It seems to me, that a third position is reasonable, which may be the
solution of the problem.
Are we talking about
1.) splitting use cases or
2.) splitting scenarios
Regarding 1.) I agree with position A.
Regarding 2.) I agree with position B.
Why ?
I'm used to concern a use-case consisting of two parts:
the specification, which describes the what
What should be done ?
What is the purpose ?
What data is needed as input ?
What is the result ?
and second the flow of events (scenarios), which describes the how
How must it be done, to get the task done ?
How must it be done, to fulfill the purpose ?
So, I think it is reasonable to structure the scenarios by itself
(according to structured programming), whitout making a separate
use-case of each sub-flow (except in case of reuse)
Like structuring the scenarios in vertical manner
main flow,
exceptional flows,
worst case,..
it is helpful to also structure them in horizontal manner (modelling
sub-flows in a separate sequence diagram and indicate them in a
high-level flow of events)
Kind regards
Walter
-----Urspr�ngliche Nachricht-----
Von: Eric D. Tarkington [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 28. November 2000 06:04
An: ROSE_FORUM
Betreff: (ROSE) Bar Bet #1
There is a collegial dispute between some of the instructors here at
Seneca. I won't tell you which side I'm on, but your comments would be
welcome. You can rest assured that I will pass them on -- if they
support me, of course.
Position A: One instructor says that you can't split a use case into
scenarios that cover less than a *complete* path through the FOE. This
agrees with Quatrani (start of chapter 5, VISUAL MODELLING), but may
produce long, awkward scenarios, and long, wide sequence diagrams.
Position B: The other says that's not good software practice, and
scenarios need to capture a small, natural unit of work in the FOE.
This contradicts Quatrani, but produces shorter scenarios with easier
sequence diagrams. One argument against is that the decomposition into
smaller scenarios may be confusing.
So, whadaya say? Do you favor position A or position B? Why?
-Eric
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
************************************************************************
*
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
************************************************************************
*
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
