Chapter 11 – Business Requirements Gathering




Chapter 11 – Non Functional Requirements

Having discussed the functional requirements in Chapter 10, we will now review the eight non-functional requirement types within Chapter 11. The non-functional requirements usually do not affect the functional requirements of the product. The non-functional requirements encompass the characteristics or properties of the product.  I will explain a few non-functional requirements below:

Look and Feel – This non-functional requirement captures the style, the visuals, the texture and the overall appearance of the product and the feeling/ emotion the developer wants to evoke from the user

Usability and Humanity Requirements – This non-functional requirement ensures that the design and development of the product takes into consideration the expectations and capabilities of the target market. The intention is to eliminate any possible issues the user may experience in using the product and ensures that the user experience is comfortable and user friendly.

Performance Requirements – This non-functional requirement captures all the activities the product should be able to do in its working/ functionality capacity. This may refer to storage capabilities, accuracy of output, reliability, accessibility, availability and overall ability to meet user expectations.

Operational and Environmental Requirements – This non-functional requirement describes the conditions under which the product is expected to be functioning at full capacity – the conditions/ situations which would lead to optimum operational capacity.

Maintainability and Support Requirements – This requirement describes the level of upkeep/ maintenance and developer support the product will need to ensure continuous functionality for the user.

Security Requirements – This non-functional requirement specifies the level of accessibility, privacy and integrity capabilities of the product.

Cultural Requirements – This requirement covers the local, cultural characteristics the product should have to fit the needs of the target market

Legal Requirements – This requirement refers to the compliance obligations of the product with local, national, international or environmental laws and regulations. The requirements may also extend to industry regulated standards or certification requirements in the sale and distribution of the product.

To determine the non-functional requirements, the relevant stakeholders must be involved in consultations.

Comments

  1. Kirandeep Kaur23 April 2020 at 14:01

    This chapter provides an information about the non-functional requirements that specify how well the product does and what it does. Functional requirements are those that cause the product to do the work while non-functional requirements are those that give character to the work. The security non-functional requirement give access confidentiality, recoverability and auditability of the product. Security requirements give protection to the product via access, privacy and integrity.
    Access: In access security requirement, product's data are only accessible to authorized users.
    Privacy: In privacy security requirement, product's data is protected from unauthorized users.
    Integrity: In integrity security requirement, product's data is protected from being corrupted.
    Except these three security requirements, there is another security requirement, Audit which means product allow complete verification of its operations and data

    ReplyDelete
  2. Sukhpreet Singh23 April 2020 at 14:11

    Non-functional requirements – In this there is specification of requirements that shows the quality of our product and its activity.
    An introduction to non-functional requirements- The non-functional requirements shows which features your product should have and how perfectly It do its work.
    Formality guide – If the product brings difficulties for the users in case of its usage or it is slow or risky, its performance is low, brings more chances for making of new product. The high-quality products are used in Rabbit projects, horse projects and elephant projects.

    ReplyDelete
  3. Karandeep singh23 April 2020 at 15:26

    Performance Requirements - 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. Everyone asks for a product with a quick response time, but the need for speed must be genuine. All too often, we want things to be done quickly when there is no real need to do so. If a task is to produce a monthly summary report, then there is probably no need to complete this job quickly. By contrast, the very success of the product may depend on speed.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 7 – Business Requirements Gathering

Chapter 7 –  Understanding the Real Problem This chapter focuses on the Business Analyst “thinking above the line” and focusing on the true essence of the business. This requires reviewing the Brown Cow Model – that is looking at the area above the line – the “ What Now ”. This section examines the undiluted and core reason for the business’ existence. The next step would be to look at the future of the business, called the “Future What”. Examining these two areas helps the Business Analyst get to the heart of the business problem, rather than focus on possible solutions. With the right focus the Business Analyst is not distracted by what others may think the solution could be, but the BA delves and trawls through as much information as possible to accurately understand the business and how it functions, minus technology or automation. This determination to channel all efforts towards the core purpose of the business allows the BA to be more open to all possible solutions...
Read more

Chapter 3 - Business Requirements Gathering

Chapter 3 - Scoping the Business Problem This chapter focuses on Project Blastoff Deliverables such as Project Purpose, Scope of work, Stakeholders, Constraints, Names, Estimated Cost and Risks. The chapter refers to Scope, Stakeholders and Purpose as the Trinity confirming that these are core elements of any successful project blastoff. ·          For Project Scope, we must understand the extent of the work to be done and how this task (business improvement) will impact the current operational environment and its existing products and services. We must ensure that we accurately document the depth and breadth of the project. ·          For Project Purpose, we must accurately capture the quantifiable/ measurable business benefit to be gained from the completion of the project. ·          For Stakeholders, we must document all possible persons with a vest...
Read more

Chapter 4 - BUSINESS USE CASES

Business use cases  -Business events are useful to partition the work, but it is the work’s response to the  event that now captures the interest of the requirements analyst. For every business event, there is a preplanned response to it, known as a business use case (BUC). Rabbit Projects - it is important to have a rock-solid grasp of the business problem to be solved. Rabbits make use of business use cases to explore their problem domain before starting to formulate a solution. This approach does not add to the documentation load, and it lessens the time spent delivering inappropriate solutions. Horse Projects - Horse projects are more strategic than rabbits. they need more time to complete. There is also the possibility of using Business use case scenarios as the documentation to pass along to the developers. Elephant Projects - elephant projects have a large number of stakeholders, clear communication is both important and difficult. Business ...
Read more