Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Part 2- Scheduled Job

 
Nimit Shah
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As a part of one of the Risk mitigation i am putting scheduled jobs.
Scheduled job is not mentioned in requirements or any usecase. I just put that as risk mitigation.

I have shown scheduled job in component diagram.

Should, it also be shown in class/sequence diagram?
Should it be only using EJB Timer as this is JEE5 solution? If I choose EJB Timer should I include it in class diagram?

 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 35279
384
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, you should put your class in the class diagram.

What is the risk of a scheduled job? This seems like a technology choice and not a risk.
 
Nimit Shah
Ranch Hand
Posts: 55
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Jeanne for your reply.

To answer your question of what is risk?

In my assignment, it involves some activity with external bank. I have identified this as risk. As a mitigation I put that the system should have scheduled jobs to reconcile the system.

So, scheduled jobs are not the part of requirements, it is just a part of risk mitigation strategy.

In this case, because it is JEE system I believe natural choice should be ejb timer. I show these scheduled job in component diagram. I am howeve confused about showing this in class diagram.

If I hv to show this in class diagram then exact ejb and method needs to be shown, while in component diagram it is at high level.
 
Jeanne Boyarsky
author & internet detective
Marshal
Posts: 35279
384
Eclipse IDE Java VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I see. The scheduled jobs are a risk mitigation and not a risk. (That makes sense.) You don't need to include mitigations in your design. You can simply describe them in the mitigation section. It is fine to include mitigations in the actual design of course. But then you should have extra risks since you've already taken care of this one.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic