0002525 PI redesign

From UG

(Difference between revisions)
Jump to: navigation, search
(RFP)
 
(19 intermediate revisions not shown)
Line 1: Line 1:
-
[[Category:Projects]]
+
[[Category:RFD]]
== Info ==
== Info ==
-
Mantis: 0002525: [PI re-design] ......... <proj>
+
Mantis: '''0002525''': [PI re-design] ......... <proj>
-
Team:
+
This is a [[Project]].
-
* MO: Karen
+
-
* BA: Tracie
+
-
* SA: Alex
+
-
* Developer: Kostya?
+
-
* QA: ?
+
== Business Analysis ==
== Business Analysis ==
-
=== Requirements ===
+
=== Business Needs ===
-
Acc MO/Jaguar CFO requested PI module redesign. It should address 2 unrelated problems:
+
Acc MO/Jaguar CFO requested PI module redesign. It should address 2 unrelated problems: [[#Delay problem]] and [[#Verification problem]]. See below.
==== Delay problem ====
==== Delay problem ====
Line 21: Line 16:
Currently user adding new Invoices through ''Main Menu > Acc > Add New Purchase Invoices'' experiencing long delay. It is inconvenient.  
Currently user adding new Invoices through ''Main Menu > Acc > Add New Purchase Invoices'' experiencing long delay. It is inconvenient.  
-
==== Reminder requirement ====
+
===== Reminder requirement =====
-
We do understand that it happens mainly because currently system runs [[Incomplete PI Report]] every time user wants to see new PI web form. Please note that it was designed in such a way to remind/notify Acc operators that there are X incomplete PIs that require immediate attention. Therefore if step of running report is eliminated then another mechanism must be provided to satisfy this "reminder requirement".
+
We do understand that it happens mainly because currently system runs [[Incomplete PI Report]] every time user wants to see new PI web form. Please note that it was designed in such a way to remind/notify Acc operators that there are some incomplete PIs that require immediate attention. Therefore if step of running report is eliminated then another mechanism must be provided to satisfy this "reminder requirement".
==== Verification problem ====
==== Verification problem ====
-
The process of entering PI an verifying that this PI correctly being associated with required CT is cumbersome. CFO user feels necessary to look at P/L tab of given CT every time she enters PI against this CT. This to make sure that PI/amount is correctly appeared there. This is normally for PI with very large amounts entered against individual CTs.  
+
The process of entering PI and verifying that this PI has been been indeed associated with required CT is cumbersome. CFO feels that it is necessary to look at P/L tab of given CT every time she completes entering PI against this CT. This is to make sure that PI/amount is correctly appeared there. She does this normally only for PIs with very large amounts entered against individual CTs.  
-
So her steps are (example):
+
So her steps are the following (example):
* click ''Main Menu > Acc > Add New Purchase Invoices''
* click ''Main Menu > Acc > Add New Purchase Invoices''
* enter PI#123 (5000 USD against CT#678), submit  
* enter PI#123 (5000 USD against CT#678), submit  
* open CT#678 through Quicklink
* open CT#678 through Quicklink
* goto P/L tab; verify that PI#123 (5000 USD) appears there  
* goto P/L tab; verify that PI#123 (5000 USD) appears there  
 +
* click ''Main Menu > Acc > Add New Purchase Invoices''
 +
* so on ...
-
New process and/or system feature needs to be (re)designed to satisfy requirements above. Current process/system is to slow/cumbersome.
+
Entering PI Business Process and/or system feature needs to be (re)designed to satisfy requirements above. Current process is too slow/cumbersome.
-
=== Possible solutions ===
+
=== RFP ===
 +
No [[Proposal]] is required before coding unless solution suggested is complex and takes a long time to implement.
-
'''Delay problem'''
+
== Systems Analysis ==
 +
 
 +
=== SA for Delay problem and Reminder requirement ===
 +
 
 +
Of course simplest solution (for user and her manager) would be is to optimize report in such a way so that it will appear instantly. I this case no business process re-design (and as a result re-training) is required. But it seems to me that it is unlikely to achieve on the technical level. Also still it would be a "two step process" which was required by previous MO but not current MO.
[[#Delay problem]] could be solved by eliminating the step of executing [[Incomplete PI Report]] every time user clicks ''Main Menu > Acc > Add New Purchase Invoices''.
[[#Delay problem]] could be solved by eliminating the step of executing [[Incomplete PI Report]] every time user clicks ''Main Menu > Acc > Add New Purchase Invoices''.
Line 45: Line 47:
Of course we still need to be able to access this report. So link to this report could be added to ''Acc > Reports''.
Of course we still need to be able to access this report. So link to this report could be added to ''Acc > Reports''.
-
In addition to this some mechanism is required to remind/notify Acc operators that there are X incomplete PIs in the system and require action. We suggest to use [[Dashboard]] approach for this.
+
In addition to this some mechanism is required to remind/notify Acc operators that there are X incomplete PIs in the system and require action. I suggest to use [[Dashboard]] approach for this.
-
'''Verification problem'''
+
=== SA for Verification problem ===
 +
 
 +
MO and BA suggested the following solutions:
'''Solution 1.''' Karen suggested to add additional tab to CT Editor from which PI could be entered.
'''Solution 1.''' Karen suggested to add additional tab to CT Editor from which PI could be entered.
Line 55: Line 59:
'''Solution 2.'''I suggested that two browser windows could be open - one with "Enter PI screen". Another is used to enter CT through Quicklink. User could switch between 2 browser tabs. But it seems that this idea did not become popular. Also it probably still could qualify as "cumbersome".
'''Solution 2.'''I suggested that two browser windows could be open - one with "Enter PI screen". Another is used to enter CT through Quicklink. User could switch between 2 browser tabs. But it seems that this idea did not become popular. Also it probably still could qualify as "cumbersome".
-
=== RFP ===
+
Solution 1 is not a good idea since it will make CT editor even slower. Instead we could provide "Add PI" link to "PI editor" from "P/L tab". This version of editor would have Back button directing back to P/L tab so that user can verify that invoice indeed appeared there.
-
No [[Proposal]] is required before coding unless solution suggested is complex and takes a long time to implement.
+
-
== Systems Analysis ==
+
== Architect Review ==
'''Delay problem''' and '''Reminder requirement'''
'''Delay problem''' and '''Reminder requirement'''
-
Of course simplest solution (for user and her manager) would be is to optimize report in such a way so that it will appear instantly. I this case no business process re-design (and as a result re-training) is required. But it seems to me that it is unlikely to achieve on the technical level. Also still it would be a "two step process" which was required by previous MO but not current MO.
+
Report could be optimized to run 10 times faster. But still it should be eliminated from the Add PI workflow.  
 +
 
 +
I approve Dashboard solution.
 +
 
 +
'''Verification problem'''
 +
 
 +
Yes, adding new tab is a bad idea. I approve solution suggested by SA.
 +
 
 +
== Implementation Summary ==
 +
''Author:TBD(Developer)''
-
I agree with solutions suggested by BA. Use standard [[Dashboard]] design: display only number of incomplete PIs. User can click on this number to see report.
+
== QA Plan ==
 +
''Author:TBD(QA)''
== History ==
== History ==
* removed SA Notes section;
* removed SA Notes section;
-
* re-worked Requirements section
+
* major re-work --[[User:Alex|Alex]] 23:44, 11 December 2010 (EST)
-
--[[User:Alex|Alex]] 17:07, 11 December 2010 (EST)
+

Current revision as of 02:02, 12 January 2011


Contents

[edit] Info

Mantis: 0002525: [PI re-design] ......... <proj>

This is a Project.

[edit] Business Analysis

[edit] Business Needs

Acc MO/Jaguar CFO requested PI module redesign. It should address 2 unrelated problems: #Delay problem and #Verification problem. See below.

[edit] Delay problem

Currently user adding new Invoices through Main Menu > Acc > Add New Purchase Invoices experiencing long delay. It is inconvenient.

[edit] Reminder requirement

We do understand that it happens mainly because currently system runs Incomplete PI Report every time user wants to see new PI web form. Please note that it was designed in such a way to remind/notify Acc operators that there are some incomplete PIs that require immediate attention. Therefore if step of running report is eliminated then another mechanism must be provided to satisfy this "reminder requirement".

[edit] Verification problem

The process of entering PI and verifying that this PI has been been indeed associated with required CT is cumbersome. CFO feels that it is necessary to look at P/L tab of given CT every time she completes entering PI against this CT. This is to make sure that PI/amount is correctly appeared there. She does this normally only for PIs with very large amounts entered against individual CTs.

So her steps are the following (example):

  • click Main Menu > Acc > Add New Purchase Invoices
  • enter PI#123 (5000 USD against CT#678), submit
  • open CT#678 through Quicklink
  • goto P/L tab; verify that PI#123 (5000 USD) appears there
  • click Main Menu > Acc > Add New Purchase Invoices
  • so on ...

Entering PI Business Process and/or system feature needs to be (re)designed to satisfy requirements above. Current process is too slow/cumbersome.

[edit] RFP

No Proposal is required before coding unless solution suggested is complex and takes a long time to implement.

[edit] Systems Analysis

[edit] SA for Delay problem and Reminder requirement

Of course simplest solution (for user and her manager) would be is to optimize report in such a way so that it will appear instantly. I this case no business process re-design (and as a result re-training) is required. But it seems to me that it is unlikely to achieve on the technical level. Also still it would be a "two step process" which was required by previous MO but not current MO.

#Delay problem could be solved by eliminating the step of executing Incomplete PI Report every time user clicks Main Menu > Acc > Add New Purchase Invoices.

Of course we still need to be able to access this report. So link to this report could be added to Acc > Reports.

In addition to this some mechanism is required to remind/notify Acc operators that there are X incomplete PIs in the system and require action. I suggest to use Dashboard approach for this.

[edit] SA for Verification problem

MO and BA suggested the following solutions:

Solution 1. Karen suggested to add additional tab to CT Editor from which PI could be entered.

This is only for PI invoices that are mapped to only one CT. When adding a new PI from the CT record, the CT number should automatically fill in and should not be editable. This will make sure that only PI's belonging to that CT record can be entered there.

Solution 2.I suggested that two browser windows could be open - one with "Enter PI screen". Another is used to enter CT through Quicklink. User could switch between 2 browser tabs. But it seems that this idea did not become popular. Also it probably still could qualify as "cumbersome".

Solution 1 is not a good idea since it will make CT editor even slower. Instead we could provide "Add PI" link to "PI editor" from "P/L tab". This version of editor would have Back button directing back to P/L tab so that user can verify that invoice indeed appeared there.

[edit] Architect Review

Delay problem and Reminder requirement

Report could be optimized to run 10 times faster. But still it should be eliminated from the Add PI workflow.

I approve Dashboard solution.

Verification problem

Yes, adding new tab is a bad idea. I approve solution suggested by SA.

[edit] Implementation Summary

Author:TBD(Developer)

[edit] QA Plan

Author:TBD(QA)

[edit] History

  • removed SA Notes section;
  • major re-work --Alex 23:44, 11 December 2010 (EST)
Personal tools