project planning - What UML diagram should I use for simple application features..? -


I'm really confused about this, tried to read a lot about the diagram, but I can not understand What is the most suitable for this matter?

I need to show that I have 10 modules, which have 10 features, one of the other modules can call the feature.

Something very easy . It would be better with some kind of constraints [as the features] and how each module block will interact with another block.

The objective is to show that there is no need to open source systems, And what is this system after will modifications. Along with the colors, it is easy to display all the modifications. It is easy to start a project plan and count how much you will need to do.

The reason you are confused is that the creators of UML created a list of their diagrams (a dozen types) and never really Tells one or the other.

If you are talking about features, this means using the case diagram. You can see some examples here: or


Comments