SDLC
Design
Architecture Patterns
Programming Principles
Agile Development and Testing
100

This is what SDLC stands for

What is Software Development Life Cycle

100

This diagram type represents a static view of the system

Class diagram

100

This pattern may make it easy to create applications quickly, but difficult to split up later

Layered

100

This is what KISS stands for

What is Keep it Simple Stupid

100

This is the definition of a sprint

a short, time-boxed period when a scrum team works to complete a set amount of work

200

This is the description of the term requirements

a non-technical definition of features that users expect from the system

200

These diagram types aim to show the purpose of objects and their relationships

Object diagram

200

This pattern often has shared servers as a bottleneck

Client-server

200

This is what YAGNI stands for 

You Aren't Gonna Need It

200

These are the 6 phases of testing

Requirement Analysis, Test planning, Test case design and development, Test environment setup, Test execution, Test cycle closure




300

These are the characteristics of non-functional requirements

What is usability, reliability, and performance

300

This diagram type demonstrates the physical hardware being used

Deployment Diagram

300

This is the purpose of the MVC pattern

Organizing large-sized web applications

300

This is the meaning behind the principle composition over inheritance

Objects with complex behaviors should contain instances of objects with individual behaviors.

300

If you're concerned with verification, you might ask yourself this

Am I building the product right?

400

These are the kinds of requirements associated with functional requirements

What are business, users and product

400

Used to visualize the interaction between objects in a specific order

Sequence diagram

400

This pattern is agile, small, and separated

microservices

400

This is what SOC stands for

Separation of Concerns

400
these are the types of testing

Unit, integration, system, acceptance

500

These are the phases of the software development life cycle

Requirements, Design, Implementation, Verification, Maintenance

500

Summarize the details of your systems user and how they interact with it

Use Case diagram

500

This architecture pattern is a derivation of the MVC pattern

MVP (Model-View-Presenter)

500

This is the purpose of refactoring

Revisiting code looking for ways to optimize it

500

These are the core values of agile development

Individual and interactions, Working software, Customer collaboration, Responding to change