Practice Flashcards
7 cards from real B.S.W.E. Bachelor of Software Engineering practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Practice flashcards as text
Which refactoring technique replaces a temporary variable with a direct call to the expression that assigned it?
Answer: Inline Temp
Inline Temp removes a temporary variable by substituting its value expression directly wherever the variable is used.
In test-driven development (TDD), what is the correct sequence of steps?
Answer: Write test → Make it pass → Refactor
TDD follows the Red-Green-Refactor cycle: write a failing test, write minimal code to pass it, then refactor.
Which version control strategy involves developers integrating code changes into a shared branch multiple times per day?
Answer: Continuous Integration
Continuous Integration requires developers to merge code frequently (at least daily) and run automated builds and tests on each integration.
A code review reveals a function is 300 lines long and performs database access, business logic, and UI formatting. Which principle is violated?
Answer: Single Responsibility Principle
The Single Responsibility Principle states a class or function should have only one reason to change, but this function handles three distinct concerns.
What does a cyclomatic complexity value of 15 in a single method indicate?
Answer: The method has 15 independent paths requiring test coverage
Cyclomatic complexity counts the number of linearly independent paths through code, indicating the minimum number of test cases needed for branch coverage.
Which practice involves automatically deploying every code change that passes all automated tests directly to production?
Answer: Continuous Deployment
Continuous Deployment automatically releases every passing build to production without human intervention, while Continuous Delivery still requires a manual approval step.
When using pair programming, what is the role of the 'navigator'?
Answer: Reviews the code being typed and thinks about design and direction
In pair programming the navigator reviews code in real time, thinks about the broader design, spots errors, and guides the driver who types.