A system designer may use IVAS during requirement analysis to analyse different symptoms of the current VA workflow, cogitate likely causes, deliberate possible remedies, and anticipate potential side-effects. A UX analyst may use IVAS to conduct initial assessment of a VA system , identify potentially critical issues for to be evaluated in detail using empirical methods, such as observational studies and small group discussions. A senior manager or a project reviewer may use IVAS to aid the reading and appraising of a report about a VA system.

IVAS, especially its lists of concrete entities, is an ongoing development, and can benefit tremendously from your contributions in terms of time and knowledge. If you have noticed any missing records of certain symptoms, causes, and remedies in improving VA systems, any missing causal relationships between symptoms and causes, between causes and remedies, and between remedies and side-effects, please to click the Contribute text here or press the Contribute button on the top of this page.  We will acknowledge your contribution by listing you a contributor.