Discussion:
Design By Use Paper
SirGilligan
2005-09-14 01:29:26 UTC
Permalink
Hello,

I have been working on Design By Use (DBU).
The paper can be found at:
http://home.att.net/~geoffrey.slinker/maverick/DBU.html

Design by Use (DBU) follows the basic steps:
1) Create High Level Design
2) Identify systems and subsystems
3) Identify messages or calls between systems and subsystems
4) Use theses identified messages or calls to specify to each team
what they should code and how the message will be made (the
message/method signature).

DBU is beyond Test Driven Development (TDD) and Design by Contract
(DbC). DBU is concerned with large software systems, multiple teams,
coordination, and integration. TDD is a code design activity. DbC is
a contract driven process based around invariants, pre-conditions,
and post-conditions.


Recently I was explaing DBU to some collegues that work at very large
software development companies.

The said something like, "DBU seems good enough but the problem is
that the teams enter into working on the product at different times
and aren't synched up."

But that is the problem, synching up, that causes such things as long
integration times and "big bang integration".

It seems that I either don't explain DBU well, or it is not
considered any more than TDD and DbC, or I don't know what.

Should I just bag the idea, or keep fighting to get the point across?

Geoff





------------------------ Yahoo! Groups Sponsor --------------------~-->
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/nhFolB/TM
--------------------------------------------------------------------~->
Kent Beck
2005-10-05 21:05:47 UTC
Permalink
Geoff,

It's frustrating when you know you have something important to say and other
people don't get it. When I want to be heard, though, "fighting to get a
point across" is not a metaphor I find contributes to communication.
Sometimes in such situations I give up trying to communicate my whole vision
and pick a little, obvious point with immediate relevance and talk about
that. Making one useful point builds a relationship from which I can hear
other people's concerns and talk about my next bit of idea.

Take care,

Kent Beck
Three Rivers Institute
-----Original Message-----
SirGilligan
Sent: Tuesday, September 13, 2005 6:29 PM
Subject: [xpe2e] Design By Use Paper
Hello,
I have been working on Design By Use (DBU).
http://home.att.net/~geoffrey.slinker/maverick/DBU.html
1) Create High Level Design
2) Identify systems and subsystems
3) Identify messages or calls between systems and subsystems
4) Use theses identified messages or calls to specify to each team
what they should code and how the message will be made (the
message/method signature).
DBU is beyond Test Driven Development (TDD) and Design by Contract
(DbC). DBU is concerned with large software systems, multiple teams,
coordination, and integration. TDD is a code design activity. DbC is
a contract driven process based around invariants, pre-conditions,
and post-conditions.
Recently I was explaing DBU to some collegues that work at very large
software development companies.
The said something like, "DBU seems good enough but the problem is
that the teams enter into working on the product at different times
and aren't synched up."
But that is the problem, synching up, that causes such things as long
integration times and "big bang integration".
It seems that I either don't explain DBU well, or it is not
considered any more than TDD and DbC, or I don't know what.
Should I just bag the idea, or keep fighting to get the point across?
Geoff
------------------------ Yahoo! Groups Sponsor --------------------~-->
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/nhFolB/TM
--------------------------------------------------------------------~->
geoffrey_slinker
2005-10-21 21:48:54 UTC
Permalink
Thanks for the advice. I do get frustrated with my ability to
communicate and I find myself pushing harder.

I know my father has told me a million times (while working on
something on the farm) "If it doesn't move when you push on it
pushing harder isn't going to help."

Now I have been reminded a million and one times. Will I ever get
it? ;-)

Thanks alot, the advice is really appreciated.

Geoff

http://groups.yahoo.com/group/maverick_software_development/
http://home.att.net/~geoffrey.slinker/agile.html
Post by Kent Beck
Geoff,
It's frustrating when you know you have something important to say and other
people don't get it. When I want to be heard, though, "fighting to get a
point across" is not a metaphor I find contributes to communication.
Sometimes in such situations I give up trying to communicate my whole vision
and pick a little, obvious point with immediate relevance and talk about
that. Making one useful point builds a relationship from which I can hear
other people's concerns and talk about my next bit of idea.
Take care,
Kent Beck
Three Rivers Institute
-----Original Message-----
SirGilligan
Sent: Tuesday, September 13, 2005 6:29 PM
Subject: [xpe2e] Design By Use Paper
Hello,
I have been working on Design By Use (DBU).
http://home.att.net/~geoffrey.slinker/maverick/DBU.html
1) Create High Level Design
2) Identify systems and subsystems
3) Identify messages or calls between systems and subsystems
4) Use theses identified messages or calls to specify to each team
what they should code and how the message will be made (the
message/method signature).
DBU is beyond Test Driven Development (TDD) and Design by
Contract
Post by Kent Beck
(DbC). DBU is concerned with large software systems, multiple teams,
coordination, and integration. TDD is a code design activity. DbC is
a contract driven process based around invariants, pre-
conditions,
Post by Kent Beck
and post-conditions.
Recently I was explaing DBU to some collegues that work at very large
software development companies.
The said something like, "DBU seems good enough but the problem is
that the teams enter into working on the product at different times
and aren't synched up."
But that is the problem, synching up, that causes such things as long
integration times and "big bang integration".
It seems that I either don't explain DBU well, or it is not
considered any more than TDD and DbC, or I don't know what.
Should I just bag the idea, or keep fighting to get the point across?
Geoff
------------------------ Yahoo! Groups Sponsor --------------------~-->
Fair play? Video games influencing politics. Click and talk back!
http://us.click.yahoo.com/T8sf5C/tzNLAA/TtwFAA/nhFolB/TM
--------------------------------------------------------------------~->
Continue reading on narkive:
Loading...