What can be done if requirements are changing continuously?
上一篇 /
下一篇 2010-05-14 12:47:20
/ 个人分类：FUNCTION TEST
And it is. One place where I worked was a web-based
company and things changed quickly so there was rarely a formal spec
done up. It was a boardroom meeting where the project lead or CEO, or
whomever, gave a presentation of what it would do. I would note the
requirements. Build them into test cases, and that's it. Beyond that, if
something changes, you adapt on the go. In an environment like this you
need to have a means of documenting changes effectively without bogging
down your process in paperwork. The fact is that if you were to
implement a very formal, traditional process, you would most likely fail
because you simply cannot keep up with the updates to the requirements.
Your concentration in these environments would be more on the testing
of the requirements as they stand at any given time, rather than trying
to record them and keep a detailed record of the change history.
收藏
举报
TAG:
