| || |
goal and scenario approaches in requirements engg
Hi would you guys tell me the differences between the goal based and scenario based approaches to requirements engineering. an example will also be more helpful..thxs
Re: goal and scenario approaches in requirements engg
Please provide some details about your definition of requirements engineering, and - then please specify the desired outcomes/outputs. That may help those who would provide you with guidance.
To me requirements engineering - at a very high level means doing the necessary work to assure that requirements are sufficiently refined and clearly understood so that people can design, develop, and test the product. And, that product is what the customer wanted after all negotiated refinements typical of a development life-cycle. And the customer is better off than they were prior to having this product. Theoretically, the designers/developers could go do their thing without ever talking to the gray and black box testers who are doing their thing in parallel. Without consideration to iterative development for a moment; when the designers/developers are done doing their thing, the gray and black box testers should theoretically be able to being testing with the correct tests.
How does your definition compare with my own?