Chapter 12 - Fit Criteria and Rationale post by Paramjeet Kaur Toor

Look and Feel Requirements

These requirements are related to look, style or behaviour of any specific product and impression  the user gets when using that product. For example, it can be colour, size , design of product and how user feel about it such as impression user gets when using the product. The rationale for this requirement is either attachment to branding standards or a desire to enhance customer recognition. In addition, fit criterion will be specify target that is easily determine when you know the rationale.

Usability and Humanity Requirements

Usability and Humanity Requirements involve the experience of users when using the product. For example, users can find that product is easy to use or hard to use, able to use by certain kind of users only. So, all things are relate to user's experience about a product. We should specify a target for who will be going to use it the most as it can be specific age group or for people how have disabilities. So, these requirements are all depends upon usability of a product.

Performance Requirements

Performance requirements are quantitative as we use numbers to describe things like accuracy, speed, avaliability, capacity, reliability , scalability and some other characteristics of product. It suggest a measurable scale for the nature of performance. For example, response should be fast so that user do not have to wait so fit criterion will be that the respond time shall be not more than 0.7 seconds for 95% responses. As these requirements are quantified so these are straightforward to write good fit criterion.

Operational Requirements

These requirements specify the environment in which product will create. In some cases, product also used in adverse conditions.The fit criterion for  operational requirement is a quantification of the successful usage in the required environment.Operational conditions may also specify that the product will coexist with partner. In this case, fit criterion will cite  partner sepecification system or the way to interact  with the other partner.

Maintainability Requirements

Maintainability requirements involves the exceptions of maintenance of product . So, fit criteria for these are requirements are usually amount of time allow to make any changes to product and changes only make where these are excepted. Thus, these requirements are about to keep maintenance of product.

Security Requirements

These are requirements are related to security which is very important for developers. Security standard either specific to your organization or product but it is important to know the security standards and include them to fit criterion. These keep your product under specific security standards.



Comments

  1. Liliane Marino21 April 2020 at 21:09

    Very good information about no-functional requirements to be fit. We can include in this list the Cultural requirements that are subjective and more difficult to quantify. The fit criterion for these requirements is usually based on who will certify the product’s acceptability.

    ReplyDelete
  2. Chelsia Palta23 April 2020 at 09:23

    Thanks for providing with this useful information. In addition to security requirements it is very crucial to for the developers to maintain proper security standards. Proper security measures should be taken that are fit for an organization for example the banks contain all the personal and financial data of the customers. So, it is the responsibility of the bank to provide security to the data. The Bank needs to keep their security strong as the data can be hacked and leaked and can be used for criminal activities.

    ReplyDelete
  3. Hassan Kamara23 April 2020 at 21:04

    Thank you for this very useful post! prior to reading i didn't have much information on the different kinds of ways to measure the non-functional requirements using the fit criteria. I believe that the security requirement is the most important because if its not done correctly it can lead to the most negative repercussions which could include security breaches and other negative security related problems. Each item was explained very well in this fit criteria chapter blog.

    ReplyDelete
  4. Harvinder Singh24 April 2020 at 18:17

    The fit criterion for operational requirement is a quantification of the successful usage in the required environment.Operational conditions may also specify that the product will coexist with partner. The fit criterion for operational requirement is a quantification of the successful usage in the required environment.Operational conditions may also specify that the product will coexist with partner

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 8 - Starting the Solution by Harvinder Singh

  Chapter 8 Starting the Solution We are transferring from an abstract global to the physical international, from policy to technology, from problem to solution; from purpose to design: we have reached the closing quadrant of the Brown Cow Model, in which will be determined how we are going to enforce the essential business. With a solid know-how of the essence of the business, which means that the real trouble to be solved, it’s time to determine which components of that problem would advantage from being automated. The commercial enterprise analyst juggles many factors to determine the most appropriate product to build. Iterative Development Iterative development is a way of breaking down the software improvement of a large application into smaller chunks. In iterative development, feature code is designed, developed and examined in repeated cycles. With each iteration, additional functions may be designed, advanced and examined till there is a com...
Read more

Chapter 4- Business Use Cases - posted by Chelsia Palta

Understanding the Work  The product you intend to build must improve its owner’s work; it will be installed in the owner’s area of business and will do part of the work. It does not matter which kind of work it is commercial, scientific, embedded real-time, manual, or automated you always have to understand it before you can decide which kind of product will best help with it. Use Cases and Their Scope The term "use case" was coined by Ivar Jacobson back in 1987 as a way to describe an interaction between a system and a user of that system. Jacobson needed to break the system into smaller units, as he felt that object models were not scalable. Thus, to conquer the complexity and largeness of modern systems, he said it was first necessary to partition them into convenient chunks, and that these chunks should be based on the user’s view of the system. The Outside World Adjacent systems behave like any other systems: They contain processes and consume and/or...
Read more

Chapter 11 Non-Functional Requirements by Hassan

Non-Functional Requirements Non-Functional Requirements can be generalized as "what a product/system is supposed to be. these requirements tend to be qualities that the product should have and they should specify how well the product does what it does. the requirements should either make the product usable, fast, reliable, attractive or safe and they should describe the character/ the way the functions should behave. Look and Feel Requirements the look and feel requirements are key to the non-functional requirements and as a BA one must consider them for every project. These requirements can describe how a product/system's desired appearance, mood, spirit or overall style/ appearance. The look and feel requirements can further specify what the product/system intends to appear as and is not a detailed design of the product/system itself. The typical look and feel requirement should be simple to use, professional looking, attractive to its market, consistent with previ...
Read more