Skip to main content

Power of Information visualization

Ben Shneiderman is a giant person in information visualization field and he has contributed for many theories in this field. He has coined what he calls information visualization mantra that leads to information seeking behavior:

“Overview first, zoom and filter, then details on demand”

The important point is that a good computer-based visualization is an interface that can support all of these activities. According to this mantra; system should represent the overview of the entire collection, any interested item should be able to zoom, able to filter out uninteresting items, and also able to select an item or group and
get details when needed. Any system which follows this mantra can be representing the high volume of information in an effective manner. Figure 1 shows application (Ex: Spotfire) which built upon using this mantra. In this application entire item collection are displayed and any item can be
Labels:

Comments

Post a Comment

Popular posts from this blog

The transaction is in doubt

Sometimes you may get this error when you use transaction scope . The transaction is in doubt I also got this error recently and able to find the reason for it. That is because of the some of the readers had not properly disposed. Actually in this case you can use Using keyword to overcome this. Exception : System.Transactions.TransactionInDoubtException was unhandled by user code Message="The transaction is in doubt." Solution : using (reader) { }
1 comment
Read more

Dead Code Problem

Problem Actually this problem occurred when i was doing integration two projects. [Phase1 and phase2 of a project] . Phase 2 is developed on top of the phase1. Parallel phase1 had changed lot . Mean time those were working on phase2 has commented existing phase 1 code without comments . Phase 1 and phase 2 merged with some conflicts. So we commented such places with the descriptive comment . After merged the result code base has merged those phase 2 commented parts. Also there was some of already dead code in phase 1. So it is difficult to understand weather this is actual dead code or commented one from phase 2. Mistake Had left dead dead code and missing comments . Lesson learned Normally developers leave dead code in their original code with the mind of future purpose. But this not a good habit to continue.As long as you use source control ,earlier code may exist. Problem will occur if you are not using such version control. In such a situation you can keep dead code with des
2 comments
Read more