[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [epf-dev] Lifecycle diagram revision


I think the first one is a great picture and we should find a place for
it.  On the other hand the "lifecycle diagram" (that started this
thread) is the picture above the WBS that is labeled Workflow on the
Lifecycle page.  I think this diverges too much from the focus of "what
is the lifecycle?" and instead covers "what's it all about?"  Especially
the ones without the phases.

I like the picture though.  A lot.  Perhaps this is a missing graphic at
the top of the Core Principles page.

Did we add Daily Meetings as a definitive, default characteristic of
applying OpenUP/Basic?

Back to the lifecycle diagram, I think it can have iterations added
somehow. Perhaps just in a more aesthetically pleasing version of what
Steve scrawled or perhaps someone has a more innovative representation.

Though the Lifecycle page does not call it out, WBS elements are
understood to have Work Product Usage in addition to the task-centric
perspective.  I'd love for us to get the focus on the ever growing
product in there (as suggested by Scott).  Of course we don't have a
Work Product called Product, just the Build.  Maybe something like Ana's
ever-growing blocks could fit into the Lifecycle Diagram.

BTW, do we need a side discussion on the Entry State and Exit State and
Deliverable columns on the Work Product Usage?  That sounds like
something that could add a little more clarity to the process.

                                       ------- b

-----Original Message-----
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ana Valente Pereira
Sent: Tuesday, January 23, 2007 5:38 AM
To: Steve Adolph
Cc: Eclipse Process Framework Project Developers List
Subject: Re: [epf-dev] Lifecycle diagram revision

just some ideas ... modified from a picture I saw for something else...

.. I tried to show core principles, some practices inside the iteration 
and the phases ... maybe its too much


Ana Valente Pereira wrote:

> it is also to linear and lacks the learning... feedback from one 
> iteration being used to improve the solution (and the process) for the

> next iteration
> ... I can try to make some drawings and sketches to discuss at the 
> next F2F ? ... and then someone would take care of the graphics?
> Ana
> Steve Adolph wrote:
>> Hello Everyone
>> The OpenUP lifecycle diagram bothers me because it does not include 
>> any dramatic visual clue to OpenUP being an iterative process. I've 
>> just sketched a revise diagram and wonder two things:
>> 1) Am I the only one who is concerned the lifecycle diagram does not 
>> dramatically include iterations?
>> 2) Is there someone out there who actually has creative and drawing 
>> talent and is interested in re-drawing this? J
>> Best regards
>> Steve
>> _______________________________________________
>> 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