CTAL-TTA_001 · Question #18
Part 1 "Test Techniques various" An embedded software company is considering to improve the quality of its software components to be delivered to the integration team. After studying various…
The correct answer is C. Both are usually undertaken by development during coding and unit testing E. Both usually use a tool. Static analysis (e.g., linters, SAST tools like SonarQube) and dynamic analysis (e.g., unit tests, memory profilers) share two key traits: both are primarily performed by developers during coding and unit testing (C), and both almost always require a dedicated tool (E) - you…
Question
Part 1 "Test Techniques various" An embedded software company is considering to improve the quality of its software components to be delivered to the integration team. After studying various experience papers that report a higher level of quality for software components, two main alternative techniques are identified:
static analysis and dynamic analysis. In deciding which one is most applicable and how they relate to each other a detailed study is performed. Which of the following are TWO key similarities between static analysis and dynamic analysis? 2 credits [K4]
Options
- ABoth are performed using requirements as its major input document
- BBoth are usually undertaken by integration testers
- CBoth are usually undertaken by development during coding and unit testing
- DBoth are related to reviews
- EBoth usually use a tool
How the community answered
(67 responses)- A19% (13)
- B4% (3)
- C67% (45)
- D9% (6)
Explanation
Static analysis (e.g., linters, SAST tools like SonarQube) and dynamic analysis (e.g., unit tests, memory profilers) share two key traits: both are primarily performed by developers during coding and unit testing (C), and both almost always require a dedicated tool (E) - you can't practically do static code analysis or instrument runtime behavior by hand at scale.
Why the distractors are wrong:
- A is wrong because static analysis takes source code as its primary input, not requirements; requirements-based testing is a different technique.
- B is wrong because both techniques belong to the development phase, not integration testing - integration testers pick up the work after components are delivered.
- D is wrong because reviews are a separate form of static testing (human-led inspection); static analysis is automated tool scanning, and dynamic analysis involves executing code - neither is a review.
Memory tip: Think of the two "D's" - both static and dynamic analysis are done by Developers using Dedicated tools. That maps directly to C and E. If an answer says "integration testers" or "requirements document," it's describing the wrong phase or the wrong input.
Topics
Community Discussion
No community discussion yet for this question.