All relevance

Question 1

*Agile Methodology

Answer 1

An iterative software development approach focusing on collaboration, customer feedback, and small rapid releases.

Question 2

*Waterfall Model

Answer 2

A linear and sequential software development approach with distinct phases: requirements, design, implementation, verification, and maintenance.

Question 3

*Software Development Life Cycle (SDLC)

Answer 3

The process of planning, creating, testing, and deploying an information system.

Question 4

*UML (Unified Modeling Language)

Answer 4

A standardized modeling language used to visualize the design of a system.

Question 5

*Design Patterns

Answer 5

Reusable solutions to common problems in software design, such as Singleton, Factory, and Observer.

Question 6

*Cohesion

Answer 6

The degree to which elements of a module belong together; high cohesion is desirable.

Question 7

*Coupling

Answer 7

The degree of interdependence between software modules; low coupling is ideal.

Question 8

SOLID Principles

Answer 8

Five design principles intended to make software designs more understandable, flexible, and maintainable.

Question 9

*MVC (Model-View-Controller)

Answer 9

An architectural pattern that separates an application into three interconnected components.

Question 10

Dependency Injection

Answer 10

A technique where one object supplies the dependencies of another, improving modularity.

Question 11

*Unit Testing

Answer 11

Testing individual components of the software in isolation.

Question 12

Integration Testing

Answer 12

Testing the interaction between integrated units/modules.

Question 13

Regression Testing

Answer 13

Testing existing functionality after changes to ensure it still works.

Question 14

Mocking

Answer 14

Simulating the behavior of real objects in controlled ways for testing.

Question 15

Code Smells

Answer 15

Signs in the code that may indicate a deeper problem.

Question 16

*Functional Requirements

Answer 16

Statements of the services the system should provide.

Question 17

*Non-Functional Requirements

Answer 17

Requirements that define system attributes such as reliability, usability, and performance.

Question 18

*Use Case Diagram

Answer 18

A visual representation of the system’s functional requirements from the user’s perspective.

Question 19

Sequence Diagram

Answer 19

A type of UML diagram showing interactions over time.

Question 20

Activity Diagram

Answer 20

A type of UML diagram that represents workflows of stepwise activities and actions.

Question 21

*Gantt Chart

Answer 21

A bar chart that represents a project schedule.

Question 22

MoSCoW Prioritization

Answer 22

A method to prioritize requirements as Must have, Should have, Could have, and Won’t have.

Question 23

Risk Management

Answer 23

The process of identifying, assessing, and controlling threats to a project.

Question 24

*Technical Debt

Answer 24

The cost of choosing an easy solution now instead of a better approach that would take longer.

Question 25

*Relationship: Agile vs Waterfall

Answer 25

Agile allows for iterative development with user feedback; Waterfall follows a strict linear progression.

Question 26

*Relationship: Cohesion vs Coupling

Answer 26

High cohesion and low coupling are design goals that enhance modularity and maintainability.

Question 27

*Relationship: Unit Testing and Dependency Injection

Answer 27

Dependency injection facilitates unit testing by allowing mock objects to be injected.

Question 28

*Relationship: Use Case Diagram and Functional Requirements

Answer 28

Use case diagrams visually represent the functional requirements of a system.

Question 29

*Relationship: MVC and Separation of Concerns

Answer 29

MVC enforces separation of concerns by dividing the application into input, processing, and output.