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.

I like the last one as it shows the product getting "bigger" and morecomplete through the four phases.

Regarding the lifecycle diagram, attached is a slide that appears in APG'sRUP training that might foot the bill. The things I like about it is itshows "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 andsolution 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 forincorporating 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 goodreason) that it was going to be an extension to OpenUP as a plug in someway(OpenUP/XP?)...

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 thisthread) is the picture above the WBS that is labeled Workflow on theLifecycle page. I think this diverges too much from the focus of "what is
the lifecycle?" and instead covers "what's it all about?" Especially theones without the phases.

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

Did we add Daily Meetings as a definitive, default characteristic ofapplying 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 understoodto 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 (assuggested 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 andDeliverable columns on the Work Product Usage? That sounds like somethingthat could add a little more clarity to the process.

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

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

Ana

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