Glossary ​
The glossary explains the terms used in ADOxx.
A ​
Description | |
---|---|
ADOxx Binary Language (ABL) | File format, in which application libraries can be saved (exported). |
Accelerator | Letter marked by underlining. Occurs in titles of menus and menu options, in field and list names of input fields and in chapter headings and attribute names of ADOxx Notebooks. By entering the accelerator (sometimes in connection with the <Alt> key) you can call functions and navigate inside both windows and ADOxx Notebooks via the keyboard. |
Access Rights | The access rights (read-write/read-only/no access) to an ADOxx model group are assigned to the ADOxx user groups in the Development Toolkit. |
Activity | Smallest entity of a business process. Activities describe what is done in a business process. |
Activity, cooperative asynchronous | An activity carried out by several performers who work together but not at the same time. |
Activity, cooperative synchronous | An activity carried out by several performers who work together at the same time. |
ADL Export | Functionality in the Import/Export Component in the Modelling Toolkit and in the Model Management in the Development Toolkit. Using the ADL export, you can export ADOxx models and ADOxx model groups as well as ADOxx attribute profile and ADOxx attribute profile groups to ADL files. |
ADL Import | Functionality of the Import/Export Component in the Modelling Toolkit and in the Model Management in the Development Toolkit. Using the ADL import functionality, you can import ADL files containing ADOxx models and ADOxx model groups as well as ADOxx attribute profile and ADOxx attribute profile groups into ADOxx and store them in the ADOxx database. |
ADOxx Attribute Profile | Attribute Profile |
ADOxx Attribute Profile Group | Attribute Profile group |
ADOxx Browser | Special result window used in the Modelling Toolkit (in the components Modelling, Analysis, Simulation and Evaluation) as well as in the Development Toolkit (in the components Library Management and Attribute Profile Management). The results are represented in tabular form and can be displayed graphically. They can also be printed out, saved in a file in TXT format (table and text), RTF format or HTML format. |
ADOxx Comparable Representation (ACR) | File format, in which simulation and analysis results, which are displayed in the ADOxx browser can be saved. ACR-files are needed in the Evaluation Component for the comparison of results. |
ADOxx Component | Part of the Modelling Toolkit or Development Toolkit. These group various similar functionalities into a component, like Modelling, Import/Export or Library Management |
ADOxx Configuration | A version of the Modelling Toolkit in which the components are configured according to specific needs. The minimal ADOxx configuration consists of the modelling component. |
ADOxx Database | All ADOxx data is stored in the ADOxx database. |
ADOxx Default Language | The language ADOxx starts by default with. The default language is English. |
ADOxx Definition Language (ADL) | Language in which ADOxx models and ADOxx model groups as well as ADOxx attribute profile and ADOxx attribute profile groups can be saved (exported). ADL files can then be imported and edited within the ADOxx Modelling Toolkit on other computers which may not be connected to a network or which are connected to different databases. |
ADOxx Directory | Directory in which ADOxx has been installed. Contains the applications for the installed ADOxx version, additional resources and (if applicable) the database administration tools. By default a sub-directory of C:\\Program files\\BOC\\... . |
ADOxx Explorer | Tool providing an overview of the models/model groups stored in the ADOxx database and offering various manipulation possibilities. |
ADOxx Inspector | Tool that supplies the ADOxx user with various details about the active modelling environment. |
ADOxx Installation Directory | ADOxx directory |
ADOxx Model | Aggregation of objects of various classes that serve to represent the essential aspects of the real world for the ADOxx user. Also simply called "models". The models serve as a basis for components such as analysis, simulation and evaluation. |
ADOxx Model Group | Group, in which ADOxx models are referenced. Access rights for ADOxx user groups and the ADOxx users referenced therein are defined for an ADOxx model group. |
ADOxx Navigator | Tool which shows an overview of the active model. The part of the model, which is currently visible in the model window is highlighted and can be used for navigating through the model. |
ADOxx Notebook | Special dialog window where the attributes of objects, connectors, attribute profiles, models or libraries may be changed. |
ADOxx Program Folder | ADOxx directory |
ADOxx Rights | Rights of an ADOxx user to access the Development Toolkit and/or Modelling Toolkit. |
ADOxx User | User in the ADOxx system(#a). The ADOxx users stored in the ADOxx database are displayed in the user list. ADOxx users may be exported (optionally including ADOxx user groups) to UDL files or imported from UDL files. |
ADOxx User Group | Group, in which ADOxx users are referenced. An ADOxx user group has access rights to ADOxx model groups and the ADOxx models referenced within these. The ADOxx user groups stored in the ADOxx database are displayed in the user group list. ADOxx user groups may (optionally including ADOxx users) be exported into UDL files or imported from UDL files. |
ADOxx Window | Graphical user interface of ADOxx. You can call the individual components from within the ADOxx window. |
AdoScript | Script language allowing to implement customised functionality extensions in ADOxx. Moreover AdoScript enables the call of web services, external programs and functions in DLLs. |
Agent | Created by an ADOxx user in the Simulation Component. Calculates user-defined simulation results during the simulation. An agent's results refer only to the objects specified by the user. |
Agent Calendar | Description of the period of time during which an agent evaluates the simulation algorithm Workload Analysis. |
Alignment Function | Functionality in the Modelling Component, which allows you to align the objects and connectors of an ADOxx model with the help of predefined or user-defined parameters. Available in the "Edit" menu. |
Analysis (component) | A component of the Modelling Toolkit, in which queries and reports can be run on your models. The queries are formulated in a language called AQL. A wizard to build AQL queries is available also available. |
Analytical Evaluation (Calculation) | Evaluation mechanism for dynamic models in the Analysis Component of the Modelling Toolkit. The models are not simulated by this kind of evaluation but calculated mathematically. |
Animation | Passive component in the simulation algorithms "Workload Analysis (fixed time period)" and "Workload Analysis (steady state)", which is responsible for graphically representing the task stacks of the different performers in the Static model being simulated. Different from offline animation. |
ADOxx Protocol File (APF) | File format in which the results of a "Capacity analysis" or "Workload analysis" simulation run can be saved. APF files serve as input for the offline animation function to play through the simulation again observing the times and optionally adding breakpoints at certain times. |
Application Library | Combination of a Dynamic Library and a Static Library library. The two libraries contain the classes and the relations for the models of the model types defined. The application libraries stored in the ADOxx database are displayed in the Library Management component. Exactly one application library is assigned to each ADOxx user. |
Application Model | Combination of at least one dynamic model and exactly one Static model. The definition of an application model is necessary for the Simulation Component to carry out the simulation algorithms "Capacity Analysis" and "Workload Analysis". |
ADOxx Query Language (AQL) | Query language used to query lists of objects or models. It enables you to assign performers and allocate resources dynamically in the Modelling Component. You can also enter selection criteria for the functions "global change" and "model search". In addition, you can run queries in the Analysis Component and generate predefined queries and predefined evaluation queries when you edit the library attributes in the Library Management. |
Assessment | Functionality in the Modelling Component in the Modelling Toolkit. This functionality enables you to evaluate dynamic models according to time and cost criteria. |
Attribute | Property of a library, a model, a class, an object, a relation or a connector. Attributes are usually filled with values (=attribute values) through the ADOxx Notebooks. |
Attribute-dependent Graphical Representation | Representation of objects and visualised attribute values on the drawing area depending on concrete attribute values. An attribute-dependent graphical representation can be defined while customising in the Development Toolkit within the Library Management component. See also GraphRep |
Attribute Filter | Filter function for the Documentation Component. Using the attribute filter, you can select the attributes you want to transfer to the documentation (e.g. HTML, XML, RTF files). |
Attribute Mode | Presetting in the application library for the Documentation Component. An attribute mode defines, which attributes of a class should be transferred to the documentation (e.g. HTML, XML, RTF files). |
Attribute Profile | Concrete instance of an attribute profile class. An attribute profile represents one or more attributes, which are reused for any objects and can be maintained in the Attribute Profile Management. |
Attribute Profile Class | Template, according to which the attribute profiles are generated by instancing. An attribute profile class or its attribute profiles are described by a quantity of attributes, which are assigned with concrete values in an attribute profile. |
Attribute Profile Group | Grouping, in which attribute profiles are summed up, similar to folders or directories. |
Attribute Profile Management | A component in the Development Toolkit, in which you can instance, edit or delete attribute profiles as well as create, rename and delete attribute profile groups. |
Attribute Profile Reference (ATTRPROFREF) | An attribute type for referencing an attribute profile. |
Attribute Value | Value of an attribute, being a concrete instance of a characteristic. |
Automatic Random Generator | Random generator, automatic. |
B ​
Description | |
---|---|
Balanced Scorecard (BSC) | Instrument to translate company's mission and strategy to a clear system in order to measure the performance. This system creates the framework for a strategic performance measurement and management system. The Balanced Scorecard focuses above all on the financial targets, but contains also the business drivers of these financial targets. |
Bend-point | Point where a connector changes its direction. |
Microsoft Bitmap (BMP) | Graphic file format, in which diagrams/graphics which have been generated from models can be saved. BMP files may be opened or inserted into graphics programs and may be edited further there or integrated into other applications such as word processor applications. |
BPMS Paradigm | (=Business Process Management Systems-Paradigm). Framework for the management of business processes. This framework consists of five subprocesses: "Strategic Decision Process", "Re-engineering Process", "Resource Allocation Process", "Workflow Process" and "Performance Evaluation Process". It was developed by the BPMS group of the Institute for Applied Computer Science and Information Systems, Department of Knowledge Engineering, University of Vienna. |
Browser | ADOxx browser |
Business Process | Number of logically connected activities whose execution should meet a business objective. |
Dynamic Library | Classes for modelling dynamic models. The classes of a Dynamic Library are derived from the classes of a dynamic meta model. A Dynamic Library is part of an application library. A dynamic model always refers to exactly one Dynamic Library. Dynamic libraries are defined while ADOxx is developed |
Modelling Toolkit | ADOxx component in which the ADOxx user works. In its standard configuration it consists of the following components: Modelling, Analysis, Simulation, Evaluation and Import/Export. |
Dynamic (Abstract) Meta Model | Classes predefined in ADOxx for modelling dynamic models. The classes of a Dynamic Library are derived from the classes contained in the dynmic (abstract) meta model. |
Dynamic model | 1 ADOxx model of a dynamic models. Comes into existence by instantiation of classes of a Dynamic Library. 2 Model type of the ADOxx 1.5 Dynamic Experimentation Library. |
C ​
Description | |
---|---|
Calculation | Analytical Evaluation. |
Calendar | 1 Agent Calendar, Performer Calendar, Process Calendar. 2 CALENDAR; attribute type for defining the period of presence of performers ( Performer Calendar) or the period of occurrence (frequency) of business processes ( Process Calendar). |
Capacity Analysis | Simulation algorithm in the Simulation Component of the Modelling Toolkit which "plays through" dynamic mdoels and assigns activities to the performers. An application model serves as input for capacity analysis. This analysis enables you to plan your personnel capacity demand. The results of the capacity analysis are displayed in the ADOxx browser. |
Capacity Management (component) | Special definition of the Dynamic Evaluation Modules. Used for period-related calculation of the organisational/personnel capacity requirements. |
Class | Static template according to which objects are created by instantiation. A class or its objects, are described by a set of attributes, which are filled with concrete values within an object. The class "Performer", for example, has among others the attributes "Name", "Availability" and "Hourly wages". |
Class Attribute | Attribute of a class, which refers directly to the class and does therefore not occur in objects of this class such as the attribute "Info text" in an ADOxx modelling class (See: Information icon in Notebooks). |
Class Filter | Filter function for the Documentation Component. Using the class filter, you can select the classes, in which objects should be transferred to the documentation (e.g. HTML, XML, RTF files). |
Class Panel | Button panel, which contains exactly one button for each class that can be modelled. The class panel represents the second part of the modelling bar - between the edit button and the relation panel. |
Client | A client is a software module which requests services from a server, usually via a network. |
Client/Server | Computer system consisting of a client and a server. |
Comparison of Results | Functionality of the Evaluation Component in the Modelling Toolkit. Compares results of analysis and simulation in tabular and graphical form. The results are displayed in the ADOxx browser. |
Component | ADOxx component |
Component Access | Configuration of the access to the components of the Modelling Toolkit. The component access can be defined individually in the Development Toolkit for ADOxx user groups and for each ADOxx user, whereby the ADOxx configuration can be customised |
Component Bar | Panel, by default below the menu bar in the ADOxx window. The smart-icons visible show the available components. To the right of the component bar, usually the quick access bar can be found. |
Component Configuration | Functionality of the Component Management in the Development Toolkit. Additional ADOxx components can be included here by entering a new licence number. |
Component Management | Component of the Development Toolkit, in which the components of the Modelling Toolkit can be configured. |
Configuration, current | The current configuration ( ADOxx configuration) specifies which functions of the components of the Modelling Toolkit are available. |
Connector | Instantiation of a relation. Connection/link between two objects (e.g. "Subsequent"). |
Connector Attribute | Attribute of a connector. |
Connector Mark | Visualisation of connection joints for connectors that extend over page boundaries. (See connectors, page layout). Connector marks are very useful in model documentation. |
Connector Numbering | Assigning numerical or alphabetical identifiers to connector marks. The connector numbering is non-ambiguous within a model. |
Context Menu | Context-depending menu. Appears when you press the right mouse-button. Provides functionality suitable for the particular situation. |
Cooperative Activity | An activity, which is executed by more than one performer (such as a meeting). |
Cost Cutting Component | Additional ADOxx component, which can be integrated into the Evaluation Component of the Modelling Toolkit. The Cost Cutting Component is not part of ADOxx standard configurations. The Cost Cutting Component supports cost optimisation, especially in the area of overhead costs. |
Cost Driver | Establishes the relation between costs, processes and calculation objects. The cost driver is a measure of the costs caused by the business processes and subprocesses. |
Cost Driver Quantity | The measurable output of a cost driver. Each output-induced (OI) process has a cost driver quantity. |
Comma Separated Value (CSV) | Text file format in which contents from the ADOxx browser can be stored and transferred without loss to a spreadsheet software. |
Cursor Key | Arrow keys on the keyboard, using which you can navigate to the left, the right, upward and downward. |
Customer Number | An unambiguous alphanumerical identifier for each customer. The customer number must be entered when installing ADOxx. |
Customising | Adapting ADOxx to a customer's demands without programming effort. Via customising, definition of the page layout, the model types, predefined analysis queries and plans as well as predefined evaluation queries and simulation mechanisms is performed. |
Cycle Time | Time that (on average) passes between the start of a dynamic model and its end. |
D ​
Description | |
---|---|
Database Administration | ADOxx component, which the database administrator uses to administrate the ADOxx databases. The database administration contains the programs to create, store and restore ADOxx databases. |
Day Profile | Template, which describes a performer's time of presence or the stochastic occurrence (frequency) of a business process per day. Day profiles are used in the Agent Calendar, the Performer Calendar and the Process Calendar. |
DB2 | DBMS for Windows, Linux, OS/2 and other operating systems (owner: IBM). |
DBMS | DataBase ManagementSystem. |
Default Language | ADOxx default language. |
Depth Search | Process to go through objects, i.e. to automatically process the objects and relations of a model in the RTF generation in the Documentation Component. Starting from a start object, all objects, which are directly connected to this start object, will be processed. Unlike the width search the process will not be carried out gradually, but the relations of the objects will be followed until an object, which has no further relation, is reached. |
Development Toolkit | ADOxx tool needed to manage ADOxx users, ADOxx libraries, ADOxx models and ADOxx attribute profiles. The Development Toolkit consists of the User Management, Library Management, Model Management, Attribute Profile Management and Component Management components. |
Distribution | DISTRIBUTION; Attribute type for statistic distribution used for assigning variables. |
Document Model | Model type of the ADOxx 1.5 Dynamic Experimentation Library to illustrate the documents used in Dynamic models. |
Documentation (component) | Function in the Import/Export Component of the Modelling Toolkit. Using the Documentation Component, you can transport ADOxx models to specific target formats (e.g. RTF, HTML, XML), whereby you can distribute the model contents including graphic representation integrated into documents or via the Intranet. |
Domain | A domain is a group of computers as part of a network using a common directory database. A domain is organised in different levels and is administered as one unit with common rules and procedures. Every domain has a unique name. (Definition from "Windows Help".) |
Drawing Area | Rectangle in the model editor of the Modelling Toolkit. The drawing area is at least big enough so that it encloses all objects and connectors of a model. The drawing area is represented in the modelling window by a grey outline. It is part of the workspace. |
Drawing Mode | Mode of the model editor in which objects and connectors can be drawn. You can switch from editing mode to drawing mode by clicking on a button in the modelling bar. |
Drawing Space | Area of a model window, where objects and connectors can be placed. The drawing area is a part of the drawing space. |
DSSSL | Document Style Semantics and Specification Language (DSL file); DSL files are used in the Documentation Component, to convert SGML files to any format (e.g. HTML, RTF, XML). |
DTD | Document Type Definition; DTD are used to define the structure of documents (e.g. in the formats XML, SGML) . |
Dynamic Evaluation Modules | Additional ADOxx Component, which can be integrated to the Evaluation Component of the Modelling Toolkit. The component "Dynamic Evaluation Modules" is not included in ADOxx standard configurations. The Dynamic Evaluation Modules enable period-related evaluations (e.g. Human Resources Management). |
E ​
Description | |
---|---|
E-Business | E-Business includes all business activities, i.e. the internal and external business processes of an organisation, which are supported by Internet technology. |
Edge Centre | For each connector the ADOxx user can move the "centre". By moving the edge centre, the transition condition of a connector of type "Subsequent" may be arranged along this connector as you like. Alternatively, the edge centre may automatically be placed in the geometrical centre of the connector. This is useful to position the text displayed along a connector at a position at which it can be clearly read. |
Edit Button | Topmost button within the modelling bar. With this button the cursor in the model editor can switch from drawing mode ("pen") to editing mode ("arrow"). |
Editing Mode | Mode in the model editor, in which it is possible to edit (i.e. select, move, copy, cut, paste, delete etc) objects and connectors. You can switch from drawing mode to editing mode either by clicking on the editing button in the modelling bar or by right-clicking on the drawing area in the modelling window. |
Windows Enhanced Meta Files (EMF) | Graphic file format, in which graphics, which have been generated from models can be stored. EMF is based on vector graphics. This way EMF graphics can be scaled (resized) freely. EMF files can be inserted into graphic programs and be further edited there or connected to any applications (e.g. spreadsheet calculation programs). |
Empty Space Tool | Tool in the Model editor that helps creating empty spaces in crowded models by moving the objects. Part of the Modelling bar. |
Enumeration | ENUMERATION; attribute type with predefined attribute values. The valid value is exactly one of the set of values supplied. |
Enumeration List | ENUMERATIONLIST; attribute type with predefined attribute values. The value valid may be zero, one or more elements of the value range defined. |
Evaluation Agent | Agent |
Evaluation (component) | Component of the Modelling Toolkit. Supports both the core "evaluation" activity in re-organisation projects and the "Performance Evaluation Process" within the BPMS Paradigm. |
Evaluation Queries | Functionality of the Evaluation Component in the Modelling Toolkit. Evaluation queries on models serve to extract the model content (especially with regard to the simulation results). These can then be displayed in a clearly structured way in the ADOxx browser. Depending on your particular library configuration various predefined evaluation queries may be available. |
Evaluation Queries, predefined | Predefined evaluation queries are defined in the Development Toolkit for business process libraries and working environment libraries. They are made available to the ADOxx user by special menu options in the Evaluation Component of the Modelling Toolkit. The results of predefined evaluation queries are displayed in the ADOxx browser. |
Execution Time | Time during which an activity belonging to a business process is executed. |
Exit Button | Button in the top left of the window panel, which closes the window when you double-click on it. |
Export | ADL-Export, XML-Export. |
Export Migration Assistant | Functionality in the Development Toolkit. The export migration assistant supports you in exporting application libraries, ADOxx users, ADOxx user groups, ADOxx models and ADOxx model groups. |
Expression | 1 EXPRESSION; attribute type which determines the value of an attribute using a flexible calculation rule, whereas the attribute value is defined by other attributes. 2 AQL expression. |
Express Message | Specific form of a message ( ADOxx mail) to a logged in ADOxx user. An express message will be immediately delivered to the receiver and shown in a pop-up window. |
External Coupling | Coupling of an external tool to ADOxx. |
F ​
Description | |
---|---|
Flowmark Definition Language (FDL) | Language for describing FlowMark models. FDL files can be imported into the Workflow Management system WebSphere MQ/MQSeries Workflow/FlowMark from IBM. |
FDL Generation | Functionality of the Import/Export Component in the Modelling Toolkit. This functionality generates FDL files from models (in order to then import them into FlowMark). |
Floating-Point Number | DOUBLE; attribute type for decimals (up to six decimal places). |
FlowMark | MQSeries Workflow. |
Flowmark Audit Trail | Audit trail of business processes carried out by FlowMark. |
G ​
Description | |
---|---|
Global Change | Simultaneous change of attribute values of several objects in one or more models. The attributes to be changed are selected by entering standardised or user-specific search criteria. |
Global End | Terminates a business process including those processes that call it (i.e. may appear within a subprocess). A global end represents the termination of the whole processing. |
GraphRep | [TBD] |
Groupware System | Computer system supporting teamwork by providing services like e-mail, document management, discussion forum and so on. |
H ​
Description | |
---|---|
Hyper Text Markup Language (HTML) | Language / file format, in which the contents of the ADOxx browser or model content generated using the Documentation Component can be saved. HTML files can be displayed in web browsers. |
Human Resource Management (component) | Specific definition of the dynamical evaluation modules. Used for the period-related calculation ( time-related versioning) of the organisational/personnel capacity requirements. |
I ​
Description | |
---|---|
Import Migration Assistant | Functionality in the Development Toolkit. The import migration assistant supports you in importing application libraries, ADOxx users, ADOxx user groups, ADOxx models and ADOxx model groups. |
Import/Export (component) | Component of the Modelling Toolkit in which ADL Import, ADL Export and FDL Transformation can be called. |
Informix | DBMS for Windows (owner: IBM). |
Input Parameter Combination | Parameter for simulation and analytical evaluation (calculation). When a Simulation or Analytical Evaluation is started, an input parameter combination must be selected. This specifies on which attributes the results should be calculated. Depending on the input parameter combination different results will be calculated. Additional input parameter combinations can be defined in the Development Toolkit ( Library Management, library attribute "Simmapping"). |
Inspector | ADOxx Inspector. |
InstallShield | Software, using which you can install ADOxx via Windows (manufacturer: Macrovision Corp.). |
Instance | 1 Object 2 Attribute Profile 3 Process Instance. |
Instantiation | 1 Creating an object of a class or a connector of a relation 2 Creating an attribute profile of an attribute profile class. |
Integer | INTEGER; attribute type for an integer (whole number). |
Inter-Model Reference | INTERREF; attribute type used to create a reference to another ADOxx model or to an object in a different ADOxx model. |
Internet | Worldwide computer network. |
Intranet | Computer network, which is restricted to one organisation (company, department) - in contrast to the Internet. |
ISO9000 | This umbrella term is commonly used for the series of norms ISO 9000 ff. These regulations of the International Standards Organisation (ISO) aim at creating a quality assurance system. They include a maximum number of twenty core elements. Depending on the type and size of a company's business operations, the company may acquire a certificate according to the norms ISO 9001, 9002 or 9003. An accredited certifier (= one recognised by the commission) awards this certificate. It certifies that the enterprise quality assurance system conforms with the core elements of the respective norm. The certificate according to ISO 9001-9003 is usually regarded as guarantee for high-quality products and/or services. It is a commonly applied criterion when selecting suppliers especially in the public services and industrial sector. |
J ​
Description | |
---|---|
JPG | JPEG; graphic file format of the Joint Photographic Experts Group, in which graphics generated from models can be saved. JPG files may be opened or inserted into graphics programs and may be edited further there or integrated into other applications such as word processor applications. |
K ​
Description | |
---|---|
Knowledge Management | Knowledge Management covers all activities of an organisation which deal with supplying and maintaining knowledge. |
L ​
Description | |
---|---|
LEO | Meta-language for customising and specifying attributes. Shows the contents of data structures in text form ( AdoScript). |
LEOgram | Sequence of LEO elements. |
Library | Number of user-defined classes for modelling. Both ADOxx 1.5 Dynamic Experimentation Library and ADOxx 1.5 Static Experimentation Library can be defined in ADOxx. Libraries are defined during ADOxx customising. |
Library Attributes | Attributes of libraries. |
Library Configuration | Functionality of the Library Management in the Development Toolkit. Using the library configuration, you can edit and check class and library attributes ( customising). |
Library Export | Export of an application library into an ABL file to transfer data into a different ADOxx database or for backup purposes. This functionality of the Library Management is located in the Development Toolkit. |
Library Import | Import of an application library from an ABL file and then save it in the ADOxx database. Functionality of the Library Management in the Development Toolkit. |
Library List | List that shows all the business process and Static libraries stored in the ADOxx database. From the library list you can import, export and delete libraries. |
Library Management (component) | Component of the Development Toolkit, which is used to import and export application libraries and to configure library attributes (= library configuration). The Library Management also contains an import and export migration assistant with the help of which the complete contents of the ADOxx database (models, model groups, application libraries, users and user groups) can be exported (back-up) and imported into a different ADOxx database (data transfer). |
Licence Number | Customer-specific number for configuring ADOxx and creating ADOxx databases. A licence number consists of the encoded customer number and the key for the available components of the Modelling Toolkit (depending on the customer-specific configuration of ADOxx). |
Longstring | LONGSTRING; attribute type for text of up to 32.000 arbitrary symbols. |
Lotus Notes | Groupware and document management system (manufacturer: IBM). |
LOVEM | Line of VisibilityEngineering Methodology; business process modelling method of the IBM Corp. |
M ​
Description | |
---|---|
Main Reference | Classification of references to determine the referenced models (for instance when opening models including referenced models) outgoing from a model. Main referenced models will be processed like the start model, i.e. all references contained in this model will be followed, if the restriction of depth allows it. (see also side reference). |
Management Office | Software tool suite of BOC Asset Management GmbH. The Management Office consists of the Strategy and Performance Toolkit ADOscore, the Business Process and Knowledge Management Toolkit ADONIS, the Supply Chain Management Toolkit ADOlog and the IT Service and Architecture Management Toolkit ADOit. |
Manual Random Generator | Random generator, automatic. |
Max. Length of Loops | Parameter of the Analytical Evaluation. Determines how many objects a loop (in a model) may contain at most, before the evaluation is assumed as a never-ending loop. |
Max. Number of Paths | Parameter of the Analytical Evaluation. Determines how many different paths a model may contain before the evaluation is cancelled. |
Max. Start Time Period | Attribute of objects of the class "Activity". The maximum start time period specifies, for how long a cooperative activity will at most be delayed until sufficient performers are available for executing the cooperative activity. This attribute is only evaluated by the simulation algorithm " Workload Analysis". |
Menu Bar | Panel between the window panel and the toolbar in the ADOxx window which contains the menu options for the activated ADOxx component. |
Messages | ADOxx mail. |
Meta Model | Describes the modelling classes of a model type and their dependences. |
Method Library | Application library. |
Microsoft SQL Server | DBMS for Windows (owner: Microsoft Corp.). |
Microsoft SQL Server Express Edition | DBMS-Runtime for Windows (owner: Microsoft Corp.). |
Migration | Transfer of an application library, ADOxx database or ADOxx version to a new or changed ADOxx application library, database or version. |
Model | ADOxx model. |
Model Access | Access right. |
Model Attribute | Attribute of a model. |
Model Comparison | Comparison of two models. Differences found will be displayed in the ADOxx browser. |
Model Editor | Graphically oriented editor in the Modelling Component, used for creating models. |
Model Group | ADOxx model group. |
Model Group Management | Functionality of the Model Management in the Development Toolkit. With the help of the model group management you can create, rename, move or delete ADOxx model groups, create, copy, move or delete model references as well as define access rights of ADOxx user groups to ADOxx model groups. |
Model History | Supports the navigation between models. For instance, you may switch between a main model and its sub model. |
Model Management (component) | Component of the Development Toolkit, in which the model access can be defined. |
Model Pool | Quantity of all ADOxx models saved in the ADOxx database which are not assigned to any ADOxx model group. Can be accessed via model group management. |
Model Reference | 1 Reference of an ADOxx model group to an ADOxx model in the model group management. ADOxx models may be referenced in any number of ADOxx model groups. 2 Inter-model reference (INTERREF) to an ADOxx model, created in the Modelling Component. |
Model Search | Functionality of the Modelling Component of the Modelling Toolkit. Using the model search, you can search for models that are stored in the ADOxx database. You can either search according to model attributes or within the process hierarchy. |
Model Type | In ADOxx version 1.5 one or several model types can be defined in a ADOxx 1.5 Dynamic Experimentation Library and in a ADOxx 1.5 Static Experimentation Library. In the ADOxx 1.5 Experimentation Library we distinguish between Dynamic models, company maps (business process library) and working environment models (working environment model). |
Model Window | Window in which a model is displayed and edited. |
Modelling (component) | Component of the Modelling Toolkit, in which Dynamic models and Static models are created, using the model editor. |
Modelling, bottom-up | Approach to creating models. When modelling bottom-up you start with detailed small models ("micro perspective") and gradually combine them to a bird's-eye view on the process in question by reducing their complexity. |
Modelling, top-down | Approach to creating models. When modelling top-down you start with a bird's-eye view on a given process and gradually go into more detail ("micro perspective"). |
Modelling Bar | Button panel, by default on the left-hand side of the ADOxx window. The modelling bar consists of the edit button, the empty space tool, the class panel and the relation panel. |
Mode | A mode is a (sub)set of the objects and connectors contained within an ADOxx model. By selecting different modes (menu "View"), some extra objects may be made available and some existing objects may be hidden. |
Mouse Access | It is possible to block mouse access for each class and relation during modelling separately. This means that none of the objects of that particular class or none of the connectors of the particular relation can be selected. |
MQ Series Workflow | WebSphere MQ. |
MSDE | Microsoft DatabaseEngine; DBMS for Windows (owner: Microsoft Corp.). |
MS SQL Server | DBMS for Windows (owner: Microsoft Corp.). |
N ​
Description | |
---|---|
Navigator | ADOxx Navigator. |
Notebook | ADOxx Notebook. |
Notes | Lotus Notes. |
O ​
Description | |
---|---|
Object | Instantiation of a class as for example "Specialist" could be an instantiation of the class "Role". |
Object Attribute | Attribute of an object. |
Object Reference | Specific form of an Inter-model reference to an object in the same or in a different ADOxx model. |
objectiF | Object-oriented UML CASE tool (owner: microTOOL GmbH). |
Offline Animation | The offline animation enables you to exactly replay an earlier simulation run based on a simulation protocol. During this, the performers' task stacks are animated. Agents may also be employed during the offline animation. When generating the simulation protocol the format "short version" must be specified in order to create a file (*.apf) that can be used by the offline animation function. |
Output-induced (OI) Process | Process causing costs that vary depending on the amount of work that must be executed by the cost centre. A cost driver exists. |
Output-neutral (ON) Process | Process causing costs which are independent of the amount of work that must be executed by the cost centre.No cost driver exists. |
Oracle | DBMS for Unix, Windows and other operating systems (owner: Oracle Corp.). |
P ​
Description | |
---|---|
Page Area | Visualisation of the page layout in the model editor of the Modelling Toolkit. The page area is marked by a broken line. The page area is most important when graphic files are generated. |
Page Layout | Description of the size of a printed page. The section available for the graphic model information and the headers and footers per page layout can be defined in the library configuration of the Development Toolkit. The size of a printed page is especially taken into account when graphic files and connector marks are generated. |
Path | Sequence of objects ( activities, decisions etc), which describe one possible way in which a process can be executed. |
Path Analysis | Simulation algorithm in the Simulation Component of the Modelling Toolkit, which "plays" through Dynamic models. Serves to calculate process-specific key figures such as "Expected Cycle time" and "Expected Costs" and to determine which paths are critical with regard to various criteria selected by the ADOxx user. |
ZSoft Paintbrush Graphic (PCX) | ZSoft Paintbrush graphic file format. One of the formats available for generating graphics, for example from models. |
Portable Document Format (PDF) | File format, using which documents can be shown independently of the hardware, the operating system and the application software used for the creation (owner: Adobe Systems Incorporated). The complete ADOxx user documentation is contained in PDF on the ADOxx installation CD. |
Performer | Actor within a business process. Performers are represented in ADOxx as objects of the class "Performer" in Static models. It is possible to specify the performer (or set of performers) who can execute a certain activity using the "Performer" attribute in an activity's notebook. |
Performer Calendar | Description when a performer is present and available for executing activities. A performer's availability can be described in detail down to seconds and refers to one year. Performer calendars are evaluated in the simulation algorithm " Workload Analysis". |
Performer Assignment | In ADOxx, business processes and Statics are modelled separately. To assign activities to performers, AQL expressions are entered in the attribute "Performer" in objects of the class "Activity". These are interpreted during simulation to assign an actual performer to an activity. |
Plans, predefined | predefined plans are a specific type of result representation for predefined queries. If a query's result are all objects of a class within a model - such as all activities of a business process model - the lines of the result table will only show the model name. The columns of the result table will be empty. Predefined plans may e.g. be used for generating task plans. They are defined in the Development Toolkit for Static libraries and business process libraries) and are then available to the ADOxx user, together with the predefined queries in the Analysis Component of the Modelling Toolkit. |
Portable Network Graphics (PNG) | Graphic file format, in which graphics generated from models can be stored. PNG files can be inserted to graphic programs and then further edited or be connected to any application (e.g. spreadsheet programs). |
predefined Evaluation Queries | Queries, predefined. |
predefined Plans | Plans, predefined. |
predefined Queries | Queries, predefined. |
Prioritisation | Process, using which the ADOxx user can select the next activity to be edited during the simulation. |
Process Calendar | Describes the stochastic occurrence of business processes in time intervals. An example of stochastic occurrence is seasonal fluctuation. Process calendars are evaluated by the simulation algorithm " Workload Analysis". |
Process Hierarchy | Call hierarchy of Dynamic models. A hierarchy may be structured according to business processes calling or to business processes called. Within a process hierarchy, models can be searched ( model search). The process hierarchy can be displayed graphically or in tabular form. |
Process Instance | Specific instance of a business process during the simulation. |
Program call (PROGRAMCALL) | attribute type for launching an external program (such as Microsoft Excel). |
Q ​
Description | |
---|---|
Quality Assurance | The basic objective of quality assurance measures (or QA systems) is to guarantee a constant quality level with regard to a company's products and/or services. There is a fundamental difference between two different approaches of quality assurance: active vs. reactive methods. The latter attempts to assure the product quality by introducing control mechanisms. These, however, just fight the consequences of faulty processes, i.e. the poor/defective products. Newer approaches have tried to develop optimised procedures to actively affect the products' quality. These active quality assurance approaches are known as Quality Management and find their expression in a great number of methods, concepts and canons of rules. These include Total Quality Management (TQM) in particular or the series of norms ISO 9000 ff. |
Quality Management | Quality Management is an umbrella term for a number of active quality assurance methods. Active QM approaches - in contrast to approaches of reactive Quality Assurance - are those the purpose of which is to avoid "quality gaps" in the products and/or services of a company. An essential part of the quality management is thus the documentation and (re-)structuring of business processes). |
Quantity | Attribute of objects of the class "Process start". Specifies how often the business process occurs. The quantity refers to the value of the attribute "Time Period". Both attributes are used in the Capacity Analysis simulation algorithm. |
Queries | Functionality of the Analysis Component in the Modelling Toolkit. By running queries on models, the model contents can be extracted and be displayed in a clearly structured way in the ADOxx browser. The following types of queries are available: user-defined, standardised and (depending on the particular library configuration) predefined ones. |
Queries, predefined | The ADOxx administrator defines predefined queries for business process libraries and Static libraries in the Library Management component of the Development Toolkit. The predefined queries are made available to the ADOxx user in the Analysis Component of the Modelling Toolkit by specific menu options. The results of the predefined queries are displayed in the ADOxx browser. |
Queries, standardised | Standardised queries are available to the ADOxx user in the Analysis Component in the Modelling Toolkit. Standardised queries may be used to create user-defined queries. The results of the standardised queries are displayed in the ADOxx browser. |
Queries, user-defined | The ADOxx user defines user-defined queries in the Analysis Component of the Modelling Toolkit by using AQL expressions. The results of the user-defined queries are displayed in the ADOxx browser. |
R ​
Description | |
---|---|
R/3 | Standard software suite (manufacturer: SAP). |
Random Generator, automatic | The assignment of variables during the simulation run is automatically using the defined distributions. |
Random Generator, manual | The ADOxx user can select the variable assignment during the simulation run. |
Rational Rose | Object-oriented CASE tool (owner: IBM). |
RDBMS | Relational database management system. DBMS, which is based on the relational data model. |
Read Access | Access right to an ADOxx model group and the ADOxx models referenced within this group. With this type of access right, you may view models locally but do not have access to make any changes. |
Record | RECORD; attribute type which enables a flexible list/record administration of assembled file types ( attributes). |
Reference Model | Consists of standardised reference processes (templates) that represent operational activities generally valid or necessary. Reference models focus on branch or software-specific aspects and can be adapted (customised) to company-specific circumstances. |
Reference Process Model | Process from a reference model. |
Relation | General connection between two classes. Objects of a class can be linked by concrete instantiations) of this connection), for example, two organisational units may be linked by the relation "Is subordinated". |
Relation Attribute | Attribute of a relation. |
Relation Panel | Button panel that contains exactly one button for each relation that can be modelled in the active context. It is the lowest part of the modelling bar, following the edit button and the class panel. |
Relation Table | Functionality available in the Analysis Component of the Modelling Toolkit. A relation table represents connections (of a relation) inside a model. The objects (start and target objects), which are linked by the connectors, are displayed in the row or column headers of the table. Which relation tables are available depends on the respective library configuration. |
Repository | Central database for the administration of all ADOxx users, ADOxx application libraries, ADOxx models etc. |
Representation, graphical | Possibility of visualising an ADOxx model in graphical form. |
Representation, tabular | Possibility of visualising an ADOxx model in tabular form. |
Resource | Part of a Static which is needed for executing activities, such as PC, printer or fax. |
Resource Assignment | In ADOxx business processes and Statics are modelled separately from each other. For the Simulation to take account of resources, AQL expression(s) must be entered in the "Selection" attribute of objects of the class "Resource" in business processes (support available for this). These are interpreted during the Capacity and Workload Analysis s. In this way, the resources in the Static which are needed to execute an activity are determined. |
Resting Time | Time during which an activity of a business process has been executed but has not yet moved on to be transported to the next stage in the process. |
Result Function | Function which is assigned to an agent. By this, the agent is instructed to calculate a certain simulation result. |
Rich Text Format (RTF) | File format, in which the contents of the ADOxx browser or model contents which were generated using the Documentation Component can be saved. RTF files can be further edited in word-processing programs. |
S ​
Description | |
---|---|
SAP | Systems,Applications,Products in data processing. Owner of the standard software R/3. |
Scalable Vector Graphics (SVG) | SVG files are used when generating graphics from models or model parts and when copying the graphical result representation of the ADOxx browser. In addition SVG files can be created during documentation generation. In general, SVG files are used in HTML browsers. |
Server | A server is a software module which puts its services at the disposal of other software modules, the clients. |
Standard Generalized Markup Language (SGML) | SGML files are used in the Documentation Component to transfer the documented model contents. In a second phase, the SGML files will be then converted to any target format (e.g. HTML, RTF, XML) using a DSL file. |
Side Reference | Classification of references to determine the referenced models (for example when opening models including referenced models) starting from a model. Outgoing references from side-referenced models will only be followed, if these references start from the same attribute and if no depth restrictions prevent it. |
Sim Mapping | Attribute of a business process library. In the sim mapping the input parameter combinations are defined. In addition, the sim mapping defines which classes should be to totalled for aggregated results, for the assignment of performers and for the reference objects of the agents. |
Simulation (component) | Component in the Modelling Toolkit, which simulates business processes and Statics. ADOxx contains the simulation algorithms " Path Analysis", " Capacity Analysis", " Workload aAnalysis (steady state)" and " Workload Analysis (fixed time period)". |
Simulation Cache | The simulation cache stores the simulated ADOxx models in the internal representation necessary for simulation. Thus, the models need not be transferred into the internal representation again, if you start the simulation anew. |
Simulation Log | Report (protocol) of a simulation run in the Simulation Component. |
Simulation Log, short version | Compressed form of the simulation log; used by the offline animation function. |
Simulation Log, long version | Detailed form of the simulation log for replaying each step of the simulation. |
Simulation Run | Processing of a process instance during the Simulation. |
Single Sign-on (SSO) | Functionality in ADOxx which enables that the Windows system user can be imported into the ADOxx user management and therefore allow system users working and logged in to the domain to log into ADOxx without providing user name and password again. |
Smart-Icon | Graphical buttons in the component bar, the quick access bar etc. |
Snap Grid | Grid according to which objects and bend-points can be aligned on the drawing area. |
SQL | Structured Query Language. Query language for relational databases. |
SQL Server | Microsoft SQL Server. |
SQL Server Express Edition | Microsoft SQL Server Express Edition. |
Staffware | Workflow Management System (owner: TIBCO, Inc.). |
Stand-alone | A single computer system. |
Standard Model Group | ADOxx model group, which is created automatically with the ADOxx database. The standard model group has the name "Models". |
Standard User | ADOxx user who is created automatically together with the ADOxx database. The standard user has the user name "Admin" (default password is "password") and cannot be deleted. |
Standard User Group | ADOxx user group, which is created automatically with an ADOxx database. The standard user group has the name "ADOxx" and cannot be deleted. |
Standardised Queries | Queries, standardised. |
Swimlane | A swimlane is a modelling construct to describe roles, organisational units etc. A swimlane is visualised by vertical and horizontal areas on the drawing area. The characteristic of a swim lane is that when changing its size you will also move the objects and relations placed on this swimlane. |
System Administrator | Person responsible for the IT infrastructure (hardware, network, software installations and so on). |
System User | User of the operating system (Windows) who is authenticated by logging into a domain. In general the system has to be created by a system administrator within the system user administration in order to be able to work with and log in to the system. System users can log in to ADOxx via single sign-on (SSO), if this feature is provided. |
System User Administration | Part of an operating system used to create, delete or change the settings of system users, create, rename and delete system user groups, as well as assign system users to system user groups. |
System User Group | A group containing system users. A system user group has specific access and execution rights to components of the operating system which are defined by the system administrator. |
T ​
Description | |
---|---|
Tabular Representation of a Model | Representation, tabular. |
Task Stack | Stack of activities a performer has to execute. The size of the task stack is determined in the simulation algorithm "Workload Analysis". |
Task stack, central | The activities in the central task stack will be executed by the first performer who has time for it ( prioritisation). |
Task Stack, personal | The activities in the personal task stack of a performer are exclusively executed by this performer. |
Text | STRING; attribute type for text containing up to 3.700 arbitrary symbols (exception: attribute "Name" which is restricted to at most 240 symbols). |
Time | TIME; attribute type for the ADOxx time format YY:DDD:HH:MM:SS (Years:Days:Hours:Minutes:Seconds). |
Time, company | Division of time referring to the presence of a performer in the company. A (performer's) company time may for example consists of 170 days a year and 8 hours a day. |
Time, real | Conventional division of time, i.e. a year has 365 days and a day has 24 hours. |
Time Period | Attribute of objects of the class "Process start". The time period specifies for which period of time the value of the attribute " Quantity" is valid. (Used in capacity analysis). |
Tolerance Waiting Time | Maximum waiting time before a process instance is aborted unedited during the simulation. |
Toolbar | Panel, by default below the menu bar in the ADOxx window. The buttons (smart-icons) visible depend on the component selected. They provide quick access to certain functions of the component. |
Transformation | FDL-Generation. |
Transport Time | Time needed for transporting files, documents etc. |
TXT | ASCII-TEXT; file format in which ordinary text files are saved. |
U ​
Description | |
---|---|
User Definition Language (UDL) | File format in which ADOxx users and ADOxx user groups are saved (exported) from the Development Toolkit. UDL files can then be imported into the Development Toolkit on a different computer. |
UDL Export | Functionality of the User Management in the Development Toolkit. With UDL export, ADOxx users and ADOxx user groups can be exported into UDL files. |
UDL Import | Functionality of the User Management in the Development Toolkit. With UDL import UDL files ( ADOxx users and ADOxx user groups) can be imported into ADOxx and then stored in the ADOxx database. |
UML | Unified Modeling Language; method of object-oriented modelling of complex software systems. |
Use Case Diagram | 1 UML diagram type. Interactions between a system and external people involved are described in Use Case Diagrams. 2 Model type of the ADOxx 1.5 Dynamic Experimentation Library. |
User | ADOxx user. |
User Account | User name and password for logging into the DBMS or the operating system. |
User Assignment | Assignment of an ADOxx user to one or more ADOxx user group(s) in the User Management of the Development Toolkit. This assignment makes it possible for the user to access ADOxx model groups and ADOxx models within the Modelling Toolkit. |
User Export | Export of ADOxx users and/or ADOxx user groups into a UDL file in order to transfer the data into a different ADOxx database or make a backup. Functionality of the User Management in the Development Toolkit. |
User Group | ADOxx user group. |
User Group List | List of all ADOxx user groups stored in the ADOxx database as well as all ADOxx users referenced in them. With the help of the user list, ADOxx user groups can be added, renamed and deleted. user assignment can also be edited. |
User Import | Import of ADOxx users and/or ADOxx user groups from a UDL file into the ADOxx database. Functionality of the User Management in the Development Toolkit. |
User List | List of all ADOxx users stored in the ADOxx database. With the help of the user list, you can add and delete ADOxx users as well as edit their settings. |
User Management (component) | An ADOxx component of the Development Toolkit where ADOxx users can be created, deleted and their settings can be changed ADOxx user groups can be created, renamed and deleted. An ADOxx user can be assigned to ADOxx user groups and ADOxx users can be imported and exported. |
User-defined Queries | Queries, user-defined. |
W ​
Description | |
---|---|
Waiting Time | Time during which an activity of a business process cannot yet be executed, as the person due to execute it is still busy working on something else; i.e. the activity is ready to be executed but must first queue for a while. |
WebSphere MQ | Workflow Management System, successor of FlowMark and MQ Series Workflow (owner: IBM). |
Width Search | Process to go through objects, i.e. to automatically process the objects and relations of a model in the RTF generation in the Documentation Component. Starting from a "Process start" object, all objects which are directly connected to this start object, will be processed gradually. When all objects which are directly connected to this start object have been processed, one of these directly connected objects will be selected as a new start object and the process will recur. This will be carried out for all objects. (see also depth search) |
Window Panel | Title bar of an ADOxx component's window ( ADOxx window). |
Windows System User | System user. |
Workflow Management System (WMS) | Computer system that controls the execution of business processes. The most prominent task of a Workflow management system is to delegate business process activities to the organisation's employees. |
Static | (= organisational structures); structures (e.g. departments and roles), performers and resources of an organisation. The working environment of an organisation is represented in ADOxx in Static models. |
Static Library | Contains classes and relations for modelling the Static as well as description, layout, analysis and simulation definitions. The classes of a Static Library are derived from the classes of the Static meta model. A Static model always refers to exactly one Static Library. Static libraries are defined during ADOxx customising. |
Static Meta Model | predefined classes for modelling Statics in ADOxx. The classes in a Static Library are derived from the classes contained in the Static meta model. |
Static Model | 1 Model of a Static. Results from instantiating classes of a Static Library. 2 Model type of the ADOxx 1.5 Static Experimentation Library. |
Workspace (Working Area) | Main part of the ADOxx window, usually situated below the toolbar. The modelling windows are displayed in the workspace. |
Workload Analysis | Simulation algorithm in the Simulation Component of the Modelling Toolkit, based on queuing theory. The simulation runs "on the time axis". The results are the number of cycle times and waiting times depending on the capacity/amount of work of performers and resources. The input for the Workload Analysis is an application model. A Workload Analysis can be run based on a steady state or a fixed time period basis. The results of the Workload Analysis are displayed in the ADOxx browser. |
Workload Analysis, fixed-time period | Workload Analysis, in which the length of the initialisation phase and the calculation (result measuring) phase and the types of results calculated (input parameters) are defined by the user. |
Workload Analysis, steady-state view | Workload Analysis, in which the length of the oscillation phases and the calculation period depend on the number of simulation runs. |
Write Access | Access right granted to an ADOxx user group to an ADOxx model group and the ADOxx models referenced within it. With this access right, you can locally change as well as save a model's content. |
X ​
Description | |
---|---|
eXtensible Markup Language (XML) | File format in which ADOxx models can be stored (exported). The models which have been exported to XML files, can for instance be imported to other computers, where they can be edited. In ADOxx, XML files will be created with encoding "UTF-8". |
XML Export | Functionality in the Import/Export Component of the Modelling Toolkit. Using the XML export, ADOxx models can be exported to XML files. |
XML Import | Functionality in the Import/Export Component of the Modelling Toolkit. Using the XML import, XML files ( ADOxx models) can be imported to ADOxx and stored in the ADOxx database. |