Today's dominant usage model is interactive computing; historically, what was the earlier prevailing model in organizations?

Introduction / Context:
Modern systems emphasize interactive experiences and near real time responses. Historically, however, organizations relied on batch processing where jobs were collected and executed in scheduled runs, often overnight. This question tests knowledge of that historical baseline.

Given Data / Assumptions:

• Legacy mainframes and early business computing prioritized throughput over interactivity.
• User terminals and online transaction processing matured later.
• Many financial and payroll activities were batch oriented.

Concept / Approach:
Batch processing executes groups of jobs without user interaction during the run. It optimizes machine utilization and suits periodic tasks like payroll, billing, and end of day posting. Interactive systems trade some throughput for immediate user feedback and validation.

Step-by-Step Solution:
1) Contrast interactive models with non interactive job scheduling. 2) Identify the historical model used widely in enterprises. 3) Select 'Batch processing' as the earlier prevailing approach.

Verification / Alternative check:
Historical accounts of MIS evolution and mainframe operations describe batch windows, JCL job queues, and overnight cycles as standard practice.

Why Other Options Are Wrong:
Option B: Parallel processing is a hardware or execution paradigm, not the historical organizational model.
Option C: 'Random processing' is not a formal model.
Option D: Multitasking is a system capability, not the classic enterprise usage model.
Option E: Not applicable since batch processing is correct.

Common Pitfalls:
Confusing architectural capabilities with organizational usage patterns. Batch refers to how work is grouped and scheduled for business processes.

Final Answer:
Batch processing