nerdexam
CompTIA

CAS-002 · Question #305

A software development manager is taking over an existing software development project. The team currently suffers from poor communication due to a long delay between requirements documentation and…

The correct answer is B. Waterfall. Waterfall's sequential, phase-gated structure creates a long delay between upfront requirements documentation and final feature delivery, allowing security flaws to persist undetected until production.

Integration of Computing, Communications and Business Disciplines

Question

A software development manager is taking over an existing software development project. The team currently suffers from poor communication due to a long delay between requirements documentation and feature delivery. This gap is resulting in an above average number of security-related bugs making it into production. Which of the following development methodologies is the team MOST likely using now?

Options

  • AAgile
  • BWaterfall
  • CScrum
  • DSpiral

How the community answered

(38 responses)
  • A
    5% (2)
  • B
    89% (34)
  • C
    3% (1)
  • D
    3% (1)

Why each option

Waterfall's sequential, phase-gated structure creates a long delay between upfront requirements documentation and final feature delivery, allowing security flaws to persist undetected until production.

AAgile

Agile methodology uses short, iterative cycles with continuous stakeholder feedback and frequent delivery, which minimizes the gap between requirements and working features.

BWaterfallCorrect

Waterfall methodology enforces a strict linear sequence - requirements, design, implementation, testing, deployment - where each phase must be completed before the next begins. This creates a large temporal gap between requirements documentation and delivery, making it difficult to catch security defects early and resulting in a higher rate of security bugs reaching production.

CScrum

Scrum is an Agile framework using time-boxed sprints (typically 2-4 weeks) that produce shippable increments regularly, keeping requirements and delivery tightly coupled.

DSpiral

Spiral methodology is an iterative, risk-driven model that incorporates repeated prototyping and risk analysis cycles, enabling early identification of defects including security issues.

Concept tested: Waterfall SDLC delays and security vulnerability impact

Source: https://csrc.nist.gov/publications/detail/sp/800-64/rev-2/final

Topics

#waterfall methodology#SDLC#requirements documentation#software development

Community Discussion

No community discussion yet for this question.

Full CAS-002 Practice