Identifying iViews
How Can I Identify Potential iViews? | Which is a Useful iView, Which iView Does not Make Sense?
How Can I Identify Potential iViews?
The best way to identify possible iViews is to watch users at work and to study their behavior. A user's workplace tells a lot about which information and transactions a user needs on a regular basis.
For example, a user may stick Post-Its along his or her monitor with the names of transactions or reports. Or he or she may stick such lists on the wall or put them elsewhere.
In addition, watching the work practice may provide useful hints about which information the users needs in untypical situations in order to overcome errors or problems.
Which is a Useful iView, Which iView Does not Make Sense?
Useful iViews
Any information or transaction that is used on a regular basis or that must be easily accessible in problem situations is a potentially useful iView. In addition, there are many pieces of information that users need every morning when they start work, every evening when they quit work, or in certain recurring situations.
Useless iViews
iViews that provide information or functionality that is only seldomly used do not make sense.
Example: There is no point in creating an MiniApp that is used for customizing a function once, because the user needs such an iView only once and then never again.
topSource: SAP iView Guidelines for Java