Software Engineering Fundamentals
Software Design & Architecture
UML Diagrams
Agile & Process Models
OOP & Programming Principles
100

This term describes a systematic approach to analysis, design, implementation, testing, and maintenance of software

What is software engineering?

100

This architecture pattern divides a system into presentation, business logic, and data layers

What is Layered architecture?

100

These two main categories of UML diagrams show system structure and system behavior respectively

What are structural (static) and behavioral (dynamic) diagrams?

100

This Agile framework uses time-boxed iterations called sprints, typically lasting two weeks

What is Scrum?

100

These are the four pillars of object-oriented programming

What are Encapsulation, Abstraction, Inheritance, and Polymorphism?

200

These are the five phases of the SDLC in order

What are Requirements → Design → Implementation → Verification → Maintenance?

200

 In MVC, these three components handle the user interface, business logic, and data respectively

What are View, Controller, and Model?

200

This behavioral diagram shows the interaction between objects over time through method calls

What is a Sequence diagram?

200

These two roles in Scrum are responsible for facilitating the process and managing the product backlog

Who are the Scrum Master and Product Owner?

200

This principle allows one interface to have multiple implementations


What is Polymorphism?

300

In the WRSPM model, these two components represent what users want versus the technical design

What are Requirements and Specification?

300

This architecture pattern involves small, independently deployable services

What are Microservices?

300

This structural diagram shows classes with their attributes, methods, and relationships

What is a Class diagram?

300

This Agile methodology emphasizes pair programming, test-driven development, and continuous integration

What is Extreme Programming (XP)?

300

This acronym warns against building features you don't currently need

What is YAGNI (You Aren't Gonna Need It)?

400

These two types of requirements describe what the system does versus constraints on the system

What are functional and non-functional requirements?

400

The "S" and "O" in SOLID stand for these two principles

What are Single Responsibility Principle and Open/Closed Principle?

400

This diagram type models the flow of control from one activity to another, similar to a flowchart

What is an Activity diagram?

400

These are the four values stated in the Agile Manifesto

What are individuals and interactions, working software, customer collaboration, and responding to change?

400

This term refers to the future cost incurred from taking shortcuts in code, and this practice improves internal code structure without changing external behavior

What are Technical Debt and Refactoring?

500

Spending extra time in this phase reduces cost and rework later.

What is the Requirements phase?


500

This design goal minimizes coupling and maximizes cohesion.

What is Separation of Concerns?

500

This diagram shows how objects collaborate in response to a single use case.

What is a Communication diagram?

500

This artifact contains prioritized user stories for future work.

What is the Product Backlog?

500

This principle states that high-level modules should not depend on low-level modules.

What is the Dependency Inversion Principle