Management Information Systems - An Overview: formula sheet

Key formulas

Core idea of MIS

Data → Processing → Information → Decision → Action → Feedback

Use this flow to explain how MIS supports decisions. Data becomes information only after processing.

Components of MIS

MIS = People + Data + Hardware + Software + Procedures

A common way to list components. Name all five in a definition answer.

Qualities of good information

Accurate, Timely, Relevant, Complete, Concise, Understandable

Use as a checklist when asked what makes MIS output useful. Wording of the list varies across books; the idea stays the same.

Hierarchy

Data → Information → Knowledge

Each stage adds context and value. Some texts add wisdom on top; mention it only as an extension.

Processing cycle

Input (data) → Processing → Output (information) → Feedback

Processing includes capture, validation, sorting, calculation, summarising and storage.

Core definition of information

Information = processed data that is meaningful and useful for decision making

Both conditions matter: processed and useful.

Qualities of good information

Accurate, Timely, Relevant, Complete, Concise, Consistent, Reliable, Accessible, Understandable, Cost-effective

Lists vary across textbooks. Learn the core ones and explain each in one line.

Level-to-system map

Operational → TPS | Tactical → MIS, DSS | Strategic → EIS (also DSS)

This is the usual textbook mapping. Systems overlap in practice, so use it as a guide, not a strict rule.

Decision type to system

Structured → TPS, MIS | Semi-structured → DSS | Unstructured → EIS

Use this to justify your choice of system in case questions.

Data flow

TPS (raw data) → MIS (summary reports) → DSS (analysis) → EIS (executive view)

TPS is the base data source for the higher systems.

Expert system components

Knowledge base + Inference engine + User interface

Some books add an explanation facility and a knowledge acquisition module.

Five components of MIS

MIS = Hardware + Software + Data + People + Procedures

Some textbooks add a sixth item such as network or communication. State the five and mention a network as supporting infrastructure if you wish.

Basic MIS process

Input (data) → Processing → Output (information) → Feedback and control

Use this to explain the conceptual structure in any answer.

Two views of structure

Structure of MIS = Physical structure + Conceptual structure

Physical is about actual parts and arrangement. Conceptual is about logical design and information flow.

Management levels served

Operational (detailed) → Middle (summarised, control) → Top (strategic, broad)

Detail falls and breadth rises as you move up the levels.

SDLC sequence

Planning → Analysis → Design → Development → Testing → Implementation → Maintenance

Textbooks may merge or rename phases. State the sequence you follow and explain each phase.

Feasibility study dimensions

Technical + Economic + Operational + Legal + Schedule

Done in the planning phase to decide whether to proceed. Some texts list only the first three.

Changeover methods

Direct | Parallel | Phased | Pilot

Parallel is the safest but costliest. Direct is the fastest but riskiest.

Quick revision

• An MIS turns data into information that helps managers plan, control and decide.
• Data is raw facts, information is processed data with meaning, and knowledge is information combined with experience and judgement.
• Information is useful only if it is relevant, accurate, timely and complete enough for the decision.
• Different information systems serve different levels of management, from daily operations to strategy.
• Transaction-level systems record routine events, while higher-level systems summarise and support decisions.
• An MIS has inputs, processing, outputs, storage and feedback, supported by hardware, software, data, people and procedures.
• Feedback lets the system check results and correct itself.
• MIS development follows planned stages: need, design, build, test, implement and review.
• Implementation risks include user resistance, poor data quality and weak training.
• In an exam answer, always link the system to a business function and a decision.
• Use short Indian examples, such as a retailer tracking stock or a bank assessing a loan.
• Define the term first, then explain, then conclude.

Common mistakes

• Treating MIS as just a computer or software package Fix: State that MIS includes people, data, procedures and managers' needs along with hardware and software.
• Confusing data with information Fix: Say data is raw fact and information is processed data useful for a decision. Show this in your answer.
• Treating data and information as the same thing. Fix: Always say data is raw and unprocessed, and information is processed and meaningful for a decision.
• Giving examples that do not show the change from raw to processed. Fix: Use one example in three forms: raw figures, summary report, and the decision taken.
• Saying MIS and DSS are the same thing. Fix: MIS gives routine, fixed-format reports for structured decisions. DSS is interactive and supports what-if analysis for semi-structured decisions.
• Placing TPS at the top level because it holds all the data. Fix: TPS serves the operational level. It is the base that feeds the others.
• Listing components but giving no explanation or example. Fix: Add a short meaning and an example for each, such as an ERP system as software or a data backup rule as a procedure.
• Confusing physical and conceptual structure. Fix: Remember: physical means things you can touch or staff (devices, programs, people). Conceptual means logic and flow (input, process, output, levels).
• Listing phases in the wrong order, for example testing before design. Fix: Remember the logic: decide, understand needs, plan the solution, build, check, go live, maintain.
• Writing only phase names with no explanation. Fix: Add purpose and output for every phase, and link it to the facts in the question.

Exam tips

• Start every answer with a clear definition. Examiners look for it first.
• Use numbered points with one explaining line each. This is easier to mark than long paragraphs.
• Always tie a point to a managerial decision or a business example. This lifts a descriptive answer above a memorised list.
• Do not copy a fixed list of characteristics blindly. Pick the ones that fit the question and explain them in your own words.
• If a case or scenario is given, name the information needed, the manager who needs it and the decision it supports.
• Always give a business example from a company setting. A bare definition earns fewer marks.
• For 'distinguish' questions, present points in two columns and cover at least four points.
• Do not stop at the qualities list. Add one line of explanation for each quality.