Interested to Buy Any Domain ? << Click Here >> for more details...
What can be done if requirements are changing continuously?
- 5 Answers
- 20621 Views
- Oracle, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
IF THE REQUIREMENTS ARE CHANGING OR CLIENT NOT HAVING THE
CLARITY ON REQUIREMENT, COMPANY WILL FOLLOW THE PROTOTYPE
MODEL, MEANS FIRST COMPANY WILL DEVELOP THE SAMPLE SOFTWARE,
THEN AFTER GETTING CLARITY ON REQUIREMENT, THEN THEY DEVELOP
FINAL SOFTWARE TO RELEASE.
IN THIS MODEL BUSINESS ANALYST WILL PREPARE PROTOTYPES FOR
CLIENT TO GET THE CLARITY ON REQUIREMENT.
| Is This Answer Correct ? | 12 Yes | 0 No |
If client requirements are chaging continuously, then below
changes are expected.
1. Change in design document or new design document HLD &
LLD
2. Change in test case scenarios
3. Change in test cases
4. Developer needs to write the code as per the change.
5. Tester needs to write new test cases
6. Tester needs to test the change.
7. In agile, work done in iteration can be affected.
8. Involves more cost.
| Is This Answer Correct ? | 9 Yes | 1 No |
Answer / sani
Test plan should be updated according to new requirements.Try to move new requirements to a 'New' version of an application, while using the original requirements for the 'Old' version.
| Is This Answer Correct ? | 3 Yes | 0 No |
Answer / mudaseer
in agile requirements keep changing so develop according to
the changing requirements
| Is This Answer Correct ? | 2 Yes | 1 No |
Answer / phu
When requirements are changing continuously, we prepare clearly and detail documents:
1/ Create a relationship document: display module/component relationship. When there are some changing, we can know affecting others.
2/ Calculate cost
3/ Backup or use source safe to keep track builds
4/ Update plans, schedules, designs, code, test cases
| Is This Answer Correct ? | 1 Yes | 1 No |
At what stage of the development cycle software errors are least costly to correct?
What is back to back testing?
Hi friends, Intw qs : 1.wat wil a tester do if the developer rejects or doesnt accept the bug u report. thou u try to shw the snap shots wat would b ur next step 2. wat are the quality factors ...explain Cost of quality 3. Wat is root cause analysis : Explain fisher model regds, swati
When are you done testing?
In my application there are 5 modules. In every module there are 8-9 sub-modules. Preview, Print & Download options are there on every sub-module screen. My Question is - Should I have to write that much test cases for Preview, Print & Download options???????? Please reply soon.
what is 'v'model?
What is a test strategy?
what is bugzilla?
Which is the better way to explain tipical bug life cycle?
Could Login Id field accept special characters?
Hi, Please tell how to write system test cases for between two modules. please ans real time expirience people... thanks in advance..
How we can test Cookies Manually?
Automation Testing 
