Henry Petroski has made the convincing case
that all things we make evolve over time. Something is built, it’s used,
it works as well as it does but it also fails in some way, and then the thing
is modified to address the failure. In other words, “Form follows
failure.” For me, BUP is a way to formalize and accelerate that process.
Iterative development is a way to get feedback on the “failure”
before spending time and money on finishing something that won’t meet
user’s needs.
I think the evolution metaphor is
powerful. The product adapts as the needs – the environment – are revealed
or change around the product. We evolve software as much as we build it.
- Jim
____________________
Jim Ruehlin, IBM Rational
RUP Content Developer
Eclipse Process Framework (EPF) Committer
email: jruehlin@xxxxxxxxxx
phone: 760.505.3232
fax:
949.369.0720
From:
epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of Peter
Haumer/Cupertino/IBM
Sent: Thursday, March 30, 2006
12:43 PM
To: Eclipse Process Framework
Project Developers List <epf-dev@xxxxxxxxxxx>
Cc: Eclipse Process Framework
Project Developers List <epf-dev@xxxxxxxxxxx>;
epf-dev-bounces@xxxxxxxxxxx
Subject: Re: [epf-dev] BUP
Fundamental Concepts and CollaborativePrinciplesProposal
I agree. Developing software is not like building a
house or a bridge. These comparisons have been trashed many times in
literature. Software development a la UP is a creative process in which
the results are constantly tested, reviewed, and refactored. You cannot
test how you use the kitchen and dinning room area with the house in the
elaboration picture. Same with growing a fetus. There no way of
elaborating a growing child unless you could read and fully interpret its DNA,
run tests of its future behavior, and continuously rewrite its DNA until you
get the kid that fits your "stakeholder's" needs (what a lovely
thought :-).
Thanks and best regards,
Peter Haumer.
______________________________________________________________
Rational Software | IBM Software Group
PETER HAUMER, Dr. rer. nat.
RUP Development, Cupertino,
CA
Tel/Fax: +1 408 863-8716
______________________________________________________________
Donald Firesmith
<dgf@xxxxxxxxxxx>
Sent
by: epf-dev-bounces@xxxxxxxxxxx
03/30/2006 12:22
Please
respond to
Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>
|
|
To
|
Eclipse Process Framework Project Developers
List <epf-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
Re: [epf-dev] BUP Fundamental Concepts
and CollaborativePrinciplesProposal
|
|
Navvena,
At one level, I like your pictures and their
clarity. However, they do
tend to imply a largely waterfall development with
first requirements,
then architecture, then
design/code/integrate/test, then deliver.
Don Firesmith
Naveena Bereny wrote:
>
> I agree that graphics are required, because a
picture speaks a
> thousand words.
>
> But what we really need are 2 sets of
graphics:-
>
> * An 'at a glance view' of the
various phases/iterations and how
> the disciplines play
along those phases.
>
> I haven't seen a better chart for this than
the RUP hump chart. I do
> see testing humps in the elaboration phase.
> However the chart needs to be modified to
take into account other
> aspects such as collaboration.
> I'd like to see a consistent hump across all
the phases to indicate
> that collaboration is a key to a succesful
project.
>
> * The second set of graphics or
supporting graphics are there for
> further clarity as we
delve into the phase descriptions.
>
> And to use a more universal metaphor, I would
suggest the building
> metaphor as I've indicated below.
>
> 1. Stage 1: It is important to
have the blueprint drawn at the end
> of inception - so you
have the basic requirements, how many
>
> bedrooms/baths
you need.
> 2. Stage 2: In the next stage of
'elaboration', you lay the
> foundation and the frame so that the house
has a solid architecture
> and support.
> Usually needs
inspections (testing) during this phase because
> if things are not up to code you have to
repeat (iterative).
> 3. Stage 3: is where the real
construction takes place - drywall,
> the insulation, doors, windows, cabinets,
painting all need to be put
> into place.
> It is important
to stress that a lot of interaction will take
> place between the stakeholders( home owners)
to figure out what
> colors, what kind
> of cabinets,
doors windows they want. People tend to change
> their minds during this phase even if they
agreed to something different
> earlier.
Communication/Collaboration is key.
> 4. Stage 10: Final inspections are done
to ensure house is to code
> etc. The stakeholder needs to sign off on it
as being ready to use..
>
>
>
> -
>
> *Inception/BluePrint*
*Elaboration/Stabilizing*
> Construction/*Building*
*Transition/Ready to move in*
> (requirements
* the architecture
the
> house
*(in production and for use)
> know what you want)
(foundation
> (drywall, doors, windows)
>
and the frame )
>
>
>
> My 0.02 cents
> Naveena
>
>------------------------------------------------------------------------
>
>_______________________________________________
>epf-dev mailing list
>epf-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/epf-dev
>
>
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev