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

Hi All,

  I am a Ph.D student at Portland State University.  I have been monitoring EPF project for a while.  I am actually not a committer but I am studying the developer material at this moment.  My research area is Software Process and Metrics. I have read a lot about RUP and Agile methodology.  Attached are some ideas that I have regarding the life cycle model.  I borrow the idea from the RUP iterative diagram.  I think it helped me when I present to other students. 

  The OpenUP1 is a bit cleaner.  It has inner circle as iterative diagram and the outer circle as the OpenUP Phases.  The size of each phase are different.  I try to convey the growth of work products.

  The OpenUP2 provide the view of work product growth.  I like Ana's idea about that.  However, people could interpret the larger of boxes as effort or duration for each phase, which is not quite correct.  That's why I have arrow called "Work Product".

   The diagrams and color are not set in stone.  I just like to convey my idea.  I hope that the digrams are not too far off from what you have in mind.

  There is an interesting analogy that I had when I think about the OpenUP2.  We can view the iteration circle as a wheel that tries to climb the slope to the finish line.  For each phase, we could put the milestones that need to be accomplished.

Best Regards,

On 1/23/07, Chris Armstrong <chris.armstrong@xxxxxxxxxxxxxxxxx> wrote:
I like the last one as it shows the product getting "bigger" and more
complete through the four phases.

Regarding the lifecycle diagram, attached is a slide that appears in APG's
RUP training that might foot the bill. The things I like about it is it
shows "loopy" iterations occuring continually throughout the phases, makes
some distinction between the end of a phase and the end of a "normal"
iteration, and provides descriptive labels related to the problem and
solution for each phase.

Regarding the presumed inclusion of Daily Meetings (which certainly isn't a
bad idea), I'm sure everyone noticed the numerous Bugzilla entries for
incorporating XP content. I was wondering (like Brian and perhaps others),
if we had made a decision to include the XP content into the "core"
OpenUP/Basic 1.0 content. I guess I thought (perhaps naively, for no good
reason) that it was going to be an extension to OpenUP as a plug in someway

I think discussing the entry/exit state thing would be pertinent...

Chris ~:|

-----Original Message-----
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx ] On
Behalf Of Brian Lyons
Sent: Tuesday, January 23, 2007 6:25 AM
To: Eclipse Process Framework Project Developers List
Subject: 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

epf-dev mailing list

epf-dev mailing list

Attachment: OpenUP1.PNG
Description: PNG image

Attachment: OpenUP2.PNG
Description: PNG image