IPO Model

This product was added to computer science because of the content, defects on the quality assurance side of the editor. This is done to bring the quality of the articles from the computer science subject area to an acceptable level. Help us to eliminate the substantive shortcomings of this article and take part you in the discussion! ( )

The EVA principle (English input -process- output ( IPO) model) describes a basic principle of data processing. The acronym is derived from the first letter of the terms input, processing and output. These three terms describe the order is processed in the data. The principle can be seen from the perspective of the processing unit (which may be a human ), and is thus independent of the electronic equipment. It is therefore generally valid for the operation of data processing.

The EVA principle in the IT area can be described as follows: ( input - processing by data processing system ( DVA) - output ). It is considered a basic diagram of the data processing. Contrary to the general opinion of the memory is not part of the processing, but he has in IPO principle a kind of special position, it encapsulates off. Which is expressed as EVA ( S) principle. An apparatus according to pure EVA principle is stateless, it has no internal state which might lead to the same input in two processes could lead to different results. Therefore must the memory contents at processing start in a unchanging state ( for example, be " empty").

Only the departure from pure EVA principle to condition- prone logic circuits ( see Medvedev automaton, and Moore machine and Mealy machine ) resulted from simple calculators to the development of today's computers.

Perspectives

The EVA principle can be seen both " spatial" (in the broadest sense) and temporally:

• Spatially: An area of the DV system is designed for data input (eg one side of a board, keyboard, mouse, USB controller, but also "logical space ": a program library of a program), another area for processing, and the third part of the output. This can relate both to the organization as a whole as well as the hardware to the software or on the computer system (hardware and software): In the hardware must be clear which input signals will be received ( keyboard or mouse input, network connections, ...), how they should be processed ( perform eg a calculation ) and the form in which the data is to be output ( screen output, printer -, network, audio outputs, ...). Converse development such as smartphones, where input (touch screen) and output (same screen) do not have explicit, clear separation.
• The software must be clear which input data a program receives ( keystrokes and / or files from a disk, ...), what should it do with it (mathematical calculations, calculation of graphic elements ...) and what is to be issued in the form ( screen output in text or graphics, saving to disk, ...). Contrary principle here is, for example, object orientation, in the not functionally separate but related object: Both methods for reading, as well as for processing and outputting an object are object methods, so do not " spatially separated "; second example: the fuzzy logic attempts to make clear decisions yet unclear input signals; Neural networks try to generate defined from inaccurate input data outputs, often no exact processing rule can be laid down - the network is to it "somehow" carry out and learn through training.