| Abstraction |
A view which represents essential aspects of interest while
hiding detail. |
| Assumption |
Something flagged as taken for granted or accepted as true
which may need to be verified. |
| Brainstorming |
A method of shared problem solving in which all members of
a |
| Business metric |
A measurable attribute of the business, such as cost,
inventory turns, time to market, or yield. |
| Collaboration |
A |
| Collaborator |
A target |
| Communicated Item |
A reference to an information item which is passed
from a role to a collaborating role
when an event triggers a task. |
| Communication |
The process of triggering a task in a collaborator and passing
it the requisite communicated items. |
| Domain |
The sphere of activity, concern, or function, focused on
during |
| Element |
A component of |
| Event |
Behavior in a |
| Facilitator |
An individual trained in building role models and
conducting |
| Group |
An organizational unit "owned" by a manager (of
some level). |
| Information Item |
An instance of a cohesive body of data known by a role or passed between roles via communication,
such as a document, database item, condition or result. Information items may be
references to roles. |
| Information Item
Type |
A concise description of the range of possible values of an
information item. |
| Instance |
A specific example of a role or information item. (E.g., May I. Helpu is an instance
of role service agent.) |
| Issue |
A point or matter of discussion, debate, or dispute. |
| Issue keeper |
The person ( |
| Leader |
The person ( |
| Message |
The |
| Model |
A schematic description of a system, theory, or phenomenon
that accounts for its known or inferred properties and may be used for further study of
its characteristics. . |
| Organization |
A structure through which individuals cooperate
systematically to conduct business. |
| Participant |
An individual who provides |
| Practice |
A set of techniques useful for the delivery of knowledge and skills in the
application of work. Practices are organized around disciplines, or subjects, and provide
the technological support for achieving practical purposes in a particular field. A
practice includes a complete set of elements needed to perform that practice, taking into
account the skills, knowledge, materials, tools, standards, processes
and support necessary to be successful. A practice includes the training, documentation,
helpdesk, infrastructure, domain tools, and organizational structure needed to effectively use the
practice. |
| Problem Statement |
Establishes the reason the |
| Process |
A connected prescription of the |
| Resources |
The people, assets, systems, equipment, labor, and raw
material needed by a |
| Responsibility |
Behavior for which a |
| Responsibility
Domain (RD) |
A synonym for Role which is used when it is
desirable to focus on how and by whom the scope of responsibilities
that define a Role are established. [See the Responsibility
Domain page.] |
| RM |
Role Model or Role Modeling |
| Role |
An abstraction representing a provider of a set of services
in fulfillment of a cohesive set of |
| Role Model |
A |
| Role Modeling |
The practice which negotiates, produces, documents and
maintains an evolvable, responsive, collaborative, empowered, business organization
described via a role model. [see the Role Modeling page] |
| Roleware™ |
Tools which support the creation, dissemination and
maintenance of role models and Role-based
business practices. [see the Roleware™ page] |
| Roleware™ modeler |
The person (role) responsible for developing stored graphic
and textual representations of an ™ tools. |
| RRC |
Role, Responsibilities, Collaborators |
| RRC Card |
An index card used to record |
| Scenario |
A narrative description tracing the behavior of a |
| Scenario log |
The physical medium in which a |
| Sponsor |
The person (RM and
provides resources for its accomplishment. An RM
may have more than one sponsor. |
| Stakeholder |
A role which has a direct interest
in a particular responsibility
domain. The human clients, collaborators
and sponsors of a domain are stakeholders. |
| Task |
A piece of work assigned or done by a |
| Team |
Individuals bound together in performance of a mission or |
| Trigger |
To initiate a task as a result of
an event.. |
| UseCase |
A simple statement of a situation the system must handle,
given in the form of a triggering event, the preexisting
conditions, and the desired outcome. A UseCase is intended to be independent of the
structure of the model and represents external
requirements and constraints. [Note that this usage of the term UseCase differs
from Jacobson's notion of "use-case-driven design", in which a UseCase
includes a scenario. We believe the
scenario should serve as a check on well-designed roles
and responsibilities. It is the UseCase
which is fundamental, not a prescribed sequence of events. Deriving - rather than
designing - the scenario leads to better allocation of roles and responsibilities.]
Nested UseCases can be used to store increasingly detailed,
specialized, or partial UseCases. |
| View |
A representation of part of an RM.
Views are established to provide focus and hide detail which is irrelevant to the matter
at hand. |
