Motivation.

The mentioned activities in the previous section can be analyzed like an user-computer interaction process that is possible to emulate, and to Automate and even Activate, with the purpose to make easier the user daily activities.

A practical example can be the daily job of a user, who from the terminal of his computer, consults a data base of a determined manufacturer and captures a series of data, using then laterwho in a spreadsheet of another manufacturer, and whose results are the source of data of a particular application that offers new results.

This information, along with other data from other network computers under different operating systems, and other data from Internet or Intranet, are sources of data for another different data base of the another manufacturer, etc.

All this sequence could be automated according to the criteria of the user by means of a memorization and a very intuitive visual programming in a graphical user interface, so that a certain compatibility of the information was obtained from diverse surroundings, increasing the level of system integration.

This is the motivation to generate the concept of the AutoActivator.


Concepts explanation.

Ability to memorize any sequence of input-output actions between a user and his computer terminal, in a bidirectional way:

If through an input device (keyboard, mouse...) the user makes a interaction sequence with diverse applications, that can be implemented by different manufacturers, with different programming languages and surroundings, the Autoactivator must be able to save this sequence.

As well, if the computer makes a interaction sequence with the user, through information of results in an output device (screen...) of one or several applications, that one can be implemented by different manufacturers or programmers, the Autoactivator must be able to save this sequence (capture of images...).

Ability, through the information recognition and interpretation, to allow the suitable surroundings of modular and structured programming (top-down, OO, oriented to events, visual...) with the purpose to emulate, to automate and to activate all the user-computer interaction process, as much in local way as in remote way, generating the sequences of bidirectional actions that are opportune:

Through the saved information of the sequences, by means of a suitable recognition of the information available and an interpretation of the results, programming surroundings are generated to emulate all the user-computer interaction process, as much in local way as in remote way (Internet, Intranet...), generating the adapted sequences bidirectional actions.

Recognition of characters and images object.

The use of selection techniques and image capture within a graphical user interface is one of the fundamental bases for the autoactivator operation, as well as the necessity of characters recognition when it is feasible, or the establishment of objects recognition by means of degrees of comparison with a reference pattern established by the user.

In this sense, once a serie of characters or an image object are recognized, it is needed to establish an allocation of information to a variable that represents the recognition, so that it is a utility to the process to make by the autoactivator.

As well, high level programming surroundings with the suitably variables are necessary for the recognition information within the process to make by the autoactivator.

User sequence memorization and programming.

Another one of the activities that must support the autoactivator is the one of being able to save the complete sequence that the user makes within the graphical user interface GUI, as a visual script that can properly be modified, with object to reproduce that visual script programmed when it is necessary, with the same effectiveness like when the user made the manual sequence in its origin.

Since in the manual sequence that the user makes within the graphical interface is conditioned one by certain decisions of the user based on the information that he observes, it is necessary to establish a high level programming language that allows to emulate the decisions of the user based on certain criteria to establish, using the variables with the recognized information of the output screen..., and inserting suitably the interactions of the input mouse, keyboard...

Thus, a very intuitive surroundings of visual programming, through simple methodologies of structured programming, would be a solution very adapted to adopt a high level programming language with the purpose previously mentioned (an example could be the surroundings of visual programming by " union wiring " between the icons of the diverse structures of programming, or other languages of visual surroundings like Basic, C, Java..., available in relation with the preferences of the user, since the pretension of the autoactivator of operating systems is to adapt to the user necessities in a fundamental concept of quality).

Programming languages of high level.

The previous section is in relation with the necessity to have high level programming languages within the concept of the autoactivator of operating systems; it is advisable to emphasize that it is convenient to have varied surroundings of programming languages to use because the autoactivator of operating systems is focused to the necessities of the user.

It is possible that it is necessary to make activities of development, maintenance, audit, administration, etc., which they need tools and utilities with different level at which the habitual users need from the autoactivator of operating systems, but it is important to emphasize that the autoactivator is focused to the quality surroundings of the user, trying to facilitate the user daily work, minimizing the necessary effort for the suitable application of the autoactivator.

For that reason, a high level language with fort visual surroundings, easy to assimilate, and rich surroundings in high level languages available, are of effective aid to the usuary client, because the autoactivator tries to adapt to the knowledge and the necessities of the usuary client and to their work way, increasing the quality levels.

It is possible that, in this sense, can be developed modules advanced in expert systems and intelligence artificial surroundings with the purpose of satisfying the necessities more developed of the work and the human behavior.

Interactive processing and batch processing.

Until the appearance of this concept of autoactivator of operating systems the habitual sequences of work between the computer terminal and the user have been in interactive form in general.

