The online community for software testing & quality assurance professionals
 
 
Calendar   Today's Topics
Sponsors:




Lost Password?

Home
BetaSoft
Blogs
Jobs
Training
News
Links
Downloads



Quality Engineering >> Requirements and Design

Pages: 1
Winu
Newbie


Reged: 07/28/11
Posts: 12
Requirements review and analysis
      #694567 - 12/30/11 01:32 AM


Whats the difference between requirements review and analysis?

Thanks
Winu


Post Extras: Print Post   Remind Me!   Notify Moderator  
Joe Strazzere
Moderator


Reged: 05/15/00
Posts: 12344
Loc: Massachusetts, USA
Re: Requirements review and analysis [Re: Winu]
      #694572 - 12/30/11 05:30 AM

Did you mean - what's the difference between "Requirements Review" and "Requirements Analysis"?

--------------------
- Joe
Visit AllThingsQuality.com to learn more about quality, testing, and QA!

I speak only for me. I do not speak for my employer, nor for anyone else.


Post Extras: Print Post   Remind Me!   Notify Moderator  
mbalajiwale
Member


Reged: 07/29/11
Posts: 60
Re: Requirements review and analysis [Re: Joe Strazzere]
      #694625 - 01/01/12 11:45 PM

If your question is to differentiate between Requirement Review and Requirement Analysis then, as a result of review of requirement, decision is taken to go ahead with these requirements or not. This is normally done by the Leads (both development and QA) or BAs.

As a result of requirement analysis, which should be done by developers and QA analysts to understand the reviewed requirements and come up with POC, understanding document, test strategy for the product to be developed and tested.

--------------------
_____________________
Regards,
mbalajiwale


Post Extras: Print Post   Remind Me!   Notify Moderator  
Alby_George
Newbie


Reged: 04/13/12
Posts: 3
Re: Requirements review and analysis [Re: mbalajiwale]
      #704176 - 04/13/12 05:50 AM

To explain this, let me get your attention to the requirement process.Initially the BSG team (Business Analysts) conducts meeting, workshops, interviews, etc with customer to collect requirements. Now these gathered requirements might be conflicting to each other in an application due to architectural / implementation constraints. An analysis of these scope items is described as Requirement Analysis. After Analysis you creates the solution document, which describes the requirement in detail. Review of this document is called Requirement Review ( review can be a group review internal to the project or a review with customer to finalize on the requirements)

Post Extras: Print Post   Remind Me!   Notify Moderator  
Pages: 1



Extra information
0 registered and 4 anonymous users are browsing this forum.

Moderator:  blueinatl, swt88, AJ, Daniel_S 

Print Topic

Forum Permissions
      You cannot start new topics
      You cannot reply to topics
      HTML is disabled
      UBBCode is enabled

Rating:
Topic views: 3257

Rate this topic

Jump to

Contact Us | Privacy statement SQAForums

Powered by UBB.threads™ 6.5.5