Which diagram should I use?
Which diagram should I use?
(OP)
Hi all,
I'm new to UML and would like your advice please.
My company uses a charts application to display charts about how well the company is doing.
These charts use data collected from our live SQL db.
These are the processes that I'd like to document in an UML diagram.
SQL Scheduler:
Job 1: Data collected from our live SQL db (runs at 6am)
Charts application scheduler:
Job 2: gets the collected data into the off the charts application own db in a new format (runs at 7am)
Job 3: this task makes the charts ready for users (runs at 8am)
These 3 steps are not related at all and if one step fails the rest will still run but the charts will be incorrect.
I thought the best diagram to use is the "sequence diagram" but this requires messages that flow between
activities?
As you can see there's no messages flowing and these jobs run at certain times of the day.
How would you document these steps?
Thanks in advance.
W.
I'm new to UML and would like your advice please.
My company uses a charts application to display charts about how well the company is doing.
These charts use data collected from our live SQL db.
These are the processes that I'd like to document in an UML diagram.
SQL Scheduler:
Job 1: Data collected from our live SQL db (runs at 6am)
Charts application scheduler:
Job 2: gets the collected data into the off the charts application own db in a new format (runs at 7am)
Job 3: this task makes the charts ready for users (runs at 8am)
These 3 steps are not related at all and if one step fails the rest will still run but the charts will be incorrect.
I thought the best diagram to use is the "sequence diagram" but this requires messages that flow between
activities?
As you can see there's no messages flowing and these jobs run at certain times of the day.
How would you document these steps?
Thanks in advance.
W.
RE: Which diagram should I use?
With an activity diagram, you can simply say do job 1, then do job 2, then do job 3. Then you can set up your relationships between them in terms of constraints. I would not say as a constraint that job 1 runs at 6 am, job 2 runs at 7 and so on. What you care about is that job 1 ran successfully before job 2 runs and so on, and you should express your constraints in those terms. That way, you add flexibility to the process design. If, for example, you find down the road that your business demographic changes and you need to accommodate other time zones, you may wish to decide to run the reports at a different time of day. However, what will not change is that the last 2 jobs are dependent on the previous ones running.
An unforeseen consequence of the information revolution has been the exponential propagation of human error.