| Author |
Message |
   
Maxim Rusakov
| | Posted on Friday, April 16, 2010 - 06:12 am: |    |
Functional requirement: 1) Application should make a report (derived data) 2) Application should show it to a user 3) User can edit some numbers in the report 4) User can save the report in database (edited or not). The idea behind such rules that system may have a pieceof information. So, the reports should be corrected by a user before sending them to regulators. Whould you count it as one EP and classify it as EO? Or would you rather think of 2 EP: EO + EI? |
   
Steve Neuendorf
| | Posted on Friday, April 16, 2010 - 11:39 am: |    |
Hello Maxim, Sounds like the reporting system far too many companies are using to interface with the regulators. All of the steps are dependent, so there is one EP, and that is an EO. Looking at the reports, if they are saved such that there remains a dependence on the source data, identify additional RET(s) with the source data. If the user does not consider the dependence (here I would consider time too), then count the saved reports as an ILF and an additional FTR for the initial EO. Hope this helps, Steve |
   
Maxim Rusakov
| | Posted on Monday, April 19, 2010 - 01:43 am: |    |
exhaustive answer thank you, Steve! |
   
N.Venkateswaran
Username: Nvenk
Post Number: 262 Registered: 07-2009
| | Posted on Saturday, April 24, 2010 - 03:00 pm: |    |
Big Boss. Hearty welcome to 1 EP counter's Group. |
|