Software package for the administration of ADONIS NP. The Administration Toolkit is reserved exclusively for administrators.
The data structure of the attribute. Depending on the attribute type, totally different content may be stored in the attribute: text of various length, integer and floating-point numbers, dates, times, internal and external references, tables, and much more.
An (abstract) template element defined in the ADONIS NP Application Library, from which (real) objects or relations are created as instances an placed in models. For instance, “Department 5” and “Accounting” are instances of the object class Organisational Unit and “Write Letter” as well as “Update Virus Protection” instances of the object class Task. The same applies to relation classes. The classes are defined by the customiser during the definition of the Application Library. Classes have attributes.
Part of the Administration Toolkit. Every component contains the modules needed for a certain type of tool usage. For instance, the Import/Export Component offers all functions for data exchange etc.
Connection between objects. Instance of a relation class. Shows the relation between (two, sometimes more) objects. Depending on the model type definition and the objects concerned, different types of connectors are allowed.
Person with full access to the ADONIS NP configuration. A customiser e.g. defines a new Application Library or the overall component access of an existing product.
Endpoints define to which object classes a relation class may attach to. Endpoints are subject to cardinality rules.
A group of objects, possibly connected by connectors and other relations. Models can picture flows (e.g. a process), structures (e.g. an organisational unit), an information pool (e.g. a document library) and much more. Every Application Library contains different model types, defined by a customiser. Every model is an instance of one of these model types.
Part of the ADONIS NP Application Library. Every model is an instance of a certain model type. A model type contains an aggregation of objects and connectors, serving for illustrating certain company aspects.
Instance of an (object) class. A distinction is drawn between repository objects (re-usable objects, stored in a repository) and modelling objects (maintained only in the models in which they are created).
Object classes define the modelling object types (e.g. Organisational Units, Tasks, etc.). See Class.
Every ADONIS NP administrator and every user account has access rights within the application. These cover various aspects (access to the Administration Toolkit and components, other user accounts, models and objects, the possibility to change internal structures and more).
A special kind of information storage in databases. In ADONIS NP this means for instance that models may exist in any number of versions and languages, that objects can be re-used in multiple models, that objects can contain both local (model-specific) and global (general) information and more.
A person that works with ADONIS NP. For this, they have to log in with a user account.
Each user is assigned one (or more) user account(s) by an administrator to log in to ADONIS NP. Thus, a user account is the virtual counterpart of the user in the ADONIS NP database and has features like user name, password, and rights.
Software package for the usage of ADONIS NP. The web client is available for most users.