SOFTWARE ENGINEERING

INTRODUCTION TO SOFTWARE ENGINEERING

SOFTWARE PROCESS MODELS

Question [CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
When should we not use waterfall model.
A
Product definition is stable
B
Project is short
C
Requirements are dynamic
D
Technology is well understood
Explanation: 

Detailed explanation-1: -The waterfall model is most commonly used in software engineering and product development, less often – in other projects and industries. Employ the waterfall model only if your project meets the following criteria: All the requirements are known, clear, and fixed. There are no ambiguous requirements.

Detailed explanation-2: -Costly And Inflexible One of the main disadvantages of the waterfall model is that once it’s structured with the relevant information, it’s practically impossible to make changes. Returning to a previous phase to make alterations is extremely difficult.

Detailed explanation-3: -Waterfall method does not emphasize client feedback, constant communication, and input midway through the development process. It is not suitable for projects where requirements are at a moderate to high risk of changing and needs agility.

There is 1 question to complete.