It is your first day and there are no requirements, all that you have available is one document, how do you go about gathering requirements? and Describe a few reasons that a bug might not be fixed?
It is your first day and there are no requirements, all that you have available is one document, how do you go about gathering requirements? and Describe a few reasons that a bug might not be fixed?
From the doc, first try to understand what the project is all about. Then try to look into what modules it has and why and how they are divided into modules as such. Take the first module and find what is the IT work required to to be down that acomplishes the activities in that module. Those activities would be the requirements. Try to write down each such activity that the document is talking about.
A bug may NOT be fixed if:
Devs can't reproduce the bug,
Devs find it working as per the design,
Devs find it as per the enhancement request from the client,
Devs need more time to implement correct logic,
Devs need to resolve the dependent defect and then come back to the current bug...
Actually there can be many reason Y a bug may not be fixed...
Lack of WILL POWER has caused more failure than
lack of INTELLIGENCE or ABILITY.
-sutnarcha-
Posting Permissions
Reply With Quote