[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [epf-dev] BUP Fundamental Conceptsand CollaborativePrinciplesProposal
|
Not that this isn't a reasonable description, but I also have struggled with
using the house-building example for the following reasons:
1. The requirements for a house are very ubiquitous. So much so, that they
are rarely written down (that is, why do you want a house and what is it
going to do for you). People skip the requirements aspect of house-buillding
and often go right to design.
2. As Don mentioned, many people misinterpret this as being a waterfall.
3. As it relates to many software projects, people start off thinking they
want a house, but end up discovering that what they really need is a toaster
or an aircraft carrier. In house-building, there usually is not significant
divergence from the original concept.
4. Houses actually exist in the real world; software is an abstract virtual
thing that does not really exist in the "real" world, or I should say, it
has no physical manifestation.
After a couple more of people putting in their two cents, maybe we'll have a
dollar!
Chris ~:|
-----Original Message-----
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On
Behalf Of Donald Firesmith
Sent: Thursday, March 30, 2006 2:22 PM
To: Eclipse Process Framework Project Developers List
Subject: Re: [epf-dev] BUP Fundamental Conceptsand
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
