Untitled Deck

Question 1

Agile

Answer 1

Iterative approach to software development.

Question 2

Minimum Viable Product

Answer 2

Basic version meeting essential customer needs.

Question 3

Milestone Build

Answer 3

Significant stage marking software development progress.

Question 4

Velocity

Answer 4

Days of work divided by total work.

Question 5

Burn Down Chart

Answer 5

Visual representation of work left over time.

Question 6

User Stories

Answer 6

Descriptions of software functionality from user perspective.

Question 7

Task

Answer 7

Small piece of functionality for development.

Question 8

Stand-up Meetings

Answer 8

Daily briefings to track progress and issues.

Question 9

Unplanned Tasks

Answer 9

Tasks added outside the original plan.

Question 10

Use Case

Answer 10

Detailed description of software functionality.

Question 11

Epic

Answer 11

Large user flow encompassing multiple features.

Question 12

Product Backlog

Answer 12

Prioritized list of user stories and tasks.

Question 13

Issue Boards

Answer 13

Visual representation of task progress through phases.

Question 14

SWEBOK

Answer 14

Software engineering body of knowledge.

Question 15

Software Design

Answer 15

Application of principles to define software systems.

Question 16

Architectural Design

Answer 16

Framework for hardware and software component interfaces.

Question 17

Detailed Design

Answer 17

Complete design ready for implementation.

Question 18

UML

Answer 18

Unified modeling language for system design.

Question 19

Associations

Answer 19

Relationships between classes in object-oriented design.

Question 20

Aggregation

Answer 20

Class A contains Class B without ownership.

Question 21

Composition

Answer 21

Class C owns Class D

Question 22

Inheritance

Answer 22

Class E derives properties from Class F.

Question 23

Sequence Diagrams

Answer 23

Visualizes object communication during a use-case.

Question 24

Statechart Diagrams

Answer 24

Represents object states and transitions.

Question 25

Design Patterns

Answer 25

Reusable solutions to common design problems.

Question 26

Facade Pattern

Answer 26

Simplified interface to complex systems.

Question 27

Observer Pattern

Answer 27

One-to-many dependency for state change notifications.

Question 28

Builder Pattern

Answer 28

Constructs complex objects without exposing logic.

Question 29

Singleton Pattern

Answer 29

Ensures a class has one instance globally.

Question 30

Iterator Pattern

Answer 30

Access elements without exposing underlying structure.

Question 31

Single Responsibility Principle

Answer 31

Each object should have one reason to change.

Question 32

Cohesion

Answer 32

Class represents a single concept effectively.

Question 33

Test Driven Development

Answer 33

Writing tests before implementing code.

Question 34

TDD Cycle

Answer 34

Red

Question 35

Red Phase

Answer 35

Write a failing test to start development.

Question 36

Green Phase

Answer 36

Implement code to pass the test.

Question 37

Refactor Phase

Answer 37

Clean up code after passing tests.

Question 38

Low Coupling

Answer 38

Classes are independent of each other.

Question 39

High Cohesion

Answer 39

Classes are focused on a single task.

Question 40

Database Logic Separation

Answer 40

Keeps database and logic in distinct classes.

Question 41

Burn Out

Answer 41

Fatigue from overscheduling affects productivity.

Question 42

Epic in GitLab

Answer 42

Title card with child issues for larger flows.

Question 43

Task Estimates

Answer 43

Estimates for individual tasks within user stories.

Question 44

Flow of Events

Answer 44

Sequence of actions in a use case.

Question 45

Entry Conditions

Answer 45

Preconditions for a use case to start.

Question 46

Exit Conditions

Answer 46

Postconditions after a use case completes.

Question 47

Special Requirements

Answer 47

Unique constraints or needs for a use case.