Structuring UML

[kalas]

Hi all,

I'm a newbie in UML modeling. I already understand the basics of diagrams but I have problems with structuring the project/diagrams into views/packages.

I older EA the new project is structured to
Use Case View, Dynamic View, Logical View, Component View, Deployment View, Custom while in new EA I got
Business Process Model, Requirements Model, Use Case Model, Domain, Component and Deployment M., ...

Let's assume, I want to develop bigger SW that is deployed in 2 systems, has 5 components (SW modules), defined interfaces between them and let's say 2 configuration files. The system should be developed in C++. I also want to describe the system by Use Case Views at high level.

What are yours proposals?

[thomaskilian]

Take only those parts you need. Make them "feel good" for you. Very simple! - too simple?

Try reading this thread

[sargasso]

1. Take 600 cats
2. Herd them

too easy?

1. Push 1kg of mercury up a 45 degree incline using only your nose.

still too easy?

1. Define a single formal structure for a UML repository that suits all real business situations.

[mikewhit]

Ref the cats - you're using the wrong approach. Just pull a (long!) piece of string along the ground and you can lead them where you want.

Now apply that to the single UML structure.

[Actually there are a few alternatives discussed in Realtime UML (Douglass) in one of the earlier chapters]