jayapal reddy

• Nov 2nd, 2006

 

requirements document consists of all the details regarding the s/w that will be developed.it contain all the features n functionalities that a s/w should contain.

lakshmikannan

• Feb 12th, 2007

 

hai!In requirement document contains customers specifications or functionalities what they need.

Sumanth

• Feb 13th, 2007

 

Create Tests:- Test Plan (Test Lead or Sr Tester)Test Case (Tester)Running Tests :-Test Case Execution Analysis the Test Results:-Analysis Test Case Execution Results whether Pass or FailError Report(Defect Tracking)Re-Testing(One?s the Issue Test Fixed by Developer)Thanks,Sumanth

andar777

 Profile Answers by andar777 

• Aug 30th, 2007

 

Requirements are a list of system behaviors that the users would like the system to execute.  It also understands the behavior of each user touch point as the data flows through the system. 

Before, system testing can take place the BA must have a well documented data flow process and documented functionality at each user touch point.  This is way I believe UML modling is the best way to go.  Each step in the process is documented and can be validated with the users to ensure the flow is correct.  Once the users have signed off on the use case, the developers have a roadmap.  However, it is the obligation of the BA to minimize table and index additions, if possible.  Also stay away from If, Then and Else statements, which at times result in Spaghetti code that result in system lock ups and crashes.

Eyaseen Mohamed

• Oct 10th, 2007

 

First we have to verify the Attributes in the Screen by referring with the High & Low Level Document...Then Check the Functionality and the Business Flow and it should exactly match with the Customer Requirement

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 21st, 2009

 

Requirements are the functional characteristics of a product that are required upon its release to a client or customers.  These requirements may be stipulated by a client external to your company, or they may come from member(s) of your company who have worked closely with customers to determine what they want. 

In most companies, the test team does not perform requirements gathering.  Hopefully, the requirements have already been gathered and documented before functional testing begins.  However, the test team reviews the documented requirements in order to produce their test cases. 

krantibaviskar

 Profile Answers by krantibaviskar Questions by krantibaviskar

• Aug 10th, 2010

 

Requirements are generally prepared by business analysts. It contains products functional requirements (What client wants exactly).
 Eg. For login page what is max & min length of user ID & password. Any special characters are allowed are not.etc. BA peoples gather this information by communicating with client & prepares a documents, called as FRD(functional Requirement Document)