Modelling increments in an incremetal development

[william kane]

I need to model increments in a project with an incremental approach.What is the UML diagram i can use?
Thanks in advance
William

[Stan James]

As far as software modeling I don't know any good tricks here. We have struggled for years over what to do with future requirements, known now but not scheduled for the current release. We don't want them in current working docs but don't want to lose them either. I think modeling software evolution through iterations will have the same problems.

I qualified that as software modeling because you can also use UML to model the processes of your team, and there you might find some of the diagrams useful. But I don't think that's what you were after.

[Ilja Preuss]

Originally posted by william kane:
I need to model increments in a project with an incremental approach.What is the UML diagram i can use?

What kind of information do you want to depict? How will it be used, and by whom?

[Scott Ambler]

As for modeling future requirements, consider Change Cases.

William, it sounds as if you need to read Be Realistic About the UML.

- Scott

[william kane]

Originally posted by Scott Ambler:
As for modeling future requirements, consider Change Cases.

William, it sounds as if you need to read Be Realistic About the UML.

- Scott

Thanks Scott and Ilja,
I get the point that you are driving.What i really wanted to model was the use cases I will design in each iteration throughout my project life cycle.I was looking for a UML diagram that will allow me model this split of use cases and fact that non clear use cases will be revisited in the subsequent iteration.I guess i will use a simple spread sheet to represent this.
Thanks,
William

[Stan James]

Sounds like a project plan! Have you read up on the XP "planning game"? It's a very cool way to schedule features. My team's variation on it is HERE; Google for "planning game" for other points of view.

[Ilja Preuss]

Originally posted by Stan James:
Sounds like a project plan! Have you read up on the XP "planning game"? It's a very cool way to schedule features. My team's variation on it is HERE; Google for "planning game" for other points of view.

I agree with this.

To preserve the grouping of the story cards to iterations/releases, you can simply use rubber bands or lunch boxes.