what do u write in the impact analysis document (i.e, for a
change request)
Answers were Sorted based on User's Feedback
Answer / t narasimhulu
You need to write following sections in impact analysis
document.
1. CR description. <Explain briefly about the CR>
2. Implications of the proposed change: < Mention the
functionalities affected/changed due to this change.>
3. Functionalities to be tested. <List down the
functionalities need to test for this change>
3.1 New test cases <List down the new test cases created
for this change>
3.2 Existing Test cases <List down the existing test cases
available for the change>
4. Reference Documents. < Mention the reference documents:
Technical Specification doc, Functional Spec doc,
Screenshots and Filed list validating doc>
| Is This Answer Correct ? | 49 Yes | 3 No |
Answer / piyoosh srivastava
Impact Analysis should be done before we do any code changes
as per CR.
Impact analysis should contain(s)
- Change Feasibility
- Duration
- Area / Wrokflow would affected
- What if analysis
- Development and QC effort required
- New/Modify Use Case
- New functionality/Changed functionality
- Impact approval
- Ref Specs
| Is This Answer Correct ? | 22 Yes | 5 No |
Answer / pandu
Hi Srivastava your answer is correct but i had a
doubt 'where' the analysis document prepared,and "how" the
estimate the task. give me one example or is there any
snapshoot please send me.
Thanks,
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / senthil kumar m
you have to write whether the changes you made has been
working properly & it has not affected the previous flow of
the program.
| Is This Answer Correct ? | 13 Yes | 29 No |
Explain Introduction abt Ibm framework
how to change pic of variables declared in copy book inside progrm?
write a query to get RRN value from rpg?
How many types of evaluate statements are available?
what is the role of the is numeric clause?
How are composite and multiple indexes different?
Explain identify whether a call statement is a static or dynamic call?
GO TO stmt which of the following is not true A) GO TO stmt is not essential in the sense that it is possible to write programs without using GO TO B) The target of the GO TO stmt being a procedure name avoiding GO TO result in a program with no procedure name C) Indiscriminate use of GO TO stmt can make the control structure program substantially complex D) Too many GO TO stmts make a program difficult to understand
what is Retro fitting ?
how do u debug without using xpeditor ?
what optimum values can we find for freespace, ci etc?
Does qtp tool support mainframe application testing?