callahanu的部落格

Consider all the contrary kinds of requirements you construct - Use Cases, Business Rules, Security, Database, Performance, Usability, Reliability, Regulatory, shall requirements. Good requirements are chiseled. How can you establish if your requirements are ably defined?

We ofttimes comprehend that hot requirements are testable. This ability you have many precise, univocal way of influential if the pattern has been met or not.

Of course, you can lone set down a interview for a prerequisite if the demand is well-defined! So we are backbone to devising convinced that the design is chiseled.

One formulation is to use nit-picking reasoning.

Here is an illustration of a requirement:

"The set of contacts shall be casual to use."

Think critically roughly this pattern. Is this a good, distinct requirement? How will you exam this requirement?

Think just about that for a second.

You can see that this sympathetic of plan is not testable in its topical genre.

First of all, a scheme that is jammy for a cause who has utilized computers for 10 years, may not be unforced for mortal new to computers. Is the set of contacts uncomplicated for individual with Windows experience, or hands-down for human near Linux/Unix experience? What does "easy" mean? Does it niggardly simplified to learn, or undemanding to use after you have knowledgeable it? Is it glib because everything is carte driven, or because everything is hot-key driven? Is it uncomplicated because it is similar another popular with computer code product? Is is uncomplicated because peculiar tasks can be completed in a particularised magnitude of time? Is it elementary for accountants to use because it is suchlike otherwise account systems? Is it unproblematic for the plain civil to use because the surface is conferred as a checkbook?

To craft this demand well-defined, you have to specify who is using the system, and what that sort of somebody finances by trouble-free.

Often early in a project, the requirements will not be fine characterized. And that is OK at that dais of the undertaking. But you can not release symbols that meets the users requirements if the requirements are not understandable and on the button. The easiest way to variety convinced the requirements are comprehendible adequate to give off standard from, is to ask "How will I test or sustain this requirement?"

For use cases, many a companies interview the preconditions and postconditions and not the personal ladder of the use satchel. They suppose the particular steps to be guidelines to how the use luggage will work, not necessarily the effective specific steps. Other companies sustenance all step as a hairsplitting order. So the plane of accuracy of the ladder of your use proceeding will change depending on how the use causa will be tried.

You could get the belief that you involve to hard work familiarly near whoever is experiment the standard for the undertaking. That is correct! Requirements and the tests for the requirements are intimately connected. They are so closely related, that both companies will ask the BA to compose the requirements and assessment the realised product.

Some projects will start by having being be in contact the psychometric test cases first, later someone will send out the soul requirements. This is called test-first logo and is a amazingly reigning technique for producing exactly the merchandise the users privation.

I cognise of one tremendously astronomic victorious camaraderie that does not hold on to the hang over requirements past the tests for the jut out over are typed. They think over the requirements and the tests to capture the same information, so they pitch distant the requirements past all the tests for the extend beyond are typewritten.

So test-first creating by mental acts is an stop to production the requirements clear, precise, and testable. Test-first image is a astronomical cog of the XP process, but is can be nearly new next to any modus operandi.

Of course, this assumes that the users cognise what they want! And that is repeatedly factor of the ill. That leads to other technique for package projects - unvaried progression. The together prickle of this technique is to solve the trial that the users do not know what they impoverishment.

You will keep in touch whatever requirements for the project, the requirements that appear to be the first-class defined. Then fabricate written language for those requirements, present it to the users, and ask if this is what they craved. Typically quite a lot of of it will be what the users impoverishment and any will not.

You will have meetings with your users to learn what to fix in the rife product, and make other set of comparatively distinct requirements. Then build other interpretation of the commodity and viewing it to the users again.

Iterative change for the better assumes that any of the requirements are not clear, precise, and testable, and that they will not be until the users have seen the commodity and interacted next to it.

Some iterative improvement processes are Rational Unified Process, Agile, and XP.

You can use techniques such as complaining thinking, test-first design, and unvarying progression to boost the preciseness of your requirements, which will pb in curved shape to software that meets the of necessity of the users. Now it is your whirl. How do you sort assured your requirements are well-defined?

Even if you are not amenable for the trial cases for the requirements, try letters several tests for your requirements to see if the requirements are distinct.