julianmclean
Joined: Mar 11, 2003
Posts: 118
PM |
I promised I would give regular updates on this, and it's been a while so here goes...
Things are coming together slowly, I've mainly been working on the synchronisation process (mapping calls/sms to the correct allowance or usage type in tariff), made a few changes to the objects to cope with some suggestions made on this board, making the screens look a bit prettier, and built in the call simulator (to "pretend" to make calls/sms until I can build the extract process). Below is a quick summary of progress in each area:
-----Synchronisation-----
The process works as follows:
- Extract new usages from the phone records (not implemented yet, instead use simulator to add new usages)
- Split usages into monthly periods based on the user contract
- For each period, map the usages against the selected tariff and update the relevant monthly state object.
- The state object and tariff is then used to display the remaining allowance and other usages to the user.
Good news:
- The process works and the usages are correctly mapped based on the tariff configuration
- After simulating a call, and re-synchronising, the main view is updated to reduce the available allowance, or add on to the usage total
Bad news:
- the process is currently very slow and needs a lot of optimisation. The more complex the tariff, the longer it takes to map a usage as it needs to check each type until it finds one that matches.
- Need to implement incremental syncronisation so that only new usages are considered to speed it up. Full sync will still be required in certain situations
-----Objects-----
Tariff updates:
- Each usage can now have multiple masks so for example, all calls to 01*, 02*, 03* can be collected into one usage type. (This will hopefully speed up the mapping too). Limited to have each of the masks with the same length so not allowed 01*, 0243*, 03567*, but this will hopefully not present too great a problem.
- Monthly line rental cost of tariff added, which may allow for a total monthly bill generation in the future.
Usage Type updates:
A usage type can be defined as incoming, outgoing or both. Someone commented that in USA, incoming calls are deducted from your minutes. This should allow tariffs to be designed that deal with this situation.
-----Screens-----
Most of the screens are built and work, but they are not very pretty, so I'm going through making them look nicer and more user friendly. Also need to add field validation to prevent tariff files becoming corrupt.
-----Simulator-----
- A one-screen interface allowing the user to "pretend" to generate a usage (call, sms, etc) at a certain date/time, to/from a certain destination, for a certain duration. This is added to the usage log and is therefore included in syncronisations.
- I've also knocked up an excel spreadsheet to generate the usage file for V&P tests, and it might also be possible for testers to load their usage in from an online bill to test the accuracy until teh extract process can be built. |
Posted: 2003-08-06 13:52
