BR Chapter 12: Fit Criteria and Rationale
A satisfying viewpoint (among a large number) of Kent Beck's eXtreme Programming system is its emphasis on composing experiments before composing the code. The experiment characterizes the measuring stick that the executed code must match. The fit model is pretty much something very similar: It is a measuring stick for the necessity. By adding a fit rule to the necessity, you are, basically, composing its experiment.
In the event that you are utilizing client stories, at that point we firmly propose that you give specific consideration to the explanation given for the usefulness. This is pretty much equivalent to the justification, and is a significant supporter of winding up with the right item. Composing experiments on the back of the story card ought to accomplish a similar reason as the fit standard we talk about here. For each of the non-practical necessities yielded by the blog, we presently propose determining the fitting fit rule, affirming it with the partner, and composing the experiment utilizing that fit
paradigm.
Horse ventures need to have an exact and effectively shareable comprehension of the importance of necessities. It has been our experience that when the venture has different partners—which is the standard for horse ventures— various partners relegate various implications to prerequisites. Including a reason and a fit model to every necessity implies it is basically inconceivable for misconceptions to happen. We suggest that steed ventures incorporate both of these in their prerequisites.
Elephant ventures must utilize methods of reasoning and fit criteria. These undertakings are compelled to create a composed determination to be given on to some other party, either another piece of the association or an outsourcer. Having a detail containing just unambiguous, testable prerequisites is pivotal to elephant ventures in the event that the other party is to comprehend and, at that point convey the right item.
Reason that it needs a Criterion
When you have a requirement for the product to perform some function or to have some property, the testing activity must demonstrate that the product does, indeed, perform that function or possess the desired property. To carry out such tests, the requirement must have a benchmark such that the
testers can compare the delivered product with the original requirement.The benchmark is the fit criterion—a quantification of the requirement thatdemonstrates the standard the product must reach.
In the event that you are utilizing client stories, at that point we firmly propose that you give specific consideration to the explanation given for the usefulness. This is pretty much equivalent to the justification, and is a significant supporter of winding up with the right item. Composing experiments on the back of the story card ought to accomplish a similar reason as the fit standard we talk about here. For each of the non-practical necessities yielded by the blog, we presently propose determining the fitting fit rule, affirming it with the partner, and composing the experiment utilizing that fit
paradigm.
Horse ventures need to have an exact and effectively shareable comprehension of the importance of necessities. It has been our experience that when the venture has different partners—which is the standard for horse ventures— various partners relegate various implications to prerequisites. Including a reason and a fit model to every necessity implies it is basically inconceivable for misconceptions to happen. We suggest that steed ventures incorporate both of these in their prerequisites.
Elephant ventures must utilize methods of reasoning and fit criteria. These undertakings are compelled to create a composed determination to be given on to some other party, either another piece of the association or an outsourcer. Having a detail containing just unambiguous, testable prerequisites is pivotal to elephant ventures in the event that the other party is to comprehend and, at that point convey the right item.
Reason that it needs a Criterion
When you have a requirement for the product to perform some function or to have some property, the testing activity must demonstrate that the product does, indeed, perform that function or possess the desired property. To carry out such tests, the requirement must have a benchmark such that the
testers can compare the delivered product with the original requirement.The benchmark is the fit criterion—a quantification of the requirement thatdemonstrates the standard the product must reach.
Requirements tell us what the system should be able to do, but they do not offer any suggestions as to how its capabilities are realised. Interface design comes later. However, when the system is eventually implemented, we'll want to be able to check it, to see whether or not all the requirements that we so carefully wrote out have been satisfied. Therefore, when we write out a requirement, we also need to devise some objective test - called a Fit Criterion in the VOLERE jargon - that can be applied to the implementation and can tell us whether or not that requirement has been satisfied. If the application fulfils the requirement, the result of the test will be YES. If it does not, the result will be NO.
ReplyDeleteSo a Fit Criterion is a test. It isn't a specification of a function that users can perform, and it isn't a description of an interface component that fulfils the requirement. At least until you are familiar with the concept, you may find it helpful to start your Fit Criteria with the rather formulaic words, "The system fulfils this requirement if it ..."
So many people seem to have misunderstood this aspect of the Volere requirement shell that I've gone back to my notes to check that I didn't mislead you. But the notes are quite consistent with what I've written above. Here's what they say:
[a fit criterion] can be used as an objective test for whether the solution is a sufficient way of satisfying the requirement. It may be possible to apply the test before the solution is implemented, so that the proposed solution can be accepted or rejected before it is implemented, but the important thing is that the applying criterion will generate a clear yes/no answer. The solution will fulfill the requirement if it satisfies this criterion.
The rationale is the reason, or justification, for a requirement. We have found that attaching a rationale to the requirement makes it far easier to understand the real need. Quite often, stakeholders may tell you their perceived solution to the problem, rather than their real need. Alternatively, they may state a requirement that is so vague as to be (for the moment) unusable.
ReplyDeleteFit, as we use the term here, means a solution completely satisfies or matches the requirement. That is, the solution does exactly what the requirement says it must do or has the property the requirement says it must have—no more and no less. To test whether the solution fits the requirement, however, the requirement itself must be measurable. As a simple example, if the requirement calls for a length of rope “of a suitable size,” it is obviously impossible to test any delivered solutions.
ReplyDelete