Page 46 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Principles of Software Engineering

Notes 7. This effort is no different than if the iterations were …………………. serially
(a) assumption (b) working
(c) executed (d) None of these.

8. As pipelining is to be …………………. the stages must be carefully chosen
(a) model (b) employed

(c) executed (d) None of these.
9. This early feedback from the customer serves to drive the next …………………. in the
correct direction.

(a) working (b) iteration
(c) sequence (d) All of these.
10. The project control list guides the iteration steps and keeps track of …………………. that
must be done.
(a) all tasks (b) process

(c) requirements (d) All of these.
11. A popular variation of the …………………. is called rapid application development (RAD).
(a) model (b) prototyping model

(c) requirements (d) process model
12. …………………. is responsible for testing the code written during implementation phase.
(a) Testing phase (b) process testing

(c) Rapid testing (d) None of these.
13. The information from the design is …………………. rolled into prototype.
(a) rapidly (b) responsible

(c) feedback (d) None of these.
14. The Prototyping Model was ………………… on the assumption that it is often difficult to
know all of your requirements at the beginning of a project.
(a) developed (b) rolled
(c) rapid (d) All of these.
15. The iterative model is not without its share of ………………….

(a) developed pitfalls (b) potential pitfalls
(c) Rapid (d) All of these.

2.8 Summary

• The software process is a critical factor for delivering quality software systems, as it aims
to manage and transform the user need into a software product that meets this need.
• In contrast to software life cycle models, software process models often represent a
networked Sequence of activities, objects, transformations, and events.
• The Waterfall model is one of the most used models of 70’s. It was proposed as an
alternative to Build and Fix software development.

40 LOVELY PROFESSIONAL UNIVERSITY