• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Use case diagram for interfacing external system

 
Edmund Yong
Ranch Hand
Posts: 164
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Let's say that there is a new application to be developed. This application needs to send messages periodically to another system X. System X also needs to periodically send messages to this application. All the sending/receiving of the messages are not triggered by user actions. As the sending of the messages to system X and receiving of messages from system X are considered major functions of the application, there should be a use case diagram. Now how do I draw the user case diagram? Do I show one actor presenting system X, and an arrow pointing from use case "Send messages" to the actor, and another arrow pointing from the actor to the use case "Receive mesages"?
 
Hong Anderson
Ranch Hand
Posts: 1936
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Right, actor can be anything that initiate a use case.

But are you sure that Receive Messages is a use case? Maybe, you mean Process Messages or Save Messages.
 
Edmund Yong
Ranch Hand
Posts: 164
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Kengkaj Sathianpantarit wrote:Right, actor can be anything that initiate a use case.

But are you sure that Receive Messages is a use case? Maybe, you mean Process Messages or Save Messages.


Well, it is a listener thread for receiving messages and updating the record for each message in the database. I just call it "Receive Messages" here for convenient.
 
Hong Anderson
Ranch Hand
Posts: 1936
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Do you mean this thread will check messages periodically?

In that case the use case name should be Check Messages.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic