Requirements or Bug Database:

Requirements play a major role in developing software under a normal circumstance. Collecting Business, User and Functional requirements is the first activity that should be performed in the initial stage of the software development life cycle. Sometimes, the system engineer (or requirement collector) could not able to collect the complete requirements and due to which nothing can be planned in a proper way. The development team starts coding without having a complete knowledge of the design and consecutively test team have no proper documents to test the release.

In this type of scenario, most of the bugs found by the test team converted into the limitations and remaining bugs are being logged in the Bug tracking system. That is the reason I am saying that our bug database should not be our requirement document.

The point that one should ask from the development is that whatever mentioned in the release notes has been implemented in the release or whatever implemented in the release has been mentioned in the release notes. We should be very careful while answering this question as selecting any of the option against this question will definitely tell everyone what methodology you are following in your software life cycle. Is it a software engineering or a reverse software engineering?

-- Sanat Sharma