Software Process Models Questions and Answers

Answer: D

'Circular' is not a valid software life cycle model. JAD (Joint Application Development) is a method of gathering requirements through workshops that the key treats as valid, and the iterative and prototype models are recognised models. The spiral is the model with a cyclic form, and not a model called circular. The spiral model, the waterfall model and the iterative model are examples of models that do appear in textbooks.

Answer: A

Only statement i is true for the Waterfall Model. Because the model moves from one phase to the next in order, it works badly when issues are left unsolved at a previous step. Statement ii describes iterative or cyclic models, statement iii (consideration of risk) is a feature of the spiral model, and testing at each stage in a reverse manner (iv) is the V-model. So the options with ii, iii or iv are wrong. In the waterfall model the stages (requirements, design, coding, testing and maintenance) follow one another in a line, with little return to an earlier stage.

Answer: C

The aspect is the requirement - design - code - integrate cycle.

In continuous integration, developers integrate their work into a shared mainline frequently, often several times a day, and each integration is built and tested automatically. Every small piece of work therefore passes quickly through the full cycle of requirement, design, coding and integration, and errors are caught early rather than at a final 'big bang' integration.

The other options either leave out coding or design, or put coding before design, which is not the order of the cycle.

Answer: A

The factor is iterative and incremental development.

The Rational Unified Process divides a project into four phases, inception, elaboration, construction and transition, each carried out in a series of iterations. Every iteration passes through requirements, analysis, design, implementation and testing and adds a further increment of working software. RUP is also described as use-case driven and architecture-centric.

'Continuous' and 'validations' are not the terms in which the RUP framework is defined; validation happens within each iteration but is not its organising principle.