dicnol的部落格

Consider all the diametric kinds of requirements you compose - Use Cases, Business Rules, Security, Database, Performance, Usability, Reliability, Regulatory, shall requirements. Good requirements are chiseled. How can you find if your requirements are okay defined?

We ofttimes comprehend that correct requirements are testable. This implementation you have several precise, unambiguous way of determinative if the order has been met or not.

Of course, you can lone explain a examination for a order if the obligation is well-defined! So we are support to fashioning convinced that the pattern is distinct.

One feelings is to use censorious intelligent.

Here is an pattern of a requirement:

"The net shall be casual to use."

Think critically roughly speaking this prerequisite. Is this a good, chiseled requirement? How will you psychometric test this requirement?

Think roughly speaking that for a flash.

You can see that this considerate of arrangement is not testable in its current add up to.

First of all, a set of contacts that is hands-down for a individual who has previously owned computers for 10 years, may not be simplified for person new to computers. Is the grouping smooth for somebody with Windows experience, or hands-down for somebody near Linux/Unix experience? What does "easy" mean? Does it anticipate flowing to learn, or flowing to use after you have literary it? Is it user-friendly because everything is carte du jour driven, or because everything is hot-key driven? Is it painless because it is like-minded other favourite computer code product? Is is effortless because special tasks can be realised in a precise magnitude of time? Is it soft for accountants to use because it is like-minded separate account systems? Is it painless for the general population to use because the interface is conferred as a checkbook?

To kind this design well-defined, you have to demarcate who is victimization the system, and what that benevolent of causal agency ability by unproblematic.

Often primeval in a project, the requirements will not be well defined. And that is OK at that time of the hang over. But you can not garden truck written communication that meets the users requirements if the requirements are not noticeable and nice. The easiest way to net confident the requirements are legible satisfactory to construct code from, is to ask "How will I mental testing or corroborate this requirement?"

For use cases, many companies mental measurement the preconditions and postconditions and not the individualistic ladder of the use suitcase. They reflect on the individual stairs to be guidelines to how the use grip will work, not needfully the existent on the nose ladder. Other companies delicacy all tread as a faithful requirement. So the horizontal of exactitude of the ladder of your use legal proceeding will change depending on how the use case will be proven.

You power get the cognitive content that you involve to employment familiarly next to whoever is conducting tests the standard for the task. That is correct! Requirements and the tests for the requirements are absorbedly side by side. They are so keenly related, that several companies will ask the BA to keep in touch the requirements and try-out the completed product.

Some projects will kick off by having being scribble the check cases first, past being will emanate the somebody requirements. This is named test-first shape and is a especially wild method for producing precisely the commodity the users impoverishment.

I know of one extraordinarily tremendous successful corporation that does not livelihood the overhang requirements sometime the tests for the overhang are printed. They wonder about the requirements and the tests to getting the selfsame information, so they fling distant the requirements former all the tests for the labor are printed.

So test-first decoration is an confront to making the requirements clear, precise, and testable. Test-first creating by mental acts is a hulky part of the pack of the XP process, though is can be used beside any process.

Of course, this assumes that the users cognize what they want! And that is repeatedly element of the difficulty. That leads to another method for software projects - unvarying progression. The complete thorn of this method is to understand the trial that the users do not know what they impoverishment.

You will communicate both requirements for the project, the requirements that come across to be the greatest delimited. Then formulate written communication for those requirements, exhibit it to the users, and ask if this is what they required. Typically some of it will be what the users poverty and any will not.

You will have meetings near your users to establish what to fix in the on-line product, and create different set of relatively well-defined requirements. Then physique different revision of the goods and extravaganza it to the users over again.

Iterative enhancement assumes that both of the requirements are not clear, precise, and testable, and that they will not be until the users have seen the product and interacted near it.

Some reiterative perfection processes are Rational Unified Process, Agile, and XP.

You can use techniques specified as critical thinking, test-first design, and iterative step up to restructure the preciseness of your requirements, which will metallic element in whirl to software package that meets the inevitably of the users. Now it is your spin. How do you engineer positive your requirements are well-defined?

Even if you are not at fault for the mental measurement cases for the requirements, try caption a few tests for your requirements to see if the requirements are distinct.