New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB ATM Exam - Topic 3 Question 71 Discussion

Actual exam question for ISTQB's ATM exam
Question #: 71
Topic #: 3
[All ATM Questions]

Assume you are currently working on a project developing a system where functional

requirements are very well specified. Unfortunately non-functional requirements do almost not exist.

You are the Test Manager. You have to choose a technique for test selection that allows testing of non-functional characteristics, especially reliability.

Which of the following techniques for test selection do you expect being most useful in this scenario?

K2 1 credit

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

0/2000 characters
Theron
2 months ago
Test condition analysis might be useful, but not my first choice.
upvoted 0 times
...
Hubert
2 months ago
Definitely going with operational profiles for this one!
upvoted 0 times
...
Yvette
3 months ago
I think ambiguity reviews could help too, but not as much.
upvoted 0 times
...
Lashawn
3 months ago
Wait, can a model really cover all non-functional aspects?
upvoted 0 times
...
Ettie
3 months ago
A model-based technique is great for reliability testing!
upvoted 0 times
...
Elmira
3 months ago
Cause-effect graphing seems more suited for functional testing, right? I feel like it wouldn't help much with non-functional aspects like reliability.
upvoted 0 times
...
Rupert
4 months ago
Test condition analysis sounds familiar, but I can't recall if it specifically addresses reliability. I might need to double-check that.
upvoted 0 times
...
Kenneth
4 months ago
I'm not entirely sure, but I think ambiguity reviews focus more on functional requirements rather than non-functional ones.
upvoted 0 times
...
Franchesca
4 months ago
I remember studying that model-based techniques can help in defining how the system should behave under different conditions, especially for reliability.
upvoted 0 times
...
Merissa
4 months ago
Test condition analysis seems like the most straightforward option to me. If we can identify the key conditions and scenarios that impact reliability, we can focus our testing efforts there.
upvoted 0 times
...
Aaron
4 months ago
Ambiguity reviews could be a good way to try and uncover any hidden non-functional requirements that weren't properly documented. It's worth considering, even if it's not the most direct approach.
upvoted 0 times
...
Fabiola
5 months ago
A model-based technique based on operational profiles sounds like it could be a good approach here. If we can create a model of how the system is expected to be used, that might help us identify reliability issues.
upvoted 0 times
...
Annelle
5 months ago
This seems like a tricky one. With the lack of non-functional requirements, I'm not sure which technique would be most useful for testing reliability. I'll have to think this through carefully.
upvoted 0 times
...
Sherita
7 months ago
Non-functional requirements? What is this, the Bermuda Triangle of software development? I say we just throw the whole project into the ocean and start over.
upvoted 0 times
...
Iluminada
7 months ago
Cause-effect graphing? Really? That's like trying to catch a fish with a net made of string. A model-based technique is clearly the best option here.
upvoted 0 times
Janna
7 months ago
User 2: I agree, a model-based technique would be more effective in this scenario.
upvoted 0 times
...
Deonna
7 months ago
User 1: Cause-effect graphing is not the best choice here.
upvoted 0 times
...
...
Jeanice
8 months ago
I'm not sure, but I think D) Cause-effect graphing could also be useful for testing non-functional characteristics.
upvoted 0 times
...
Sherell
8 months ago
I agree, a model-based technique is the way to go. It'll let us simulate real-world usage and put the system through its paces. Plus, it's better than relying on those sketchy non-functional requirements, or lack thereof.
upvoted 0 times
Lindy
7 months ago
User 3: Yeah, relying on non-existent non-functional requirements can be risky. A model-based approach sounds solid.
upvoted 0 times
...
Brande
7 months ago
User 2: I agree, it's important to simulate real-world usage for testing reliability.
upvoted 0 times
...
Abel
7 months ago
User 1: I think A) A model-based technique based on the creation of operational profiles would be the most useful in this scenario.
upvoted 0 times
...
...
Svetlana
8 months ago
Test condition analysis could also be helpful, but it might not give us a complete picture without the non-functional requirements. A model-based approach sounds like the way to go.
upvoted 0 times
...
Cassie
8 months ago
I agree with Portia. Operational profiles can help simulate real-world scenarios for testing reliability.
upvoted 0 times
...
Elza
8 months ago
A model-based technique based on the creation of operational profiles seems like the best choice here. Without clear non-functional requirements, we'll need to rely on analyzing the system's expected usage patterns to test its reliability.
upvoted 0 times
Judy
7 months ago
User 2: Yeah, I agree. We need to analyze the system's expected usage patterns to test its reliability.
upvoted 0 times
...
Donte
7 months ago
User 3: Yeah, we need to focus on testing the system's reliability based on how it's expected to be used.
upvoted 0 times
...
Georgene
7 months ago
User 1: I think A) A model-based technique based on the creation of operational profiles is the way to go.
upvoted 0 times
...
Rosalind
7 months ago
User 2: I agree, without clear non-functional requirements, analyzing usage patterns seems like the best approach.
upvoted 0 times
...
Shawn
8 months ago
User 1: I think A) A model-based technique based on the creation of operational profiles is the way to go.
upvoted 0 times
...
...
Portia
8 months ago
I think A) A model-based technique based on the creation of operational profiles would be most useful.
upvoted 0 times
...

Save Cancel