What is system design in MIS?

System design in MIS is the phase in which managers' information needs are turned into a specification of inputs, processing, data storage, outputs, and user screens. A management information system (MIS) is the software, data, people, and procedures that give managers regular reports for planning, control, and decisions. Design comes after system analysis, which decides what the system must do, and before implementation, which builds it.

The output of the design phase is a set of documents, not a working program. They describe every report a manager will receive and every screen a clerk will use. They also fix every table that will store the data, and every rule that turns raw transactions into summaries.

What MIS means and where design fits

An MIS starts from transaction data the organization already produces. Sales, payroll, purchases, and stock movements are the usual sources. It summarizes them for middle and senior management. A store manager sees daily sales by department. A regional manager sees the same figures across 40 stores with the underperforming ones marked. The same data serves different levels of management in different levels of detail.

The MIS life cycle has five phases: preliminary investigation, system analysis, system design, implementation, and maintenance. Analysis answers the question of what information each manager needs, and from which data. Design answers how the system will collect, process, store, and present that information. Implementation builds and installs it, and maintenance changes it as the business changes.

The five parts an MIS design specifies

A sixth element, controls, applies to all five. Controls are the checks that keep the data accurate and restricted: input validation, reconciliation totals, access rights, and audit logs.

Conceptual design and detailed design

MIS design is done in two passes, and textbooks name them conceptual design and detailed design.

Conceptual design, also called high-level or logical design, defines what the system will do without fixing how. It states the objectives and the major subsystems, with the data they exchange. It lists the information each manager receives and how often, and the constraints of budget and time. Data flow diagrams are the common tool. Conceptual design is often presented to management as two or three alternatives with costs, so they can choose one.

Detailed design, also called physical design, turns the chosen alternative into build-ready specifications. It fixes the database structure down to each field and the layout of every report and screen. It also states the processing logic for every rule, the controls, the hardware and software to run it on, and the test plan.

Example: MIS design for a retail chain

A retail chain with 40 stores wants better control of stock and sales. Analysis found two problems. Store managers reorder by guesswork, and head office learns about a shortage a week late.

The conceptual design defines three subsystems: inventory management, sales reporting, and customer relationship management (CRM). Sales data flows from every terminal and the online store into a central database each night. Inventory receives the sales, adjusts stock counts, and flags items below their reorder point. Sales reporting produces a daily store report and a weekly regional report. CRM stores purchase histories and sends offers based on them.

The detailed design then fixes the specifics. The sales table holds store code, product code, quantity, unit price, and timestamp. The reorder rule is: when stock on hand plus stock on order falls below 14 days of average sales, add the item to the purchasing screen. The daily report lists sales by department against the same day last week, sorted by the largest fall. Store managers may see only their own store; regional managers may see their region.

System design in MIS vs system design in software interviews

The phrase "system design" also names a software engineering interview round. The two uses differ. MIS design is about business information: which reports, which rules, which screens, for which managers. Interview system design is about the technical shape of one high-traffic service: load balancers, caches, database partitioning, and what happens when a machine fails.

They share the first step. Both begin by writing down the requirements and the volumes before drawing anything, and both produce a data model and a set of interfaces. An MIS designer who moves into software engineering already has that habit.