Chapter 10: Functional Requirements ( Duy Anh Tran )

    1. The functional requirements describe the product’s processing—the things it has to do to support and enable the business.
    2. The functional requirements should be a complete and, as far as possible, unambiguous description of the product’s functionality.
    1. The functional requirements are derived from the product use cases.
      1. The most convenient way we have found to generate the functional requirements is to write a scenario that breaks the product use case into between three and ten steps.
      2. Examine each of the steps and ask, “What does the product have to do to accomplish this step?” The things that it does are the functional requirements.
    1. We suggest that you write these requirements (for the moment) using two components: a description and a rationale.
    2. When you have sufficient functional requirements to achieve the outcome of a product use case, it is time to move on to the next one. As you progress through these PUCs, you may discover that a requirement you defined for one PUC also applies to other PUCs. Reuse the requirement you have already written by cross-referencing it to all relevant product use cases.
    3. When all of the product use cases have been treated this way, you will have defined the requirements that completely and unambiguously specify the functionality of the product.

Comments

  1. Description and rationale are important factor of requirement because requirement need both what and why. The description points to the solution and Rationale makes the need visible and indicate that how much attention the requirement can get. Both these together lead to a clearer requirement.

    ReplyDelete

Post a Comment

Popular posts from this blog

Business Analysis

Successful BA

module 3