Requirements Engineering
Types of Testing
Programming Principles
OOP
Agile Software Development
100

These describe what a system should do and define its core functions and behavior.

What are Functional Requirements?

100

This testing focuses on individual units or pieces of code in isolation.

What is Unit Testing?

100

This principle advises that a function should do one thing and do it well.

What is the Single Responsibility Principle?

100

In OOP, this mechanism allows one class to take on the properties and behavior of another class.

What is Inheritance?

100

Has the role of a facilitator and coach for the development team.

Who is the Scrum Master?

200

These requirements focus on performance, usability, reliability, and other qualities.

What are Non-Functional Requirements?

200

This type of testing checks how different modules or components work together.

What is Integration Testing?

200

This principle says “Don’t Repeat Yourself,” aiming to reduce code duplication.

What is DRY (Don't Repeat Yourself)?

200

The practice of hiding internal details and only exposing necessary functionality is known as this.

What is Encapsulation?

200

This ceremony happens every day and keeps the Agile team in sync, usually lasting no more than 15 minutes.

What is the Daily Standup?

300

This document captures all agreed-upon requirements for a software project.

What is a Software Requirements Specification (SRS)?

300

Testing without knowledge of the internal code is called this.

What is Black Box Testing?

300

This principle encourages writing code in a way that others can easily understand.

What is Clean Code?

300

This OOP principle allows objects to take on many forms, such as different implementations of the same interface.

What is Polymorphism?

300

In Scrum, this prioritized list of work items represents everything that might be worked on for a product.

What is the Product Backlog?

400

The process of determining the needs or conditions to meet for a new or altered product is called this.

What is Requirements Elicitation?

400

This type of testing verifies that new changes haven’t broken existing functionality.

What is Regression Testing?

400

This principle suggests designing software components so they can be swapped out with minimal changes to other parts of the system.

What is Loose Coupling?

400

A template or blueprint for creating objects in OOP.

What is a Class?

400

This Agile principle values customer collaboration over this type of document.

What is contract negotiation?

500

In requirements engineering, this term means ensuring that the final system fulfills the documented requirements.

What is Requirements Validation?

500

This type of testing measures how well a system performs under high load or stress.

What is Performance Testing (or Stress Testing)?

500

This principle advises that software entities should be open for extension but closed for modification.

What is the Open/Closed Principle?

500

This term describes when two classes can share methods but don’t share a hierarchical relationship.

What is Interface Implementation (or Composition)?

500

This Agile metric measures how much work a team can complete in a Sprint.

What is Velocity?

M
e
n
u