Reputation: 603
I am designing a use case diagram for system and doesn't know how to represent its output.
Here's what system is supposed to do.
(1) Run on different server and will be part of another product maintained by entirely different team in organisation. (2) Gather information and send it to message queue which will be part of my product maintained by my department.
I want to show explicitly in use case that there will be two different systems here and my application will run on client system and send message to message queue in different system. I am confused in how to show message queue is part of another system.
Shall I just have a use case showing only message queue in another system and connect it to user case in client system ?
Thanks
Upvotes: 0
Views: 1168
Reputation: 497
For your need sequence diagram might better emphasise the process part. I'm not sure if I get your systems right, but this simple example may help:
Upvotes: 0
Reputation: 6318
If you interact with external system (e.g. send some messages to its queue), you depict that system as actor involved in Use Case.
You don't show on UC diagram that your system is "spread" on several servers. This is presented on deployment diagram.
Upvotes: 2
Reputation: 36323
Use cases are not about architecture/technical aspects. Use cases are about the added value of the system. Neither of your 2 cases is about the added value but about its architecture (the 2nd could be re-formulated to be a use case Gather information
, but that's a commonplace). Place them in a component diagram to show how its deployed. However, you should start over thinking what the actual added value is for the actors of you system under consideration.
Upvotes: 2