CHAPTER 11 - Non-Functional Requirements

By -
Non-Functional Requirement Types

 Major non-functional requirement types, and within those, subtypes or variations on the type are divided into eight types.is nothing sacrosanct about the classes we have allocated to the non-utilitarian necessities; don't hesitate to make your own. We appointed classes since we have discovered that having an agenda of necessities types makes it simpler to find every one of them.

These are:-

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

 This would show that you have a few prerequisites posing as one, or that you have one of those normal requirements that are simply too hard to even consider categorizing. On the off chance that this troubles you, at that point you can give a prerequisite different sorts. something else to remember as you experience the different non-functional prerequisites: For the occasion, we are managing the description and reason of the necessity. A portion of the models we give may appear to be somewhat dubious, questionable, or inexactly worded. The strategy for assault is to at first catch the partner's goal for the prerequisite.

Reference - Business Requirement Textbook

Comments

  1. Rajdeep SinghDecember 3, 2019 at 6:28 PM

    Look and Feel Requirement: Type 10

    Look and feel requirements describe the intended spirit, the mood, the style
    of the product’s appearance. These requirements specify the intention of the
    appearance, and are not a detailed design of an interface.
    This requirement does not say the company logo must occupy 10 percent of the
    screen, nor does it talk about the colors or the typefaces to be used. It simply
    states that the product must comply with the branding standards your organization
    has established. These standards are published elsewhere, your own
    organization has a department (usually the communications department) or
    group responsible for these standards—and the designer has access to them.

    (Mastering Requirements Process, pg.251)

    ReplyDelete
  2. NoorDecember 3, 2019 at 7:22 PM

    Usability and Humanity Requirements: -Type 11

    Usability requirements are often left out of the requirements specification on the assumption that no programmer would build a product that is hard to use. At the same time, the product's usability might be one of the key factors that determine whether the intended users actually use it. Do not make the mistake of assuming the product will be usable what is usable to one person could be useless to another. Instead, write the product's usability requirements in a highly specific manner.

    The usability and humanity requirements make the product conform to the user's abilities and expectations of the usage experience. The usability requirements ensure that you make a successful product for them. It affects productivity, efficiency, error rates, and acceptance of the new product.

    A designer would be hard pressed to understand exactly what kind of product you want to build. Thus, later you must add a measurement so the designer and the client have the identical understanding of "easy to use." Simply imagine how you would quantify the requirement for a product to be "easy to use."

    "Easy to use" and "easy to learn" are slightly different characteristics. Easy-to-use products are designed to facilitate an ongoing efficiency, so perhaps some training is to be done before using the product. For example, if you were specifying a product to be used in an office by office workers, you would be well advised to make it easy to use. Even if meeting this requirement means training people to use the product, the ongoing efficiency will pay for this extra effort many times over.

    Usability requirements can cover areas such as the following:
    o Rate of acceptance or adoption by the users.
    o Productivity gained as a result of the product's introduction.
    o Error rates.
    o Use by people who do not speak English Personalization and internationalization to allow users to change to local spelling, currency, and other preferences.
    o Accessibility to handicapped people.
    o Use by people with no previous experience with computers.


    ReplyDelete
  3. Arshpreet Singh PahwaDecember 4, 2019 at 3:44 PM

    Maintainability and Support Requirements: Type 14
    Usually at requirements time you do not know exactly how much maintenance
    your product will undergo in its lifetime, nor do you always know
    which type of maintenance it will need. Nevertheless, maintenance can,
    to some extent, be foreseen for certain products. Consider whether any
    expected changes will occur in the following areas:
    ● Organization
    ● Environment
    ● Laws that apply to the product
    ● Business rules
    Might other factors affect your product? If you know or strongly suspect
    that the product will undergo relatively heavy maintenance due to expected
    changes, then specify the types of expected changes and the amount of time
    allowed for those changes.

    This requirement had a major effect on the product’s designers. They
    designed the interface in such a way as to make it easy to add new languages.
    Also, they took into account the fact that different languages sometimes
    mean different cultures and different ways of presenting data.
    Support requirements are also covered in this section of the requirements
    specification. In some cases, your client may indicate that the product will
    be supported by the existing help desk; in other cases, the product must be
    entirely self-supporting. By making this point clear at requirements time,
    you ensure that the designer builds in the appropriate mechanisms for contacting
    the help desk, or providing answers for questions likely to arise with
    usage.

    ReplyDelete

Post a Comment

Popular posts from this blog

Underlying competencies

By -
Chapter 9 For being a business analyst, one should have the knowledge of the business in which industry the business is running along. Knowledge should be diversified. From organization to the methodology, to perform the business analysis tasks, such details work as an asset and helps in tackling the challenges. To decide and plan out the strategies, you require the measure the effectiveness of the ability of the organization, till what limits an the organization take risks in order to grab all the opportunities. Particularly, industry knowledge provide the understanding of the current processes. It shows the current trends, market forces, key processes, top suppliers, trending products. When developing the organization, you need to know where does the company stand in the industry. Market is always dynamic, it changes from time to time, and this is a key factor which affect the business process. Organizational knowledge allows the analyst to apply changes in the organization as...
Read more

Chapter 4-Business Use cases

By -
In the event that we have some methodical and detectable method for apportioning the work, at that point we are unmistakably bound to be steady with the outcomes we get. We go to business occasions as our favored method for dividing. The reactions to the business occasions—we call these business use cases (BUCs)— meet the accompanying criteria: ● They are "characteristic" parcels—everyone makes a conspicuous and intelligent commitment to the work. ● They have insignificant availability to different pieces of the work.   ● They have a plainly characterized extension.   ● They have rules for characterizing their extension.   ● They have limits that can be watched and characterized. ● They can be named utilizing names that are unmistakable to partners. ● Their reality can be promptly decided.   ● They have at least one partners who are specialists for that piece of the work. Before we inspect business use cases, we should take a look at h...
Read more

Core Concepts in Business Planning

By -
Chapter 3 Change - It is the transformation of company protocols in response to the need. Skip the Dishes change their app on the regular basis. Every month they release 2 to 3 major updates tot he app. Need - There is always a need to change several things in a business to cope up with the changing world. In addition to that, whenever there is an entry of competition we need to change several business processes. Solution - Business analyst is the one who is responsible to provide analysis that whether the successful implementation of the solution is possible or not. Stakeholder - It is a group or individual with a relationship to the change, the need, or the solution. Business Analyst perform a stakeholder analysis to ensure planning and monitoring activities reflect stakeholder needs and account for stakeholder characteristics. Value - the worth, importance, or usefulness of something to a stakeholder within a context. Business Analyst conduct performance analysis to e...
Read more