Моделирование бизнес-процессов / Моделирование бизнес-процессов / I D E F / idef3

Instance

As pertaining to an activation, a specific case where one

of the pattern of possible activations is exhibited.

Interview

A face-to-face meeting with domain experts to pursue

some line of investigation.

Junction

An element of the IDEF3 Schematic Language providing

a mechanism to graphically display logical branching.

Kit

An assembly of diagrams, text, glossaries, decision

summaries, background information, or any portion of the

total IDEF3 description packaged for review and

comment. There are three types of IDEF3 kits: object

kits, scenario kits, and description kits.

Kit, Description

A compilation from the completed scenario and object

kits for a given project containing all the scenarios in the

IDEF3 description and their associated documentation.

An approved description kit would represent one of the

final deliverables in a development effort.

Kit, Object

Kits that address one or more objects and all or part of

their associated documentation. The items which may

appear in an object kit include Object Schematics,

elaborations, etc. packaged for review and comment.

Kit, Scenario

Kits that address one scenario and all or part of its

associated documentation. The items which may appear

in a scenario kit include Process Schematics, associated

UOB decompositions, UOB and link elaborations, etc.

packaged for review and comment.

Kit Contents Sheet

An extension to the kit cover sheet used when more space

is needed to list the contents of a kit.

Kit Cover Sheet

A structured document that identifies the material

assembled as an IDEF3 kit, the review requirements, and

an index to the contents of the kit.

Kit Review

A review and approval process used to validate IDEF3

process descriptions.

Link

A syntactic element of the IDEF3 Schematic Language

used to connect other IDEF3 syntactic elements. Links

denote significant relationships among UOBs, Object

States, and Objects. Examples of the types of relations

that can be highlighted by IDEF3 links include temporal,

logical, causal, natural, and conventional.

Link, Constrained

A specialization of precedence links that adds further

Precedence

constraints over and above the activation semantics of

simple precedence. See Link, Precedence.

Link, Dashed

A syntactic element of the IDEF3 Schematic Language,

used in Process Schematics to highlight the existence of a

(possibly constraining) relationship between two UOBs.

Dashed links carry no predefined semantics. For this

reason, they are often referred to as s or User-Defined

links.

Link, First-order

Relations that hold between first-order objects.

Link, Precedence

A syntactic element of the IDEF3 Schematic Language

used to express temporal precedence relations between

instances of one UOB and those of another.

Link, Relation

A syntactic element of the IDEF3 Schematic Language

used in Object Schematics to express additional relations

that hold between objects, between objects and object

states, between object states, and so forth.

Link, Second-order

Relations that hold between first-order objects and

second-order objects, properties, or relations; and

relations that hold between second-order objects,

properties, and relations.

Link, Strong transition

A specialization of transition links that conveys the

additional information that the object involved in the

originating state of a transition is the same object as that

in the final state of the transition.

Link, Transition

A syntactic element of the IDEF3 Schematic Language

used to express the relation transitions-to between some

source state(s) and some other destination state(s) in an

IDEF3 Object Schematic.

Method

An organized, single-purpose discipline or practice for

accomplishing some set of tasks. The IDEF methods are

specifically designed to accelerate the learning process

and help novice practitioners emulate the performance of

highly experienced individuals engaged in a particular

analysis or design activity. IDEF methods guide users

through a disciplined approach, consistent with good-

practice experience, to achieve consistently high levels of

performance (quality and productivity)

Model

An idealized system of objects, properties, and relations

that has been designed to imitate, in certain relevant

respects, the character of a given real-world system.

Models are idealized systems which are assumed to be

“close enough” to provide reliable predictors for the

predefined areas of interest within a domain.

Needs statement

A statement that records the source of the request (person

or project) and paraphrases the objectives of the project.

Note box

A syntactic element of the IDEF3 Schematic Language

that may be used to emphasize the participation of

particular objects or relations associated with the IDEF3

element to which it is attached, to tie in specific examples

of referenced data or objects (e.g., screen layouts), to

highlight special constraint sets associated with a given

elaboration, and so forth.

Object

An individual or class of individuals that participate in a

process. See individual.

Object, First-order

See individual.

Object, Second-order

Classes of individuals and first-order relations are second-

order objects. See individual and First-order link.

Object State

An individual or class of individuals that exhibit a

specific property or condition (generally indicated by an

adjective rather than a common noun). For example, a

weapon system development program undergoes a

number of different phases that may be viewed as state

transitions inaugurated by milestone decisions.

Occurrence

An instance of a UOB within a scenario activation.

“Occurrence” is also used to indicate the use of an IDEF3

pool item (i.e., Scenario, UOB, Object, Object State) in

some portion of an IDEF3 Process Description. For

