Chapter - 12 Fit Criteria and Rationale

 Fit Criteria and Rationale

Fit Criteria : 

"Fit" means implies an answer totally fulfills or matches the business requirement and "Criteria" means a principle by which someone may be judged. The fit criteria is effectively implemented as a result. It is important because it  exhibits how estimating a prerequisite make it reasonable and testable.

Why does fit need a criteria : 

1. It needs a benchmark as an analyzer.

2.  "The idea is for each requirement to have a quality measure that makes it possible to divide all solutions to the requirement into two classes: those for which we agree that they fit the requirement and those for which we agree that they do not fit the requirement."

3. At the point when a business requirement for the item is to complete some capacity, the testing activity of the work must demonstrate the product plays out that function.

Scale of Measurement :

The scale of measurement is a classification that describes the nature of the information within the values assigned to variables. It is hardest part of the testing process.

Application of fit criteria :

A fit measure can be utilized as a target test for whether the arrangement is an adequate method for fulfilling the necessity. Fit criteria create a final answer in yes or no. Fit criteria is a real business requirement. We can drive a fit criteria by examining the requirement's rational, description and figure out which measurement best communicates the client's exception fro the necessity. 

(Ramandeep kaur)

Chapter - 11 Non Functional Requirements

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. These are:

·       Look and Feel Requirements (Type 10)

·       Usability and Humanity Requirements (Type 11)

·       Performance Requirements (Type 12)

·       Operational and Environmental Requirements (Type 13)

·       Maintainability and Support Requirements (Type 14)

·       Security Requirements (Type 15)

·       Cultural Requirements (Type 16)

·       Legal Requirements (Type 17)

Chapter - 10 Functional Requirements

Functional Requirements 

Functional requirements  determine what the item should do to fulfill the essential purposes behind its existence. In a simple way we can say that functional requirements of any project describe the system behavior under various conditions. Requirement are known as contract of building the product. 

Key factors of functional requirements:

* Purpose of the Document 

* Business Processes

* Scope of the Product

* Use Cases

* Work Breakdown Structure 

* Functional Requirements 

Level of details for functional requirements:

* Should be single active sentence

* Use "and" wisely, use separate sentence to indicate the priority of requirement

* Use of similar words can result in confusion

* Must be measurable

* Use 'must' for critical requirements and 'should' for non-critical requirements

(Ramandeep kaur)

Chapter 8: Starting a solution

* Optimal response for a future product should include:

-          Most VALUABLE service from the outsider’s view

-          Lowest COST from the organization’s view

-          Most PLEASING AND ENCOURAGING manner from user’s view

-> BA should consider the boundary or scope to produce the optimal response

(Tam Dinh)

Scenario Templates

Difference between Alternatives and Exceptions in the Scenario Template?

Alternatives are the acceptable variations in the process which won't affect the project outcomes and they are optional features involved in a project. For example: When withdrawing cash from an ATM machine, getting the receipt is the alternative available to the user. The user can deny or accept the option to obtain the receipt and that decision won't have any effect on the final outcome, which in this case is receiving the cash.

Exceptions refer to the unwanted result in the process. This has an effect on the final outcome and even a single exception has the potential to change the final result of the project. For example: When withdrawing cash from ATM, if cash gets stuck in the ATM this would be considered as an exception. This has the potential to change the final outcome which in this case is user failed to receive cash.

Written by Pavandeep Singh Boparai

Chapter 7 - Six Thinking hats

How six thinking hats can help Business Analyst to determine requirements?

There are six different thinking hats which can help each Business Analysts as follows:

White Hat: With white hat business analyst analyze available data and analyze the past trends and tailor it to the project they are currently working.

Red Hat: In Red Hat, Business Analyst look upon their problems in the project and they compare how others could have reacted to that problem and how they can manage that situation.

Black Hat: In the black hat, negative outcomes of their decisions are looked upon and they can create a risk management plan to avoid that situation. This helps them to prepare for potential risks involved in the project.

Yellow Hat: This is completely inverse of black hat and in this one can look upon all the possible benefits from their decision and it can help business analysts to keep going when something is going difficult.

Green Hat: In this Business Analysts develop creative solutions to a problem and it is really beneficial when the decision of Business Analyst is criticized and it encourages them to come up with creative solutions to a particular problem.

Blue Hat: This represents process control and this can be used by Business Analysts when something is going wrong and they can direct activity into Green Hat thinking

Written by Pavandeep Singh Boparai

Chapter 6 - Brown Cow model

What is a brown cow model and what does Brown Cow model do?

The brown cow model takes four views of work separated by how and what also by now and future.

How now: In this model, the implementation of work is described including physical artifacts, people and processors used to do work.

What now: This abstract depicts the real business policy or the essence of work. This quadrant shows the business as if no machines, people and organizational departments existed. This helps business to understand what the current business model is doing.

Future what: This view shows the business how it will be after the change and but still without the technology that might be used to implement that business. In this, the business analyst can discuss with stakeholders precisely what the owner would like to do without worrying about how technology might do it.

Future how: In this quadrant, the idealized future view of business policy is augmented with technology and people needed to bring it into the real world.

Written by Pavandeep Singh Boparai