Chapter 11- Non-functional Requirements

What are the types of non-functional requirements?


Following are the non-functional requirement types we use and recommend. Each number is the identifier allocated to that type of requirement in the requirements specification template.

1. Look and Feel: the spirit of the product’s appearance
2. Usability and Humanity: the product’s ease of use, and any special considerations needed for a better user experience
3. Performance: how fast, how safe, how many, how available, and how accurate the functionality must be
4. Operational: the operating environment of the product, and any considerations that must be taken into account for this environment
5.Maintainability and Support: expected changes, and the time needed to make them; also specification of the support to be given to the product
6. Security: access, confidentiality, recoverability, and auditability of the product
7. Cultural and Political: special requirements that come about because of the culture and customs of people who can come in contact with the product
8. Legal: the laws and standards that apply to the product

USE CASES AND NON-FUNCTIONAL REQUIREMENTS

 A product use case represents a chunk of work the product does when the work is responding to a business event. In earlier chapters, you saw how the scenario breaks the product use case into a number of steps; for each of these steps, you determine the functional requirements. The non-functional requirements, however, do not fit so neatly into this partitioning theme. Some of them can be linked directly to a functional requirement, some apply to the product use case as a whole, and some apply to the entire product. The links between the functionality and the associated non-functional requirements.
Non-functional requirements are properties that the functionality must have. The functionality can be represented either by a product use case or by its constituent functional requirements. In this example, the product use case has three functional requirements, each having some non-functional properties. The use case as a whole must meet certain usability requirements, whereas the look and feel requirements relate to the entire product.
ing are the non-functional requirement types we use and recom-
mend. Each number is the identifier allocated to that type of requirement in
the requirements specification templa
wing are the non-functional requirement types we use and recom-
mend. Each number is the identifier allocated to that type of requirement in
the requirements specification template.
wing are the non-functional requirement type-
mend. Each number is the identifier allocated to that type of requirement in
the requirements specification template.

Comments

  1. Harleen Virk2 December 2019 at 21:31

    Prototypes and Non-functional Requirements
    You can use prototypes to help drive out non-functional requirements. At requirements time, the prototype usually takes the form of a whiteboard sketch, a paper prototype, or some other quick-and-dirty mockup of what the product might be like. The intention here is not to design the product, but rather to ensure you have understood the needs by reverse-engineering the requirements from the prototype. In the case of the scheduling product use case, your stakeholders respond favorably to a sketch of a screen showing the roads to be treated in a glowing, cold blue color; the safe roads in green; and the treated roads in yellow. The engineers are delighted that they can see the topography of the district and the roads.

    ReplyDelete
  2. Kent Dela Cruz3 December 2019 at 18:46

    The Non – Functional Requirements are those which shows that how the product look like. Along with the functional, the non – functional requirements are equally important for the success criteria of a product. There is a checklist to list pot the non – functional requirements based on the product features and demands of the stakeholders.
    The devil is in the details. —Common proverb Nonfunctional Requirements Nonfunctional Requirements (NFRs) define system attributes such as security, reliability, performance, maintainability, scalability, and usability. They serve as constraints or restrictions on the design of the system across the different backlogs. They ensure the usability and effectiveness of the entire system. Failing to meet any one of them can result in systems that fail to satisfy internal business, user, or market needs, or that do not fulfill mandatory requirements imposed by regulatory or standards agencies.

    ReplyDelete
  3. Mariane3 December 2019 at 20:31

    Unlike functional requirements, non-functional requirements are qualities and constraints that are typically revisited as part of the Definition of Done (DoD) for each Iteration, Program Increment, or release.
    Proper definition and implementation is critical. If you over-specify them the solution may be too costly to be viable, if you under-specify them the system will be inadequate for use.
    Source: https://www.scaledagileframework.com/nonfunctional-requirements/
    Accessed on: Dec. 03, 2019

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 1 - What is Business Analysis?

Hello! Welcome to our Business Analysis blog.  We are Mariane, Harleen, Kent and Parminder, and we are Business Technology Management students at Red River College.  Throughout our Fall term we will be using this blog to share some important concepts regarding Business Analysis.  For our first post, we will start with the basics, and define exactly what is Business Analysis, and other important concepts related to it. According to BABOK, " Business analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders. Business analysis enables an enterprise to articulate needs and the rationale for change, and to design and describe solutions that can deliver value. "  Business analysis cannot work without having a representative to intermediate these practices within an enterprise. This professional is called a Business Analyst who is responsible for putting in practice the tasks desc...
Read more

Chapter-12 Fit Criteria and Rationale

Image
FORMALITY GUIDE Horse ventures need to have an exact and effectively shareable comprehension of the significance of necessities. It has been our experience that when the task has numerous partners—which is the standard for horse ventures—various partners relegate various implications to prerequisites. Including a reason and a fit basis to every necessity implies it is for all intents and purposes inconceivable for errors to happen. We prescribe that pony ventures incorporate both of these in their necessities. Elephant ventures must utilize methods of reasoning and fit criteria. These tasks are compelled to deliver a composed determination to be given on to some other gathering, either another piece of the association or an outsourcer. Having a detail containing just unambiguous, testable necessities is pivotal to elephant ventures on the off chance that the other party is to comprehend and, at that point convey the right item Scale of Measurement Any prerequisite can be ...
Read more

Chapter 5 - Investigating the Work

The starting point for any product that will be built is the owner's work.  The book mentions that business analysts go "trawling" after business requirements.  The first task in the business requirements gathering process is to understand and investigate the work that is being done. Once that's understood, then the "essence needs to be understood, that is the clean picture of the business, without technology.  In this chapter the "Brown Cow Model" is also introduced. Which is divided into 4 parts:  How-Now: shows the implementation of the work as it currently exists, including physical artifacts, people and processors to do the work.   What-Now: shows the real business policy (essence). No machines, people, or organizational departments. Future-What: shows the business as your owner wants to have it, but still with no technology applies to it. Future-How: shows the idealized future business policy, augmented with the technology and people ...
Read more