example, the same UOB pool item may be used more than

once in the same Process Schematic.

Process

A real-world event or state of affairs involving one or

more individuals over some (possibly instantaneous)

interval of time. Typically, a process involves some sort

of change in the properties of one or more of the

individuals in the process. Sometimes referred to as

process instance.

Property

An abstract, general feature or characteristic that is

multiply instantiable; that is, it can be shared by distinct

individuals.

Purpose

The object or end to be attained by engaging in IDEF3

description development activity. That purpose may be

simply to document a process—in which case the

development of schematics and elaborations is an end

unto itself. In most cases, however, IDEF3 description

development is undertaken to assist with some discovery

or decision-making activities.

Purpose statement

A written declaration specifying the 1) main objective(s)

of the effort, 2) needs that the description must satisfy,

and 3) questions or findings that the client wants

answered. The purpose statement can be separated into

two parts, 1) defining a Needs Statement and 2) defining

the information goals in terms of how the process

description will be used. The purpose statement is

documented on an IDEF3 Description Summary form.

Referent

A syntactic element of the IDEF3 Schematic Language

used to refer to a UOB scenario or Transition Schematic

Relation

An abstract, general association, or connection that holds

between two or more objects. Like properties, relations

are multiply instantiable (i.e., it can be shared by distinct

objects. The objects among which a relation holds in an

instance are known as its arguments.

Relation, Temporal

A relation between temporal points or intervals such as

before, during, overlaps and so forth.

Role, Analyst

IDEF3 expert who is the primary developer of the IDEF3

description.

Role, Commentor

IDEF3 project team member responsible for reviewing

draft IDEF3 descriptions and making written critiques.

Role, Librarian

A person assigned the responsibility of maintaining files

of documents, making copies, distributing IDEF3 kits,

and keeping records.

Role, Project leader

An administrative role that carries the responsibilities for

overseeing and guiding an IDEF3 description

development effort. In particular, the project leader is

ultimately responsible for the outcome of the description

development effort, team organization and leadership, and

schedule and budget management.

Role, Reader

IDEF3 project team member responsible for reviewing

draft IDEF3 descriptions but who is not responsible for

providing written comments.

Role, Reviewer

IDEF3 project team member knowledgeable of the

application domain and/or the IDEF3 method and

responsible for reviewing and/or commenting on draft

descriptions and documents. Team members and domain

experts can be reviewers. See also reader and

commentor.

Role, Team member

A person involved with the IDEF5 ontology description

project.

Schematic

A connected diagram constructed from the lexicon of the

IDEF3 schematic language, in accordance with the

syntactic guidelines of the language. A visualization,

produced using the IDEF3 schematic language, that aids

in the construction of process descriptions.

Schematic, Process

An IDEF3 schematic supporting the capture and display

of a process-centered view of a scenario.

Schematic, Object

An IDEF3 schematic supporting the capture and display

of an object-centered view of one or more scenario(s) of

interest.

Schematic, Transition

A type of Object Schematic characterizing the state

transitions traversed by participating objects in an

instance of the scenario (or process kind).

Schematic, Enhanced

A Transition Schematic that includes context-setting

Transition

information about the objects and relations that are

relevant to the scenario but which do not exhibit the state

change behavior of direct interest.

Scenario

In the context of its decomposition, any UOB is a

scenario.

Source material

A textbook, a research article, an enterprise-specific

document such as a policy manual or a procedure manual,

a set of an interview notes, or direct observation notes that

has relevant information to the process description

development project.

System

A collection of physical and/or conceptual objects that

work together to achieve common objective.

Unit of Behavior (UOB)

A term used in IDEF3 to describe types of “happenings.”

Concepts such as function, process, scenario, activity,

operation, decision, action, event, procedure, and so forth

each represent “happenings” involving some

circumscribed behavior. The term UOB is used to

encapsulate concepts such as these.

UOB Box

A syntactic element of the IDEF3 Schematic Language

used to represent a real-world process.

UOB, Child

A UOB in a decomposition.

UOB, Parent

A UOB, acting in the role of a scenario, that establishes

the context for a process description.

Validation

The process of checking and ensuring that the IDEF3

process description constructed is both syntactically and

semantically correct. A primary means of validating

IDEF3 process descriptions is through the review and

approval of kits.

Validation, Syntactic

The process of checking and ensuring that the IDEF3

schematic constructed conforms to the grammatical rules

of the IDEF3 language.

Validation, Semantic

The process of checking and ensuring that the statements

made in the IDEF3 description accurately capture the

assertions of the domain expert.

Viewpoint

The perspective taken while examining or describing a

system or process. Role-specific and objective

viewpoints are captured using IDEF3’s UOB

decomposition mechanism.