Paper 1.2 BMIS: Business Management and Information Systems
Paper 1.2 BMIS tests whether you can connect management decisions to the information systems that support them. Expect scenario questions on management functions and roles, information quality, system types, systems development, and controls rather than pure definitions. The examiner rewards a clear chain: decision - user level - information characteristic - system or control.
Management foundations
Management is usually examined through planning, organising, directing and controlling. Planning sets objectives and resources; organising designs structure, authority and span of control; directing covers leadership, motivation and communication; controlling compares performance with standards and corrects variance. Mintzberg's roles (interpersonal, informational, decisional) explain why managers need different information: figurehead and leader roles need internal people data; monitor and disseminator roles need broad internal and external intelligence; entrepreneur and resource allocator roles need decision support.
Information and systems
Data are raw facts; information is processed data with meaning, relevance and purpose. Good information is accurate, timely, complete, relevant, concise and cost-effective. Systems are classified by management level: a TPS records routine transactions; an MIS produces scheduled summary reports for middle managers; a DSS supports semi-structured what-if analysis; an EIS gives senior executives summarised internal and external KPIs with drill-down. The SDLC runs through investigation, feasibility, analysis, design, development, testing, implementation and review; feasibility has technical, economic, legal and operational dimensions. Controls include access control, backup and recovery, audit trails, segregation of duties and business continuity.
Worked example
A 40-branch pharmacy chain uses EPOS terminals to record each sale; head office receives a next-day sales summary by branch; the finance director wants a model to test a 10% price cut. Reasoning: EPOS captures routine transactions, so it is a TPS. The scheduled branch summary supports middle-management monitoring, so it is an MIS. The price-cut model tests alternative assumptions, so it is a DSS, not an EIS, because it is not merely a KPI dashboard. If the question asks for controls, add exception reports on unusual discounts and segregation between price maintenance and sales reporting.
Traps
Do not label every report an MIS; match the system to decision level and structure. Do not say information is “accurate” without linking it to the decision. Do not treat a DSS as replacing managerial judgement. Do not confuse IT (hardware and software) with IS (people, process, data and technology). In management questions, distinguish authority from responsibility, and line from staff roles.