Which of the following is the best description of a component-based system development method?

A.
Components periodically revisit previous stages to update and verify design requirements

B.
Minimizes the use of arbitrary transfer control statements between components

C.
Uses independent and standardized modules that are assembled into serviceable programs

D.
Implemented in module-based scenarios requiring rapid adaptations to changing client requirements

Explanation:
C: Component-based development involves the use of independent and standardized modules. Each standard module consists of a functional algorithm or instruction set and is
provided with interfaces to communicate with each other. Component-based development adds reusability and pluggable functionality into programs, and is widely used in modern
programming to augment program coherence and substantially reduce software maintenance costs. A common example of these modules is “objects” that are frequently used in
object-oriented programming.
A is incorrect because the spiral method of system development periodically revisits previous stages to update and verify design requirements. The spiral method builds upon the
waterfall method. It uses discrete phases of development with an emphasis on risk analysis, prototypes, and simulations. The spiral method does not specify the development and
testing of components.
B is incorrect because structured programming development involves the use of logical blocks to achieve system design using procedural programming. A structured program layout
minimizes the use of arbitrary transfer control statements like GOTO and emphasizes on single points of entry and exit. This hierarchical approach makes it easier for the program to
be understood and modified later on.
D is incorrect because extreme programming is a methodology that is generally implemented in scenarios requiring rapid adaptations to changing client requirements. Extreme
programming emphasizes client feedback to evaluate project outcomes and to analyze project domains that may require further attention. The coding principle of extreme programming
throws out the traditional long-term planning carried out for code reuse and instead focuses on creating simple code optimized for the contemporary assignment