SDLC
Testing
OOP
Databases
GIT & AGILE
100

First phase of SDLC

Planning
100

Testing small parts of code

Unit Testing

100

Hiding internal data

Encapsulation 

100

Command to retrieve data

SELECT

100

Tool for version control

Git

200

Phase where requirements are gathered

Requirements 

200

Testing full system

System Testing

200

Same method, different behavior

Polymorphism 

200

Combines tables

JOIN

200

Online hosting platform

GitHub 

300

Phase where code is written

Implementation

300

“Built right vs right product” refers to

Verification vs Validation

300

Blueprint of a class

Abstraction

300

Unique identifier

Primary Key

300

Send changes to remote

Push

400

Phase where bugs are found

Testing

400

Type of testing done by users

Acceptance testing

400

Reusing code from another class

Inheritance

400

Links tables together

Foreign Key

400

Pull changes from remote

Pull

500

Final phase after deployment

Maintenance 

500

Can software ever be bug-free?

No

500

Preferred approach over inheritance

Composition

500

Deletes data

Delete

500

Short development cycle in Agile

Sprint