SirGilligan
2005-09-14 01:29:26 UTC
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
--------------------------------------------------------------------~->
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
--------------------------------------------------------------------~->