top of page

TECHNOLOGY - for techies only!

 

Enterprise ontology architecture with dynamic, modular business artifacts in a semantic network as integrated access for analysis and development of systems in general and information systems in particular. ARONTO therefore delivers a universal framework for the entire lifecycle of a system from requirements definition, analysis, to development and delivery, through to creation of a new system generation.

The underlying premise is that objects and processes are two types of equally important elements, both of which together describe the structure and behavior of a system in a single, standard model.

 

ARONTO only uses the following elements for system modeling in this regard:

 

  • Objects (business artifacts)

  • Processes

  • Statuses (artifact status)

  • Relations (specialization, aggregation)

 

A business artifact

  • identifies concrete information objects that are required for the business model,
    for example data elements (order, product, invoice, SLA), documents, etc.

  • has a process for controlling its lifecycle from generation to conclusion and archiving.

 

  • Objects and processes are interlinked in a firmly coherent manner.

  • Objects cannot be transformed without processes and processes
    have no purpose and meaning without objects.

  • Objects and processes have commonalities in relation to aggregation and
    specialization, in other words features are handled according to the
    same methodology.

  • Processes are in turn artifacts.

 

This methodology is reflexive, in other words can be extended with inherent resources.
It is therefore also complete, in other words each system can be described fully in this way.

All required modules can be developed, managed, and combined as artifacts in the ARONTO design tool. This not only applies for the application elements but also for the elements of the system itself. This provides the option of uniting various system models, i.e. business artifacts, with their static and procedural features and relationships. This system model can be extended and modified at any time. ARONTO offers a basic common vocabulary upon delivery, which is based on the eTOM (enhanced Telecom Operations Map) recommendation of the TeleManagement Forum. Proposals are offered here for typical information elements in an enterprise (e.g. offer, order, customer, etc.) and their relationships with one another. Likewise, new artifacts can be defined freely. All artifacts are created as templates and converted via their process to entities, which serve as a basis for comprehensive business information.


All artifacts, processes, and their relations can be changed at runtime with immediate effect (without generating software code).
 

Information objects can represent complex structures. For example, a product can consist of several other sub(products), require services for generation purposes, and draw on resources (e.g. human resources as actors).

Any complex structures can be represented in the ARONTO information model. A model can be structured randomly with co-existence of hierarchical and network structures. Information object and process are represented and can be processed in an integrated way in the uniform UI.

For example: Freely configurable repositories for all of an enterprise's artifacts

Modeling processes in ARONTO:

Processes are artifacts in the sense of ARONTO and can be modeled and configured with the same simple graphical resources as all artifacts in the model. A process artifact consists of a sequence of states and activities, which cause the respective business artifact to change from one status to the next. Modeling is therefore possible at this level in relation to:

  • Start, end status of the element with respect to the process

  • Annulment, cancellation

  • Nesting (sub-processes)

  • Parallelisms, branches

  • Entities who execute the activities

 

The executing entities are defined, for example, on the basis of roles. Any number of roles can be created in ARONTO, grouped in profiles, and assigned to individuals. Designers can therefore model processes quickly and efficiently and assign them to associated business artifacts. Each individual action to be performed can be configured for the information object through the fixed coupling of the information object with its associated process based on the activity artifacts of the process.

  • Input screens for recording data contents with control of input (mandatory, optional, modify) and the screen content (who is allowed to or is to see what)

  • Generation of elements

  • Aggregation, linking of elements

  • With control in each case (mandatory, optional, number) and options (who is allowed to or is to execute what)

  • With selection of source and/or destination in each case

Distributing tasks

The ARONTO process manager identifies the tasks derived from the processes and organizes their distribution to the responsible users as well as their execution. The process manager assigns the tasks configured in the process to the user based on a task list.
 

The task list consists of three parts ...

Accepted tasks

  • Tasks are listed here that have either been taken on by the user or were assigned directly to the user

  • The user is responsible for processing this task


Pending tasks

  • Tasks are listed here that the user can take on

  • The user is a member of the work group and/or fills the role for which these tasks are pending for processing

 

Details

  • Details of the corresponding tasks.
     

  • The level of detail is defined by the modeler in the respective status components.

 

Controlling tasks, making processes transparent, supporting user actions

The Process Wizard guides the user through the process context. The individual actions configured in the activity artifacts are offered to the user with instructions and/or help information in a uniform environment.

The Process Wizard

  • controls the acceptance and completion or cancellation of activities

  • supports the switch to aggregated (sub)processes

  • controls branches in the process

  • supports the processing of individual actions

  • provides instructions or assistance for the activities

  • supplies the case history for comments and queries between the users

 

The user is informed of the latest status at all times:

  • Which process step am I in

  • What is the history like

  • Which (sub)activity can I take on

  • What are the time constraints

  • What is the current process status

PROOF OF CONCEPT -

No risk decision making

ARONTO offers a comprehensive proof of concept for tackling your problems. We collaborate with you to develop a solution for your chosen task. This proof of concept is already a functional business application that you can use without risk in a productive environment.

 

 

ARONTO-Academy -

Education and training programs

ARONTO offers trainings for "Application Designers" and for general users of your business solution via in-house training or WEB webcast. The scope of training ranges from general handling of ARONTO up to individual project seminars.

bottom of page