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. Unknown7 December 2018 at 22:02

    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

Chapter 2: The Requirement Process ( Duy Anh Tran )

The Volere Requirements Process is the way to get you from the business problem all the way to atomic functional and non-functional requirements. Business Requirements are an essential part of project success and a key responsibility for the Business Analyst. A requirements something the product must do to support its owner's business, or a quality it must have to make it acceptable and attractive to the owner. A requirement exists because the type of product demands certain functions and qualities, or because the client asks for that requirement to be part of the delivered product. The most common objectives of the Business Requirements are: To gain agreement with stakeholders To provide a foundation to communicate to a technology service provider what the solution needs to do to satisfy the customer’s and business’ needs To describe what not how the customer/business needs will be met by the solution A key to complete and accurate requirements gathering i...
Read more
Some of the performance requirements the BA should consider: Speed to complete a task The accuracy of the results  Safety to the operator  Volumes of data to be held by the product  Ranges of allowable values  Throughput, such as the rate of transactions  The efficiency of resource usage  Reliability, often expressed as the mean time between failures  Availability—the uptime or time periods when users can access the product  Fault tolerance and robustness  Scalability of most of the above
Read more
Difference Between The Role of Sponsor And Customer The Customer will pay for the project’s product.  will give the products’ requirements and reap benefit from the product (usually long after the project is over).  may or may not be part of the Performing Organization. The Sponsor is usually part of the Performing Organization.  will decide how much funds will be used for the project. She/he will take budgetary decisions.  will appoint the Project Manager and provide necessary support to her/him.
Read more