Ambiguous requirements

In the traditional model, assumption leads to confusion in making the end delivery. We assume that the customer will identify all requirements during the initial phase. Though it looks reasonable, the customer is not comfortable to sign off the process officially.

As an outcome, the customer gives a list of known and probable requirements during the initial phase of software development. It is just to avoid missing them in sign-off mode.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.22.74.66