| |
171. How Will You Receive The Project Requirements?
Date Posted: 06/27/2012
Ans: The finalized SRS will be placed in a project repository and we will access from there.
|
| |
| |
172. What If You Don’t Have A Solution For One Of The Critical Bugs? Do You Stop Release?
Date Posted: 06/27/2012
It depends on what makes that bug critical. For example if application is not running on Firefox browser which is one of the basic requirement of the product, I will not stop release. Instead I add this in the release notes under the list of known issues. I give a work around to customers to use IE instead of Firefox. Otherwise if the issue is transferred money is not reaching to friend in a banking application. I prefer to postpone the release.
|
| |
| |
173. Can You Give An Example Of Unreachable Code?
Date Posted: 06/27/2012
Ans:
Age= 25
If Age<18
- - -
- - -
End if
In the above code if condition will never be reache
|
| |
| |
174. Should We Fix All The Bugs Before Release?
Date Posted: 06/27/2012
Not required. If sufficient time is available we fix all the bugs before release, else some low priority bugs can be postponed for the next release sometimes if a medium or high priority bugs doesn’t have a solution at present, that issue can be documented in release notes and the project can be released.
|
| |
| |
175. How Do You Say Review Was Successful?
Date Posted: 06/27/2012
Ans: If every reviewer prepares well before there review and provides good comments for improvement of the work product, we can say that review is successful.
|
| |
| |
176. What Is Release Note? What Is Your Contribution To Release Notes?
Date Posted: 06/27/2012
It is a document that is attached with the software we are releasing. It is also known as README file. I have contributed to update 3 sections of this document which were related to mu module. They are:
New fundamentals in current release
Issues resolved from previous release
Known issues of current release
|
| |
| |
177. What Is Your Responsibility As A Testing Team Member After Change Request Approval From CCB?
Date Posted: 06/27/2012
The testing team must go through the functional documents of the approved changes and rework on the test plan. We must also write or update the test cases corresponding to the changes.
|
| |
| |
178. How Did You Know That There Is Change In The Project?
Date Posted: 06/27/2012
We have an intranet site where all project related documents are stored in the same place there is change request links which consists of information of all proposed changes and approved changes. We can find all the changes through this intranet site.
|
| |
| |
179. At Which Phase Of SDLC Is The Change Management Process?
Date Posted: 06/27/2012
Change management process starts immediately after requirements are base lined.
|
| |
| |
180. What Is The Difference Between Project Metrics, Product Metrics And Process Metrics?
Date Posted: 06/27/2012
Product metrics: It describes the characteristics of the product such as size, compatibility, design features, performance and quality level.
Kilo lines of code
Defect detection rate
Project metrics: It describes the project team’s ability to perform the project execution examples
Productivity
Schedule
Number of developers and testers
Process metrics: It can be used to improve efficiency of an existing process used in software development and maintenance.
Defect detection percentage
Defect density
Time to fix the defect
|
| |
