ICSAN MIS key terms

A set of interrelated components that collect, process, store and distribute data, together with the people, procedures and technology that turn that data into information supporting decision-making and control in an organisation.

A hierarchy in which data are raw unprocessed facts, information is data organised and given meaning and context, and knowledge is information combined with experience and judgement that enables action.

An operational system that captures and records the routine daily transactions of an organisation, such as sales, payments and inventory movements, providing the detailed data on which higher-level systems depend.

A system that draws on transaction data to produce scheduled summary reports and exception reports used by middle managers to monitor performance against plans and support structured decisions.

An interactive system combining data, analytical models and a user-friendly interface to help managers explore alternatives and analyse semi-structured problems where judgement is still required.

A long-term plan describing how information systems, data and technology will be used to support an organisation's objectives, including demand-side needs and supply-side choices about infrastructure, sourcing and standards.

The fit and mutual adjustment between business strategy and IT strategy, so that technology investment directly supports corporate goals and business plans in turn exploit what technology makes possible.

The structures, processes and relational mechanisms by which an organisation directs and controls IT, ensuring that technology delivers value, risks are managed and resources are used responsibly against agreed objectives.

A widely used framework of governance and management objectives for enterprise IT, organised around domains such as plan, build, run and monitor, that links IT activity to stakeholder needs and value creation.

A policy, procedure, practice or technical mechanism put in place to reduce IT-related risk and provide reasonable assurance that objectives are met, classified as preventive, detective or corrective.

The amount and type of risk an organisation is willing to accept in pursuit of its objectives, set by senior management and the board and used to guide decisions about IT investments and controls.

The process of identifying threats and vulnerabilities, estimating likelihood and impact, and prioritising risks so that controls and treatments can be selected and resources allocated proportionately.

A control principle that separates incompatible tasks, such as authorising, recording and custody of assets, so that no single person can both commit and conceal an error or fraud.

A chronological record of system activity, transactions and changes that allows events to be reconstructed, supporting investigation, dispute resolution and demonstration of compliance with controls.

The process of developing arrangements, such as recovery plans, backups and alternate sites, to keep critical business functions running or restore them quickly after a disruption.

A structured sequence of phases for building information systems, typically feasibility, analysis, design, build, test, implement and maintain, providing checkpoints and control over project progress.

An iterative approach that delivers software in short increments with continuous customer feedback and adaptive planning, favouring working software and collaboration over exhaustive upfront documentation.

A documented statement of what a system must do, covering functional behaviour and quality attributes such as performance, security and usability, forming the basis for design, procurement and acceptance testing.

A model showing the trade-off between scope, time and cost, with quality at the centre, so that changing one constraint forces adjustment of the others and affects the project's risk profile.

Formal testing in which intended users verify that a system meets agreed business requirements and is fit for purpose, typically a precondition for sign-off and go-live.

An integrated suite of applications sharing a common database that supports core processes such as finance, procurement, manufacturing and human resources, replacing fragmented legacy systems.

A system and business approach for managing customer interactions, sales pipelines, service history and marketing activity so that relationships are consistent and profitable across channels.

The coordination of sourcing, production, inventory, logistics and demand information across suppliers, the organisation and customers to reduce cost and improve responsiveness.

The discipline of creating and maintaining a single trusted version of core reference data, such as customers, products and suppliers, shared across systems to avoid inconsistency and duplication.

A data store organised as tables of rows and columns linked by keys, queried with a standard language and designed to preserve integrity through normalisation and constraints.

A central store of subject-oriented, integrated, time-stamped data drawn from operational systems and structured for query and analysis rather than day-to-day transaction processing.

The collection of tools and practices for turning stored data into reports, dashboards and analysis that inform managerial decisions and performance monitoring.

The degree to which data are accurate, complete, consistent, timely and fit for their intended use, a precondition for reliable reporting, analytics and automated decisions.

The conduct of business processes and transactions over digital networks, spanning selling, procurement, collaboration and service, of which e-commerce is the buying and selling subset.

The use of digital channels and platforms to source, requisition, order and pay for goods and services, often through catalogues, auctions or supplier portals, reducing cycle time and cost.

Deep organisational change in strategy, processes, culture and customer experience enabled by digital technology, going beyond automating existing tasks to creating new ways of operating and competing.

Provision of computing resources such as storage, processing and applications as on-demand services over a network, typically charged by usage and offered in public, private or hybrid models.

The three core security goals of confidentiality, meaning only authorised parties access data; integrity, meaning data are accurate and unaltered; and availability, meaning systems are accessible when needed.

The mechanisms that determine and enforce who may use which resources and in what manner, including authentication of identity, authorisation of rights and logging of activity.

A social engineering attack in which deceptive messages impersonate a trusted party to trick recipients into revealing credentials, transferring funds or installing malicious software.

The protection of personal information through lawful, fair and transparent handling, including limits on collection, purpose specification, retention, security and the rights of data subjects.

A process-based approach to delivering and supporting IT services to agreed levels, covering service design, transition, operation and continual improvement, commonly structured around ITIL practices.

A documented agreement between a service provider and a customer that specifies the services to be delivered and measurable targets such as availability, response time and support hours.

The process of detecting, recording, prioritising and resolving unplanned interruptions or degradations of service quickly, restoring normal operation while preserving evidence for later root-cause analysis.

The structured process for planning, approving, testing and communicating alterations to systems, processes or structures so that disruption and unintended risk are minimised and adoption is supported.

The principles and standards expected of information systems professionals, including competence, integrity, confidentiality, avoidance of conflicts of interest and responsible use of entrusted data and systems.