INTRODUCTION TO SOFTWARE ENGINEERING
SOFTWARE PROCESS MODELS
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
Can distract focus from final product
|
|
|
Checks if product meets specification
|
|
|
Wasted time overproducing the product
|
|
|
Users may get attached to the product
|
Detailed explanation-1: -Reduced time and costs: Prototyping improves the quality of the specifications and requirements provided to customers. With prototyping, customers can anticipate higher costs, needed changes and potential project hurdles, and most importantly, potential end result disasters.
Detailed explanation-2: -Starting with a prototyping phase allows you to receive accurate feedback from stakeholders and end-users early on, minimizing confusion when it’s time to begin coding. Getting these answers and catching mistakes upfront is critical – they’ll only cost you more in the long run.
Detailed explanation-3: -Making high-fidelity prototypes can significantly reduce communication costs. And prototyping is more accurate and exquisite. However, the high fidelity means that you need to spend more time and development effort, and it will be more time-consuming when you need to make some adjustments.
Detailed explanation-4: -There are many great reasons to make prototypes and to include them early and often in your process, and the four main points I’ll cover are as follows: to understand, to communicate, to test and improve, and to advocate.