Program Development Life cycle — common mistakes

When asked about testing, be specific. Don't just say 'test the program'. Mention creating a test plan with specific test data (valid, boundary, invalid) and describe what is being checked. For example, 'Test the login module with a valid username and password, then with an invalid password, and finally with a username that is too long to check input validation.'

Examiners frequently ask for definitions and examples of the three types of maintenance. Memorise a clear, distinct example for each: Corrective (fixing a crash), Adaptive (making it work on Windows 11), and Perfective (adding a new report feature).

The model described here, often called the 'waterfall model', is linear and sequential. It's the primary model you need to know for the 9618 syllabus. However, in the real world, many other models exist, such as Agile methodologies. Agile models are iterative, meaning developers work in small cycles, repeating the design, code, and test stages for small parts of the project at a time. This allows for more flexibility and adaptation to changing requirements.

This is a common point of confusion. Think of it this way: Analysis is about the 'WHAT' and Design is about the 'HOW'. The Analysis stage focuses on WHAT the system must do, defining the user requirements and goals without considering the implementation. The Design stage takes those requirements and figures out HOW the system will be built, creating the technical blueprint with algorithms, data structures, and architecture.