Use Case Diagram with Multiple Systems?

Question

I don't know how to make the following use case diagram with multiple systems. What happens if I use for that example:

Another system that is for the developer actor that add the items. This is something what I am searching for:

_{(source: gliffy.com)}

but is it possible to use multiple systems and connect them?

---

I have edited my idea here:

I have to sides, the Client side and server side, where admin can edit data, in administration menu, so it updates the server database and and the database of the client... but i don't now the right notation to use...

Answer 1

Crossing borders with use cases is ok in principle. In your example the Update Database should have an <<extends>> from Edit Data (needs to point from the second to the first!).

Note that you should avoid the use of those extension. If your use case diagrams resemble a spider's web your design is broken. Remember that it's called use case synthesis - not analysis. The first will try to gather things under a hat while the 2nd is used in coding to break down complexity.