iSQI CTAL-TM_Syll2012 Exam - Topic 2 Question 64 Discussion

Actual exam question for iSQI's CTAL-TM_Syll2012 exam

Question #: 64
Topic #: 2

[All CTAL-TM_Syll2012 Questions]

You are the Test Manager of a project that adopts a V-model with four formal levels of testing.

unit, integration, system and acceptance testing.

On this project reviews have been conducted for each development phase prior to testing, which is to say that reviews of requirements, functional specification, high-level design, low-level design and code have been performed prior to testing.

Assume that no requirements defects have been reported after the release of the product. Which TWO of the following metrics do you need in order to evaluate the requirements reviews in terms of phase containment effectiveness?

K3 2 credits

ANumber of defects found during the requirements review

BTotal number of defects attributable to requirements found during unit, integration, system and acceptance testing

CTotal number of defects found during functional specification review, high-level design review, low-level design review, code review, unit testing, integration testing, system testing and acceptance testing

DTime to conduct the requirements review

ETotal number of defects attributable to requirements, found during functional specification review, high-level design review, low-level design review, code review, unit testing, integration testing, system testing and acceptance testing

Show Suggested Answer

Suggested Answer: C, E

by Lucina at Jul 18, 2024, 09:01 AM

Limited Time Offer

25%

Off

Get Premium CTAL-TM_Syll2012 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Izetta

3 months ago

Time to conduct the review? Not sure that’s relevant for effectiveness.

upvoted 0 times

...

Nickole

3 months ago

I agree with the first two options, they make the most sense.

upvoted 0 times

...

Yoko

3 months ago

Wait, how can there be no requirement defects reported? Sounds fishy!

upvoted 0 times

...

Jolene

4 months ago

I think the total defects found during testing phases is crucial too.

upvoted 0 times

...

Aracelis

4 months ago

Definitely need the number of defects found during the requirements review!

upvoted 0 times

...

Ryann

4 months ago

I practiced a similar question, and I think we need to focus on metrics that show the effectiveness of the reviews, so maybe A and B are the right choices.

upvoted 0 times

...

Leota

4 months ago

I feel like option B makes sense too because it looks at defects found in later testing phases, which helps measure if the requirements were solid.

upvoted 0 times

...

Colene

4 months ago

I'm not entirely sure, but I think option A could be one of the metrics since it directly relates to the requirements review.

upvoted 0 times

...

Val

5 months ago

I remember that phase containment effectiveness is about how well we catch defects early, so I think we need metrics related to defects found in reviews versus those found later.

upvoted 0 times

...

Yuette

5 months ago

Hmm, I'm a little confused on this one. There are a lot of options here, and I'm not sure which two metrics would be the most useful for evaluating the requirements review. I think I'd go with the number of defects found during the requirements review (A) and the total time it took to conduct the requirements review (D). That should give me a sense of how thorough and efficient the review process was.

upvoted 0 times

...

Dorian

5 months ago

Alright, this seems straightforward enough. Since no requirements defects were found after release, I'd say the two metrics I need are the number of defects found during the requirements review (A) and the total number of requirements-related defects found during testing (B). That should give me a clear picture of how well the requirements review caught issues before they became bigger problems.

upvoted 0 times

...

Adelle

5 months ago

Okay, let's think this through. We know that no requirements defects were reported after the product was released, so that's good. I'm thinking the two metrics I need are the total number of defects found across all the reviews and testing (C), and the total number of requirements-related defects found in all the reviews and testing (E). That should give me a good sense of how effective the requirements review was.

upvoted 0 times

...

Lashawnda

5 months ago

Hmm, this is a tricky one. I think the key is to focus on the requirements review and how effective it was in finding defects before they made it to testing. I'd say the two metrics I need are the number of defects found during the requirements review (A) and the total number of requirements-related defects found throughout the entire testing process (B).

upvoted 0 times

...

Britt

5 months ago

Okay, I think I've got a good handle on this. Implementing a Cloud VPN or Identity-Aware Proxy TCP forwarding seems like the best way to maintain SRE access while reducing the external attack surface. I'll make sure to read the details carefully before selecting my answer.

upvoted 0 times

...

Idella

5 months ago

I remember discussing how increased turnover could lead to higher receivable days if credit terms are extended, but I'm not sure if that's the case here.

upvoted 0 times

...

Rodolfo

10 months ago

I'm with the others on this one. B and E are the metrics you need. Though I kind of wish the question had asked for the number of coffee cups consumed during the requirements review. That would be a more useful metric, don't you think?

upvoted 0 times

Walker

9 months ago

E) Total number of defects attributable to requirements, found during functional specification review, high-level design review, low-level design review, code review, unit testing, integration testing, system testing and acceptance testing

upvoted 0 times

...

Temeka

9 months ago

B) Total number of defects attributable to requirements found during unit, integration, system and acceptance testing

upvoted 0 times

...

Joye

9 months ago

A) Number of defects found during the requirements review

upvoted 0 times

...

Huey

10 months ago

Haha, I guess the developers must have aced the requirements review if no defects were found after release. Maybe they just wrote really vague requirements to begin with!

upvoted 0 times

Tish

9 months ago

B) Total number of defects attributable to requirements found during unit, integration, system and acceptance testing

upvoted 0 times

...

Judy

9 months ago

A) Number of defects found during the requirements review

upvoted 0 times

...

Erinn

10 months ago

I also think C could be useful to see the total number of defects found across all reviews and testing phases.

upvoted 0 times

...

Tori

10 months ago

I agree with Phillip. A will show us the defects found during the requirements review, and B will give us the total number of defects attributable to requirements found during testing.

upvoted 0 times

...

Aron

11 months ago

I agree with Carisa. Option B and E are the way to go. Tracking the requirements-related defects through the different testing phases is crucial.

upvoted 0 times

Laura

9 months ago

I agree, Option E is also crucial as it includes all the defects found in different reviews and testing phases related to requirements.

upvoted 0 times

...

Rima

10 months ago

I think Option B is important because it tracks all the defects related to requirements found during testing phases.

upvoted 0 times

...

Phillip

11 months ago

I think we need to consider both A and B to evaluate the requirements reviews.

upvoted 0 times

...

Carisa

11 months ago

The correct answers are B and E. These metrics will help evaluate the effectiveness of the requirements review in terms of phase containment. Knowing the total number of defects attributable to requirements is key.

upvoted 0 times