Extend and include in file system

Question

In our Software we want that the user to open a project file with different number of items (similar as in a Visual Studio Project) and he should be able to extract and insert these items from external sources (from other project, for example). I know the user should open projects, save projects, extract and insert items but, in terms of UML Use Case Diagrams, I don't know how to represent the three last user cases:

• Either as extensions from the first one, that only exist after the first user story occurs.
• Or representing the user case Open Project as an included Use case from the other three.

In the picture I have the two Use Case Diagrams. Are they both good?

Answer 1

I don't think either one of your solutions is correct.

The diagram with the extends indicates that we we might save a project while opening a project, which seems odd to me.

The diagram on the right says the inverse, while saving a project we also open a project. Again that seems wrong to me.

From my viewpoint these use cases all need to be separate use cases without an extend or include relation between them. They all seem to be somewhat on the same level. I can imagine that each of the use cases could be triggered by a single menu option.

Answer 2

Ask yourself: is Open Project a use case? What is the added value? I guess there is none at all. So if there is no added value, it is not a use case. And if it is no use case, you don't need a bubble.