1

I am trying to create design document for a project which has all background processes in it. The sequence of background processes are as follows:

Process P1->

  • Get all records(thousands) from database.
  • Analyze validity of records.
  • Send valid records to process P2.

Process P2 ->

  • Get valid records one by one.
  • Do first level processing of data.
  • Send this to process P3.

Process P3 ->

  • Get records one by one from process P2.
  • Based on processing results, update records in database.

I am trying to decide which diagrams to create in this case. Particularly, I am confused about Use Case Diagram. What will be the actor here? Is UseCase diagram even applicable in case of such background processes.

apollosoftware.org
  • 12,161
  • 4
  • 48
  • 69
Learn More
  • 1,535
  • 4
  • 29
  • 51
  • for a background process a use case isn't applicable I thought? User has no direct interaction with the process, unless you have it interfacing with some trigger that the end user controls. Activity, Sequence Diagrams and Class Diagrams should be sufficient for your needs. – apollosoftware.org Aug 30 '13 at 18:24

2 Answers2

2

Describing a process is usually done with an activity diagram. If you want to describe a particular execution you should use a sequence diagram.

Alex
  • 71
  • 3
  • AFAIK, To describe a Usecase we can either use Activity diag and/or a Sequence diag. or both. I am confused because I am not sure how I can identify an actor for a background process. – Learn More Sep 02 '13 at 11:21
0

For a background process a use case isn't applicable I thought? User has no direct interaction with the process, unless you have it interfacing with some trigger that the end user controls.

Activity, Sequence Diagrams and Class Diagrams should be sufficient for your needs.

apollosoftware.org
  • 12,161
  • 4
  • 48
  • 69
  • The definition of "User" may also include any external system that your code is communicating with. In other words, "user" does not have to be human. But for this case you're basically right, because everything (assumedly including the DB) remains within the system boundary, so there are no external systems either. – observer Sep 15 '13 at 18:42