Filter
Top Products
Runtime client. In FlowMark: the user interface for
working with process templates, process instances,
work lists, and work items. See also
Runtime
.
S
screen layout. The design and specifications of the
image that the user sees on the screen of a system.
See also
report layout
.
service encounter. Any point of contact with your
customer. See also
moment of truth
.
shredder. A machine for the destruction of documents.
simulation. A mock-up version or prototype of the new
process and job design used to test assumptions before
final implementation.
sink. In FlowMark: the symbol that represents the
output container of an activity, process, or block. See
also
output container
and
source
.
skill. An ability, proficiency, expertness of a person
that comes from training, practice, and experience.
source. In FlowMark: the symbol that represents the
input container of an activity, process, or block. See
also
input container
and
sink
.
staff. In FlowMark: the people (and their roles,
organizations, and levels) who execute the process
instances. Staff is defined in a FlowMark database.
See also
role
and
organization
.
staff resolution. The process FlowMark uses to
decide which worklists to add a process to.
start activity. In FlowMark: an activity that has no
incoming control connector. A start activity becomes
ready when the process or block that contains it starts.
There can be more than one start activity in a process
or block.
start condition. A control setting that determines
when an activity with incoming control connectors can
start. It also determines when a process path or
workflow can start. See also
condition, exit condition
,
and
transition condition
.
start criteria. A control setting for activities on
PLOVCs or JLOVCs that determines when an activity or
a process path can start. See also
exit criteria
.
strategy. A pattern of goals, policies, and plans that
specify how an enterprise is to function over a given
period of time. A strategy can specify areas for product
development and marketing as well as techniques for
responding to competition.
subject expert. A specialist in a particular area of
expertise, such as workflow management.
subprocess. A lower level process. Processes can
be refined into subprocesses through the HSD modeling
techniques. See also
hierarchical structure diagram
(HSD)
and
process
.
In FlowMark: a process instance that is started by a
process activity.
substitute. In FlowMark: the person to whom an
activity is automatically transferred if the person to
whom the activity is assigned is flagged as absent.
symbol. A graphical representation of an object or
thing, which may be abstract in nature; for example, a
line with an arrow is the symbol for a data or
information flow.
system. A set of processes with a common aim that
act on data or information using input and producing
output. Usually used in the context of
information
system
or
data processing system
.
system development. The design, code, test,
implementation, and maintenance of an information
system. Can also denote a business function that
performs systems development.
system function. A component or module of a
system. A system can be refined into system functions
using the HSD modeling technique. See also
hierarchical structure diagram (HSD)
and
system
.
T
task. The lowest level of activity or unit of work.
Tasks belong to the physical business models. There is
no implied sequence or order in performing tasks within
an activity. Activities can be refined into tasks using the
HSD modeling technique. See also
hierarchical
structure diagram (HSD)
and
activity
.
task flow. In process-based applications, a task flow is
part of a control flow. See also
control flow, workflow,
event flow
,
and document flow
.
TCP/IP. Transmission control protocol/Internet
protocol. A commonly used protocol for various
network environments, such as Internet, Host
communications, and LANs. FlowMark uses either
TCP/IP or APPC. See also
APPC
.
technique. A procedure for doing anything in an
orderly way; a method.
time line. A notation on the PLOVC and the JLOVC
that shows the time between individual activities as well
as for the entire process path or job; for example, the
46 FlowMark V2.3 Design Guidelines