The idea of the autoactivator is to replace to the user emulating his sequence of work, and in this sense, the interactive processing between the computer terminal and the autoactivator remains.

Because within a programmed rank the autoactivator emulates the sequence of habitual user work, the batch processing in queue of the autoactivator work is also possible, in relation with the automated necessities, increasing the yield of the work made by the user (for example, the accomplishment of a certain sequence of work at night, in a holiday, in vacations..., emulating the performance sequence of the user).

Applications compatibility and orientation to the user.

The development of diverse applications by different manufacturers not always has been characterized by a good product compatibility, generating with it considerable efforts of work for the user client, as much in his looks for of manual solutions like in the habitual necessity to learn new knowledge of applications to solve incompatibilities.

This plurality of applications and technologies is an habitual guideline in the technological development, but the adaptation of the user client to this progression and diversity also generates a no focusing of the user in the accomplishment, development, and improves of his concrete work in individual, because he must dedicate too much resources of time, effort..., to assimilate knowledge of new products not totally compatible with which habitually he uses.

The autoactivator of operating systems tries to cushion this process of adaptation of the user client to new and old products, making surroundings of compatibility by means of the emulation systems of habitual sequence of user work, the information capture, the objects recognition, the adapted and simple visual programming, and the control of the input-output elements.

The last purpose of this surroundings of compatibility between diverse applications is to generate a autoactivator of operating systems strongly focused towards the user, with the maximum quality in the necessities satisfaction of the user client work.

Integration.

Continuing with the matter exposed in the previous section with respect to the compatibility of diverse applications and the user orientation, the autoactivator of operating systems has the pretension to generate integration surroundings of diverse applications, operating systems, networks, Intranet, Internet, extranet, etc., within a graphical user interface, with the objective to offer high quality surroundings to the user client.

In this sense, it can say that the autoactivator generates the suitable frame for a process of global integration of the user surroundings.

Structures of operating systems to develop.


The exposed assembly must allow the traditional systems of interprets of commands (shell) and commands archives (shell scripts).

In the determination of the structure of the operating systems we can consider the existence of layers like the kernel (that shows one narrow relation with the hardware), like the services to the system with interface of programming, API Application Programming Interface (process management, memory, input-output, files, communication, synchronization, security, protection), like the command interpreter and shell with textual or graphical interface, as well as client-server surroundings.

The mentioned surroundings must adapt to the necessities imposed by the autoactivator so that the user can have an increase of his quality of work in all the senses, remaining hidden all the complexity of adaptation exposed under the graphical interface.

This process of adaptation of the kernel activities, the services, the shell, the client-server surroundings..., to the necessities of the autoactivator will suppose the greater effort of the software evolution towards the objectives of high quality for the user client work, which really is the human concept.

The use of the autoactivator as system of high quality for the user supposes an adaptive approach of the planner of kernel (to scheduler) to select the process to execute and of the activator (dispatcher) to put in execution the process selected by the planner towards the necessities imposed by the user through the autoactivator.

The complex processes of planning and activation by means of interruptions, algorithms..., will have to adapt to the considerations of operation of the autoactivator by means of an advance and progress of software in operating systems.

Multiuser and multitask are concepts of operating systems that must reach an evolutionary progression within the possibilities that the new concept of the autoactivator of operating systems offers, because an automation of the interaction sequence of the users with its computer terminals supposes a complexity added to the tasks to support by the operating system under the autoactivator surroundings.

The activities administration of the operating systems like the processes, the memory, the archives and the directories, the inputs and the outputs, the interblockades, the priorities, the synchronization, the communications..., under the quality guidelines established by the autoactivator needs of the suitable adaptations to the new concept, that as it has commented in the previous sections, will be in relation with the software progress.

Questions like the security and the protection (accesses, authentication, registries, coding...) must be extrapolated to the concept of the autoactivator, as well as a system of documentation, maintenance and audit, monitor, modelling, errors processing, surroundings of development, operation, tests..., that they contribute to the consolidation of the quality of the user work.

The existence of a interactive help system to the user in the autoactivator surroundings is a fundamental item that it must be implemented, like the availability of utilities and tools of system, navigability and analysis, as much for the user, as for the developer and the administrator.

Also it is necessary an adaptation in distributed operating systems, clusters, and middleware for the autoactivator characteristics of operating systems.

Next operating systems.

In a near future is possible that the manufacturers software implement in their commercial operating systems the application of high level " AutoActivator " to provide to the user a greater support.

Conclusion.

By This way the " AUTOACTIVATOR " makes one double slope, by a side emulates the required part of which the user daily makes with his computer terminal, becoming " the Automatic Pilot of the Ship Computer ", and on the other hand, it supposes a " Nexus of union between different software and hardware manufacturers. Compatibility. Integration. ".