I was thinking of the jigsaw pieces as the UML or the preferred programming
language.
I.e. they already exist, what we're trying to do is put them together in
the correct sequence.
Maybe if you consider that our pieces are also mixed in with a load of
pieces from other puzzles which we must eliminate from the puzzle.
Then as was suggested by Frances, maybe Lego is a better analogy, because
in Lego, many pieces are identical.
Whereas in the jigsaw puzzle analogy every piece is unique.
No analogy is perfect, else it wouldn't be an analogy.
Perhaps you'd like to tackle the problem using Lego?
I feel Lego will give more flexibility.
Leslie.
Lars Hauschultz
<[EMAIL PROTECTED]> To: [EMAIL PROTECTED]
Sent by: cc:
owner-rose_forum@ra Subject: RE: (ROSE) Use Cases and
UC Diagram
tional.com
12/04/00 02:34 AM
Please respond to
Lars Hauschultz
Hi Leslie,
the thing I don't like about the jigsaw puzzle analogy as described in your
conversation, is that the pieces seem to be there already, and that one
just
have to assemble them correctly to finish the job. IMO, the analogy would
be
clearer, if the pieces wore to represent classes, and our job was to build
and assemble a set of jigsaw pieces in order to create a complete picture
(for our customer).
The analyst would analyse what the customer wants and make a description of
the picture. She would probably separate the description into descriptions
of chunks (horse, house, tree), their texture and their positions in the
picture.
The designer would define how the jigsaw pieces (the classes) should look
like, how they shall interact, which cardboard material to use and so on.
The coders would cut and paint the pieces.
The compiler would assemble the pieces. (!)
This is not what I wrote the last time, but I am (I hope) getting cleverer
every day. First, I thought of the pieces as being use cases.
Lars.
P.S. Far too few analysts are women too. :-)
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Saturday, 02 December, 2000 4:24
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: (ROSE) Use Cases and UC Diagram
Lars,
We agreed that the analyst is not assembling pieces, but is trying to
define the picture that the pieces will go to make.
The pieces are put together by the developers.
I don't think of the analyst as actually defining pieces, I prefer to think
of the pieces as the building blocks.
The analyst is stating what the pieces will look like when put together.
The designer is stating how to put the pieces together.
Coders put the pieces together.
I like to think that the pieces already exist, just like they do when you
open a jigsaw puzzle box. Nobody on the development team is actually making
them.
Les.
P.S. Some analysts are women too you know. :-)
Lars Hauschultz
<[EMAIL PROTECTED]> To:
[EMAIL PROTECTED]
Sent by: cc:
owner-rose_forum@ra Subject: RE: (ROSE) Use
Cases and UC Diagram
tional.com
12/01/00 04:08 AM
Please respond to
Lars Hauschultz
Hi Puzzlers,
somehow I get the feeling that you are getting it all upside down. The
analyst is not assembling the pieces of the jigsaw puzzle. On the contrary,
he is defining pieces, which will together make a large picture! He must
have some idea of how the picture should look before he can design
meaningful pieces.
;-) Lars.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 30 November, 2000 21:59
To: Butler, Frances H. (FHB)
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: (ROSE) Use Cases and UC Diagram
Frances,
I agree with what you say, 'that you have to understand the finished
picture before you put the pieces together'.
But putting the pieces together I like to consider to be the 'Design'.
Finding out what the picture is, is what I want to call 'Analysis'.
Discovering Use Cases comes before both 'Design' and 'Analysis'. It's a way
of finding out what is in your picture without going into the details.
So in the Use Case/Inception phase I'm trying to discoves what is in the
picture - in the Analysis phase I'm combining the parts I discovered in the
Inception phase and putting the details into the picture - in the design
and implementation phase I'm actually working with the pieces. (I don't
have a jigsaw analogy for the testing phase.)
I don't think this contradicts what I said yesterday. Basically in the use
case phase in order to discover whats in the picture, I'm observing the
pieces to see what they contain.
So I can see there's a horse, a house, sky, trees, etc. Note I haven't put
any pieces together, just grouped them into 'Packages'.
Now in the analysis phase, I'm going to try and put the pictures of the
horse, house, trees together to form an overall pictuse of the puzzle, and
at the same time I'm going to try and fill in the details of the grass,
walls, clouds, etc, until I'm satisfied that I have an accurate enough
picture to work from.
Now I go into my design and implementation phase and actually try to put
the pieces together.
In summary, during the use case phase we don't have a picture, it's the use
cases that help give the picture to us.
I actually have a whole paper on analysis and design which uses jigsaws as
an analogy for developing software. As I said, one phase that doesn't seem
to fit into the analogy is the testing phase. (Any ideas?)
Leslie.
"Butler,
Frances H. To:
"'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
(FHB) " cc:
[EMAIL PROTECTED], [EMAIL PROTECTED]
<[EMAIL PROTECTED] Subject: RE: (ROSE) Use Cases
and UC Diagram
gov>
11/30/00
12:28 PM
Hi Leslie,
I love your analogy, but I don't agree with your conclusion. As a fan of
jigsaw puzzles, I think you have to understand the finished picture before
you can understand how to put the pieces together, especially the
1000-piece
variety. Most systems come under that category. Why work the puzzle if
you
don't know what the finished picture should be? I'm not convinced that the
finished picture is inaccurate.
Jeff was correct, and I'll bet he's a good jigsaw puzzle solver!
:-)
Frances
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| Frances H. Butler
| Computing Specialist
| BWXT Y-12 L.L.C.
| Oak Ridge, TN
| Phone: (865) 574-3694
| Internet: [EMAIL PROTECTED]
|
| Results! Why, man, I have gotten a lot of results.
| I know several thousand things that won't work.
| Thomas Edison
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 29, 2000 10:13 PM
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: RE: (ROSE) Use Cases and UC Diagram
Still sounds like functional decomposition to me also.
As for what's wrong with it?
1) More likely to be misinterpreted as a design for your system,
2) It's a mentality thing - for me I try to forget that such a beast exists
in case it interferes with my OO thought patterns.
3) It is unnecessary.
My take is to discover your use cases and then, once you have enough start
packaging them, which is the reverse of what is being suggested below (find
chunks and break them down).
Let me try an analogy.
We're trying to do a jigsaw puzzle. There are two different processes being
followed in order to complete the picture.
1) The puzzler (for want of a better word) is looking at the pieces and
grouping them into chunks and gradually building these chunks into bigger
chunks until the complete picture is formed.
2) The puzzler is working from the picture of the puzzle, breaking the
picture into manageable chunks and then looking for the pieces that go to
make up those chunks.
Or to summarise, one is working from the BIG picture the other is working
from the pieces.
After reading this, is it obvious that my preference is to work from the
pieces(1)? The reason for this is that the BIG picture is often flawed and
inaccurate. The pieces are not so.
Leslie.
P.S. Having been out of touch with Project Technology for a while, I'd be
interested to know when they added Use Cases to the S/M method.
************************************************************************
* 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
*
*************************************************************************
