A systems development methodology refers to a structured approach used in software development and systems engineering to guide the design, development, and implementation of software applications.
Why Option A (Waterfall) is Correct:
Waterfall methodology is a linear and sequential systems development methodology where each phase (e.g., requirements, design, implementation, testing, deployment) must be completed before moving to the next.
It is widely established and historically one of the first software development methodologies.
Used in large-scale enterprise projects where detailed planning and structured execution are required.
Why Other Options Are Incorrect:
Option B (PRINCE2 - Projects in Controlled Environments):
Incorrect because PRINCE2 is a project management framework, not a systems development methodology.
Option C (ITIL - Information Technology Infrastructure Library):
Incorrect because ITIL is a set of IT service management (ITSM) best practices, not a software development methodology.
Option D (COBIT - Control Objectives for Information and Related Technologies):
Incorrect because COBIT is a governance framework for IT management and controls, not a development methodology.
IIA GTAG – "Auditing IT Projects and Systems Development": Highlights Waterfall as a traditional systems development methodology.
IIA’s Global Technology Audit Guide on IT Risks: Discusses software development lifecycle risks, including Waterfall methodology.
COBIT Framework – BAI03 (Manage Solutions Identification and Build): References structured methodologies like Waterfall in IT governance.
IIA References: