Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB Exam CTAL-TTA Topic 1 Question 15 Discussion

Actual exam question for ISTQB's CTAL-TTA exam
Question #: 15
Topic #: 1
[All CTAL-TTA Questions]

Your team is now accountable for the support and enhancement of a payroll system that has been in production for many years and modified by many different developers. It has been noticed by management that small functional enhancements take much longer than equivalent changes on more recently developed systems. You have been tasked with implementing improved testing approaches that will help to identify the root cause of this problem.

Which of the following is the best technique to apply in this scenario?

Show Suggested Answer Hide Answer
Suggested Answer: C

Static analysis is the best technique for identifying the root causes of issues in a legacy system where small functional enhancements take disproportionately long to implement. This technique involves examining the code without executing it to detect potential vulnerabilities, coding errors, and complexities. Static analysis can highlight problematic code segments and inefficient coding practices that may contribute to the increased time required for implementing changes, thereby assisting in addressing these systemic issues efficiently.


Contribute your Thoughts:

Tennie
5 months ago
I think exploratory analysis might provide some insights as well.
upvoted 0 times
...
Phyliss
5 months ago
I believe data flow analysis could also be useful in this scenario.
upvoted 0 times
...
Fanny
5 months ago
I agree with Layla, static analysis can help identify the root cause of the problem.
upvoted 0 times
...
Layla
5 months ago
I think the best technique to apply is static analysis.
upvoted 0 times
...
Mozelle
5 months ago
Exploratory analysis, eh? Might as well just throw darts at the code and see what sticks. Hey, it's worth a shot!
upvoted 0 times
Lashon
4 months ago
D) Data flow analysis
upvoted 0 times
...
Odette
4 months ago
Yeah, sometimes taking a more exploratory approach can lead to unexpected discoveries that can improve the system.
upvoted 0 times
...
Theodora
4 months ago
Exploratory analysis can actually be a valuable technique in uncovering hidden issues in the code.
upvoted 0 times
...
Tamesha
4 months ago
D) Data flow analysis
upvoted 0 times
...
Abel
4 months ago
C) Static analysis
upvoted 0 times
...
Edelmira
4 months ago
C) Static analysis
upvoted 0 times
...
Tanja
4 months ago
B) Exploratory analysis
upvoted 0 times
...
Jestine
4 months ago
B) Exploratory analysis
upvoted 0 times
...
Rickie
5 months ago
A) Orthogonal arrays
upvoted 0 times
...
Eloisa
5 months ago
A) Orthogonal arrays
upvoted 0 times
...
...
Nell
5 months ago
Static analysis, huh? Sounds like a good way to put the system to sleep while we figure out what's going on. I'm down for that!
upvoted 0 times
...
Colette
5 months ago
Orthogonal arrays? Isn't that what they use to map out the galaxy in sci-fi movies? I'll pass on that one.
upvoted 0 times
...
Daniel
5 months ago
Hmm, data flow analysis sounds like the way to go. Gotta follow that data through the spaghetti code, am I right?
upvoted 0 times
Lina
4 months ago
Definitely, it's important to understand how the data moves through the system.
upvoted 0 times
...
Emile
4 months ago
Yeah, data flow analysis seems like the most logical choice.
upvoted 0 times
...
Dottie
5 months ago
Hmm, data flow analysis sounds like the way to go. Gotta follow that data through the spaghetti code, am I right?
upvoted 0 times
...
Delpha
5 months ago
D) Data flow analysis
upvoted 0 times
...
Deonna
5 months ago
C) Static analysis
upvoted 0 times
...
Hannah
5 months ago
B) Exploratory analysis
upvoted 0 times
...
Lenna
5 months ago
A) Orthogonal arrays
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77