INP 402 Exam | Questions with 100% Correct
Answers | Verified | Latest Update 2026/2027
Save
Terms in this set (289)
which flowsheet template setting b. start removed
allows a builder to hide a flowsheet
group until the end user adds it?
a. topic
b. start removed
c. restrict rows
true or false: flowsheet rows, groups, false
and templates are stored in the same
master file
each flowsheet template is a record FLT
in what master file?
Groups and rows are records in what FLO
master file?
aims to create meaning behind tasks user experience
in the system by focusing on the
capabilities of users, how those users
feel, and the emotional connection
users have with the system.
,is a part of the overall user usability
experience and focuses on
understanding what users do, making
those tasks easy to accomplish, and
removing roadblocks to task
completion.
simple rules that you can use to heuristics
approximate a larger probable truth
from smaller truths that are easier to
observe. general rules of thumb that
can be used to help make decisions
heuristic where system should speak system matches real world
the users' language with words,
phrases, and concepts familiar to the
user. follow real-world conventions,
making information appear in a
natural and logical order.
examples are: print groups and
reports with intuitive names;
navigators, activities, and toolbars in
right order
heuristic where users should not Consistency and Standards
have to wonder whether different
words, situations, or actions mean
the same thing. Follow platform
conventions. examples are: words
like similar tools and uses org's
terminology and naming conventions
, heuristic where minimize user's recognition, not recall
memory load by making objects,
actions, and options visible. the user
should not have to remember
information from one part of the
dialogue to another. instructions for
use of the build should be visible or
easily retrievable. examples are:
toolbars and startup activities
provide shortcuts
heuristic where accelerators - Flexibility and Efficiency
unseen by the novice user - may
often speed up the interaction for
the expert user such that the system
can cater to both inexperienced and
experienced users. Allow users to
tailor frequent actions. examples are:
providing tools for workflows, but
not creating clutter and users ability
to re-arrange screen elements
(menus) to suit their needs.
dialogues should not contain simplicity and minimalist design
information that is irrelevant or rarely
needed. every extra unit of
information in a dialogue competes
with the relevant units of information
and diminishes their relative visibility.
examples are: category lists avoid
too much irrelevant information
Answers | Verified | Latest Update 2026/2027
Save
Terms in this set (289)
which flowsheet template setting b. start removed
allows a builder to hide a flowsheet
group until the end user adds it?
a. topic
b. start removed
c. restrict rows
true or false: flowsheet rows, groups, false
and templates are stored in the same
master file
each flowsheet template is a record FLT
in what master file?
Groups and rows are records in what FLO
master file?
aims to create meaning behind tasks user experience
in the system by focusing on the
capabilities of users, how those users
feel, and the emotional connection
users have with the system.
,is a part of the overall user usability
experience and focuses on
understanding what users do, making
those tasks easy to accomplish, and
removing roadblocks to task
completion.
simple rules that you can use to heuristics
approximate a larger probable truth
from smaller truths that are easier to
observe. general rules of thumb that
can be used to help make decisions
heuristic where system should speak system matches real world
the users' language with words,
phrases, and concepts familiar to the
user. follow real-world conventions,
making information appear in a
natural and logical order.
examples are: print groups and
reports with intuitive names;
navigators, activities, and toolbars in
right order
heuristic where users should not Consistency and Standards
have to wonder whether different
words, situations, or actions mean
the same thing. Follow platform
conventions. examples are: words
like similar tools and uses org's
terminology and naming conventions
, heuristic where minimize user's recognition, not recall
memory load by making objects,
actions, and options visible. the user
should not have to remember
information from one part of the
dialogue to another. instructions for
use of the build should be visible or
easily retrievable. examples are:
toolbars and startup activities
provide shortcuts
heuristic where accelerators - Flexibility and Efficiency
unseen by the novice user - may
often speed up the interaction for
the expert user such that the system
can cater to both inexperienced and
experienced users. Allow users to
tailor frequent actions. examples are:
providing tools for workflows, but
not creating clutter and users ability
to re-arrange screen elements
(menus) to suit their needs.
dialogues should not contain simplicity and minimalist design
information that is irrelevant or rarely
needed. every extra unit of
information in a dialogue competes
with the relevant units of information
and diminishes their relative visibility.
examples are: category lists avoid
too much irrelevant information
