Chapter 11

-

Chapter 11 - Non-functional Requirements

Q-1 What are Non-functional requirements?
Ans: Non-functional requirement specifies the quality attribute of a software system. They judge the software system based on Responsiveness, Usability, Security, Portability and other non-functional standards that are critical to the success of the software system. Example of non-functional requirement is, "How fast does the website load?". Failing to meet non-functional requirements can result in systems that fail to satisfy user needs.

Q-2 What is the difference between Functional and Non-functional requirements?
Ans: Functional requirements define what a system is supposed to do and non-functional requirements define how a system is supposed to be. Functional requirements along with requirement analysis help identify missing requirements while the advantage of non-functional requirement is that it helps you to ensure good user experience and ease of operating the software. A functional requirement for an everyday object like a cup would be: "ability to contain tea or coffee without leaking" while the non-functional requirement for the same example would be: "contain hot liquid without heating up to more than 45°C"

Q-3 What are the Non-functional requirements Types?
Ans: Following are the non-functional requirements types which are grouped into eight major categories:
  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
Q-4 Mention the aspects of Security Requirements Type.
Ans: When you write security requirements, considering the nature of security is important. Security have four main aspects:
  1. Access: The product’s data and functionality are accessible to authorized users and can be produced in a timely manner. Other access requirements focus on denying access to unauthorized people.  
  2. Privacy: Data stored by the product is protected from unauthorized or accidental disclosure. 
  3. Integrity: The product’s data is the same as the source, or authority, of the data, and is protected from corruption. 
  4. Audit: what the product has to do to allow complete verification of its operations and data. 
Q-5 How do we find Non-functional requirements?
Ans: The following things can prove useful in the process of finding out non-functional requirements:
  1. Blogging the requirements: Starting a blog using the template’s non-functional sections and subsections as headings can be useful in finding non-functional requirements. To elaborate, instead of writing “Usability Requirements,” instead use the subsections “Ease of Use,” “Personalization and Internationalization,” and “Accessibility.” 
  2. Use cases: Considering each use case scenario from the point of its non-functional needs can help you identify non-functional requirements.  For each of the non-functional requirements types, interview these stakeholders about the product’s needs. 
  3. Templates: Using the template as a checklist of non-functional requirement types when interviewing your stakeholders is another way of finding non-functional requirements. Deeply studying the template that is looking at each of the subtypes and probe for examples of each.
  4. Prototypes: Prototypes can be used to help drive out non-functional requirements. Going through the prototype carefully, and keep in mind that it is not the requirement, but rather a simulation of the requirement. Example of prototype- whiteboard sketch, a paper prototype.
  5. Clients: The client for the product may also have expectations that are relevant here. Your client may say that if you cannot provide an interactive and graphic display of the current trading position, then he does not want the product. Thus, your client becomes the prime source of the critical non-functional requirements. 

Comments

  1. Balpreet SinghApril 22, 2020 at 8:08 PM

    The operational and environmental requirement is mainly specify what the product has to do if it is implement and operate properly in its environment. In some cases the environment in which the product is operated have creates some special circumstances that have a huge effect on the way the product is constructed. So it is very necessary for the developers to keep in mind the operational requirement of the product where it will be operated while designing the product or gathering the functional and non-functional requirement for the product because otherwise the product will fail when it is operated. For example :- The product shall be used in and around trucks at night and during rainstorms, snow, and freezing conditions. So the environmental conditions need to consider mentioned in this requirement while designing this product.

    ReplyDelete
  2. Shaina LuthraApril 22, 2020 at 10:39 PM

    Performance requirements are written when your product needs to perform some tasks in a given amount of time, some tasks need to be done to a specific level of accuracy, or the product needs to have certain data storage capacity, or it has to achieve a certain volume of throughput. Performance requirements include the risk of damage to people or property. When you are thinking about performance requirements, consider aspects such as :
    ● Speed to complete a task
    ● 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
    ● 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

    ReplyDelete
  3. Kim LeApril 23, 2020 at 9:57 AM

    Sometimes, non-functional requirements are disregarded or underestimated, which may lead to the failure of a project. This is the reason why non-functional requirements are also an important part of gathering and analyzing requirements stage. In order to determine what the non-functional requirements, business analysts should comprehend different types of non-functional requirements. To support defining non-functional requirements, business analysts are expected to be familiar with the techniques of capturing non-functional requirements. Having concrete and clear non-functional requirements is one of the keys to a project's success.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 8: Starting the Solution

-
Chapter 8: Starting the Solution Question 1. What is a persona and when is it used? Answer: A persona is a virtual character that represents a large number of customers (or users) with similar characteristics or demographics. Personas are constructed from data collected through surveys of your target audience and so represent most of your eventual users. It is important that you construct your persona with enough characteristics for you and your team to feel that they understand it well enough to know what it wants.  Personas are used when you have a large number of in-house users, or a large number of customers who will be using the product. The business analysts and designers use a persona as their source of user specific requirements. Question 2. What do you mean by "Designing the User Experience" ? Answer: Designing the whole of the user experience is the best way to come up with a product that makes people want to buy it and/or use it. Experience de...
Read more

Chapter 7 Understanding the right Problem

-
Image
Chapter 7 Understanding the right Problem Question 1. What the brown cow model does? Answer The brown cow model is all about the number of ways (viewpoints) in which we can look at the work area, when we are investigating work area. In brown cow model there are four quadrants namely- How Now, What Now, Future what, How Future.   How Now is the place to start in most of the times and it shows the implementation of the work as it currently exists. Which includes physical artifacts, people that are used to do the work.   What Now shows the real business policy or the essence of the work. Future What shows the business as your owner want to have it in the future but still with technical neutrality that being used to implement that business. Future How shows the future business policy with the use of technology that being used to implement it. Question 2.   What are persons and how it is useful? Answer ...
Read more

CHAPTER 12: FIT CRITERIA AND RATIONALE

-
CHAPTER 12: FIT CRITERIA AND RATIONALE What are fit criteria and the rationale of a requirement? There are some differences between the fit criteria of functional and non-functional requirements. The fit criteria of functional requirements determine how business analysts will realize that the product has effectively accomplished that activity. For functional requirements, it is hardly possible to decide the scales of measurement: The action is either finished or not finished. Completion relies upon satisfying an authority that the product has correctly performed the action. The authority mentioned can be the source of the information or the nearby system that commenced the action. Business analysts can write functional requirements for various types of action. The fit criteria of non-functional requirements is a measure of those qualities such as usability, look and feel, performance, operational, and so on. In the first place, some of the nonfunctional requirements may appear ...
Read more