9618 · 12.1
Program Development Life cycle flashcards
Revision flashcards for Cambridge 9618 Program Development Life cycle (syllabus 12.1). Flip, recall, then mark a real past-paper question.
Card
What is the Program Development Life Cycle (PDLC)?
A structured, phased process that provides a framework for developing software from initial concept to final deployment and maintenance.
Card
What is the main purpose of the Analysis stage?
To investigate and understand the problem, gather user requirements, and establish the exact specifications for the new system.
Card
What is the main purpose of the Design stage?
To create a detailed plan or 'blueprint' of how the system will be built. This includes designing algorithms, data structures, user interfaces, and system architecture.
Card
What is the main purpose of the Coding stage?
To translate the designs from the previous stage into machine-readable instructions using a suitable programming language. This is the implementation phase.
Card
What is the main purpose of the Testing stage?
To systematically find and document errors (bugs) in the software to ensure it meets the requirements defined in the analysis stage and functions correctly.
Card
What is the main purpose of the Maintenance stage?
To make changes to the software after it has been delivered. This includes fixing bugs, adapting to new environments, and adding new features.
Card
What is Corrective Maintenance?
Fixing bugs or errors that were not discovered during the testing phase. For example, fixing a crash that occurs under specific, unforeseen circumstances.
Card
What is Adaptive Maintenance?
Updating the program to keep it functional in a changing environment. For example, updating an application to run on a new version of an operating system.
Card
What is Perfective Maintenance?
Improving or enhancing the software by adding new features or improving performance, based on user feedback or new requirements. For example, adding a 'dark mode' to an application.
Card
What is a 'requirements specification'?
A formal document produced at the end of the Analysis stage. It details precisely what the system must do, serving as a contract between the developer and the client.
Card
What is the key output of the Design stage?
Algorithms (often in pseudocode or as flowcharts), data structure definitions, and user interface layouts.
Card
What is a common trap when describing the PDLC in an exam?
Being too vague. Instead of 'test the program', specify the type of testing (e.g., black-box, white-box, integration) and what is being tested (e.g., individual modules, the whole system).