In broad terms there are three key elements to consider in the development of any new application – or any new product, for that matter. The obvious one, certainly from a software point of view, is the technology to be used – the language, the target platform and operating system, and the rest. But this is largely a set of …
Unfogging the crystall ball
As a Business Analyst the second biggest problem I encounter (after finding someone in the business who even recognises, let alone takes ownership of, the processes they run) is managing their obsession with reports.
Everyone needs reports, that's for sure. But the current model only tells us what has happened after the event (read, 'disaster'). Then they become justification for laying blame at someone else's door.
Having argued for years for a more intelligent approach to predictive reporting, the idea behind ODIS appeals to me. The implementation may be OTT for many SMEs who could make good use of it, but there's something for everyone here.
Example: imagine a new type of bank statement. Instead of just telling you that you are overdrawn, what if the system looked at your historical spending pattern, matched that up to your current balance, and produced an early warning that you >may< go overdrawn before the end of the month? Lots of business strive for exactly this type of predictive reports, but do it manually.
Not rocket science, IBM. But a worthy effort to make lives less stressful. The challenge will be building a user-friendly business rules engine that makes the predictions worth reporting.
- Xmas Round-up Ten top tech toys to interface with a techie’s Christmas stocking
- Google embiggens its fat vid pipe Chromecast with TEN new supported apps
- Microsoft: Don't listen to 4chan ... especially the bit about bricking Xbox Ones
- Shivering boffins nail Earth's coldest spot
- Exploits no more! Firefox 26 blocks all Java plugins by default