Header Ads

  • Breaking News

    Some Risks from Inadequate Requirement Process

    Some Risks from Inadequate Requirement Process

    • It is cleared that the requirements play the most significant role in the software development process and the success and failure of a system depends to a large extent upon the quality of the requirement documents.

    Following is a list of some of the risks of adopting an inadequate requirement process:

    • Insufficient user involvement leads to unacceptable products.

    • If input from different types of user is not taken, the output is bound to lack in key functional areas, resulting in an unacceptable product.

    • Focusing on the needs of only certain users (stake holders) leads to dissatisfaction of customers.

    • Requirement creeping: Requirement creeping is one of the most significant factors in budget and time overruns.

    • It basically means identifying and adding new requirements to the list at some advanced stages of the software development process.

    • The following figure shows the relative cost of adding requirements at different stages.

    Ambiguous requirements lead to waste time and rework.

    • Ambiguity arises from the use of natural language. Because of the imprecise nature of the language, different readers interpret the statements differently.

    • Ambiguous requirements therefore result in misunderstandings and mismatched expectations, resulting in a wasted time and effort and an undesirable product.

    • Gold-plating by developers 

    Gold-plating refers to features are not present in the original requirement document.
    In fact they are not important for the end-user but the developer adds them anyway thinking that they would add value to the product.
    Since these features are outside the initial scope of the product, adding them will result in schedule and budget overruns.

    No comments