2. Batch Processing

It is often not desirable to deal with a set of data inputs until a certain number have occurred or a set time has passed.  So they are stored until the system comes online to process the data in one 'batch'.

For example

• A stock control programme may store records of every item sold in a shop that day. Then, at the end of each day it calculates what needs to be ordered. 
• An online competition stores all the entries until it is time to find the winner.
• Electricity, gas and telephone bills are usually calculated on a monthly basis.
• Producing monthly bank statements to send out to customers
• Payroll runs which may be weekly or monthly

After loading the data into the system, batch processing does not usually require any further interaction on the part of the user. Therefore the user interface is often code-based. The user enters the parameters of the batch run then leaves it to carry on.

Batch processing data sets

The advantage of batch processing is that it can be done during less-busy times on the computer or jobs can be queued up in order to fairly share a computing resource such as a super-computer.

For example, a scientist may have data-logged a huge amount of data on an experiment - perhaps he is working at the Large Hadron Collider in Switzerland and has Gigabytes of data to process. He submits the data to the super-computer as a batch run. Once complete an output data set is available for further analysis and visualisation.

Batch processing print outs

This is probably the most common form of batch processing. Namely, an input data set results in a set of printed documents.

For example, a payroll run results in a set of pay slips to be issued.

Disadvantage

The main disadvantage of batch processing is the time delay between collecting the input data and getting an output. It can also be frustrating to find out only later that a batch run has failed due to a data input problem.