Hi All,
I have a similar situation in one of my projects,where in the system that we are developing needs to do some calculations at the end of a particular period(usually at end of a quarter).With the above discussion,I have now concluded that ,in my case a system which monitors time(external system as an actor) invokes the set of calculations in my system.My question is do I capture these calculations in a typical use case format with pre conditions,basic flow,post conditions,business rules in it and all these calculations as business rules? or is there any format where in I can capture these calculations as requirement specifications?All your help/expert opinions will be highly appreciated.Looking forward for your comments/inputs.
Thanks
Viru
Hi Viru,
In the case you have described I'd create a use case and put the calculations as one (or more) of your business rules. This type of use case is generally pretty simple in terms of the interaction between the clock / scheduler and your system. Very important to include it in your list of use cases for your system though.
Kimbo
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: