System Development Life Cycle (SDLC):

• Definition/Explanation: A highly structured, standardised framework utilised in systems engineering to plan, create, test, and deploy an information system. It ensures that systems meet predefined business requirements through distinct, verifiable, and sequentially manageable phases.

Project Steering Committee:

• Definition/Explanation: A paramount governing body comprising executive stakeholders and senior management responsible for providing overall strategic direction, ensuring alignment with corporate strategy, resolving high-level disputes, and monitoring project progress and funding.

Agile Development:

• Definition/Explanation: A lightweight, highly iterative approach to software development emphasising maximum flexibility, continuous cross-functional collaboration, and the rapid, incremental delivery of functional components, allowing teams to adapt swiftly to changing requirements and volatile risk landscapes.

Waterfall Model:

• Definition/Explanation: A traditional, linear, and sequential SDLC methodology where each distinct phase (e.g., planning, design, implementation, testing) must be entirely completed and formally approved before the next begins, characterised by heavy documentation, predictable timelines, and rigid scope control.

Business Case:

• Definition/Explanation: A comprehensive, data-driven document justifying the initiation of a project. It evaluates the financial, technical, and operational viability of a proposed system, outlining expected business benefits, strategic alignment, and the projected return on investment (ROI).

Request for Proposal (RFP):

• Definition/Explanation: A formal, detailed procurement document distributed to potential vendors outlining exact system and product requirements, inviting them to submit competitive bids, and providing a standardised, objective basis for evaluating vendor capabilities and financial viability.

Global Software Development (GSD):

• Definition/Explanation: The practice of utilising distributed software engineering teams located across different geographic regions and time zones to increase productivity, facilitate continuous development, and optimise labour costs, though it introduces significant communication and requirement engineering complexities.

Application Controls:

• Definition/Explanation: Automated or manual security and operational mechanisms embedded directly within software applications designed to ensure the absolute completeness, accuracy, and validity of data during the input, processing, and output phases of a transaction.

User Acceptance Testing (UAT):

• Definition/Explanation: The crucial final phase of testing performed directly by the designated end-users to empirically verify that the fully developed system satisfies the original business requirements and functions accurately in real-world operational scenarios before production deployment is authorised.

ACID Principle:

• Definition/Explanation: A fundamental set of properties (Atomicity, Consistency, Isolation, Durability) that guarantee database transactions are processed reliably, securely, and completely in an Online Transaction Processing (OLTP) environment, preventing data corruption during system failures.

Integrated Testing Facility (ITF):

• Definition/Explanation: An advanced audit testing technique where a fictitious, partitioned entity (e.g., a dummy department or customer account) is created within a live production database, allowing auditors to process test transactions concurrently with actual live data to verify continuous processing accuracy.

Parallel Simulation:

• Definition/Explanation: A specialised audit technique where actual production data is processed through an independent, auditor-controlled simulation program that meticulously replicates the logic of the organisation's application to verify processing accuracy without impacting the live environment.

Abrupt (Big Bang) Changeover:

• Definition/Explanation: A high-risk system migration strategy where the legacy system is completely and permanently shut down, and the new system is immediately activated to replace it at a specific, predefined point in time.

Phased Changeover:

• Definition/Explanation: A risk-averse migration strategy where the new information system is introduced gradually and incrementally, replacing the old system module by module or geographic location by geographic location, thereby minimising the impact of potential enterprise-wide disruptions.

Post-Implementation Review (PIR):

• Definition/Explanation: A formal, objective assessment conducted by an independent party after a newly deployed system has stabilised in the production environment. It evaluates whether the system has achieved its stated business objectives, realised the expected financial benefits, and maintained effective internal controls.