1What is the purpose of coding standards?
To ensure code performs well, is easy to add to, maintain, debug, and is written in a consistent style across a project.
2Why are coding standards needed?
They avoid developers coding in their own style, provide consistency, improve readability, simplify maintenance, and enable company-wide standardisation.
3What does KISS stand for in programming principles?
Keep It Short and Simple.
4What does DRY stand for in programming principles?
Don’t Repeat Yourself.
5What is the goal of abstraction in programming?
Each significant piece of functionality should be implemented in just one place in the source code.
6What does the Open/Closed Principle state?
Software entities should be open for extension but closed for modification.
7What is the Single Responsibility Principle?
A code component should perform a single, well-defined task.
8What does minimizing coupling mean?
Reducing dependencies between code sections and limiting use of shared variables.
9What does maximizing cohesion mean?
Placing code with similar functionality within the same component.
10What is the rule for abbreviations in naming conventions?
No abbreviations should be used.
11What kind of names should developers use?
Meaningful, intention-revealing names.
12How should variable names be written?
All lowercase with words separated by underscores, descriptive but concise.
13What are the standard loop indices?
i, j for nested loops.
14What are code smells?
Indicators of poor design that make code harder to maintain.
15Give examples of code smells.
Duplicated code, large classes, long methods, long parameter lists.
16What is refactoring?
Improving software’s internal structure safely without changing behaviour or external interfaces.
17What are the benefits of refactoring?
More readable and simplified code, easier to change, reduced redundancy, guidance on continuous improvement.
18What is the purpose of software testing?
To exercise a program with the intent of finding errors before delivery to the end user.
19What is desk checking?
Reviewing program code to spot logic errors.
20What is a code review?
A group review by 3–5 IT staff to identify errors, apply quality standards, and verify design requirements.
21What is unit testing?
Testing an individual program or module to find execution and logic errors.
22Who usually creates test data for unit testing?
Someone other than the programmer.
23What is integration testing?
Testing two or more programs that depend on each other to ensure proper collaboration.
24What is system testing?
Verifying all system components work together and handle real processing situations correctly.
25What does system testing confirm?
That the information system can handle predicted data volumes efficiently.
26What is a test plan?
A guide for testing software, usually prepared before software is built.
27What kind of data does a test plan use?
Dummy data (sample data).
28Who prepares a test plan?
Software testers.
29What are some example fields in a test plan?
Test Case, Test Type, Test Steps, Expected Result, Actual Result, Remarks.