DATA PROCESSING
(1) Refers to a class of programs that organize and manipulate data,
usually large amounts of numeric data. Accounting programs are the prototypical examples of data processing applications. In contrast, word processors, which manipulate text rather than numbers, are not usually referred to as data processing applications.
(2) Same as Information Technology (IT), refers to all computing functions within an enterprise.
DATA PROCESSING CYCLE
Regardless of the kind of data processed or the kind of device or equipment used, all data processing systems involve at least three basic steps : Input, Processing, and Output. These three steps constitute the data processing cycle.
1. INPUT=In this steps the initial data, or input data, are prepared in some convenient form of processing. The form will defend on the processing machine.
For example, when electromechanical devises are used.
2. PROCESSING= In this step the input data are changed, and usually combined with other information, to produce data is more useful form. Thus, paychecks may be calculated from the time cards, or a summary of sales for the month maybe calculated from the sales orders. The processing step usually involves a sequence of certain basic processing operations.
3. OUTPUT= Here the results of the preceding processing steps are collected. The particular form of the output data depends on the use of data.
***from blogs
If you mean program development cycle, it usually goes something the following. Some of these steps (like design and testing) may be combined, depending on the overall complexity of the project. Also, the cycle is not totally linear, as problems encountered in testing will usually require changes in coding and may even indicate a return to the detail design (or worse yet, general design) phase. The important thing is that, the more thorough a given phase is done before moving on to the next, the less likely a need to backtrack and less farther back you'll probably need to go.
1) User requirements - determine what the program is supposed to accomplish either by putting yourself in the role of the user or (preferably) sitting down with one or more typical users and asking them what they need
2) General design - create a high-order layout of the processes, inputs and outputs of the system as a whole. For databases, begin identify the tables, key structures and relationships. Ensure that all mandated user requirements are addressed.
3) Detail design - break the general design into smaller, more detailed pieces, identifying which individual modules and inputs/outputs perform a given process. Flesh out databases with individual elements.
4) Coding - develop code for the various modules.
5) Unit testing - test the individual modules to ensure each does what is expected and creates the required ouput(s).
6) System testing - test that the individual modules work together, passing data from one to the next in the expected manner
7) Acceptance testing - allow users to experiment with the application to see if it performs as they expected and satisfies their requirements
8) Implementation - publish the finished product for normal usage
9) Maintenance - begin the cycle over to correct problems, improve performance and/or incorporate new functionality
