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
mSky
Member


Reged: 05/03/07
Posts: 125
Requirement coverage planning and measurement
      #632647 - 06/29/10 01:16 AM

Has anyone did anything for 'Procedure for requirement coverage planning and measurement'. To me, its a fancy way of saying how we measure requirement coverage, how do we know which requirements are a priority and which ones to put on the critical path. Has anyone worked on soemthing like that before? Any thoughts to share?

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


Reged: 07/01/10
Posts: 3
Re: Requirement coverage planning and measurement [Re: mSky]
      #635359 - 07/19/10 09:37 PM

HI MSKY

We can measure Requirement coverage by using Traceability Matrix, in that Matrix we map the Requirement ID VS Test case ID or Use case ID so that we will make confirm we covered the entire Requirement, Traceability Matrix does not mean we Tested 100% it only measures at-least all the requirement covered. and its easy way to measure the requirement coverage. pls let me know if any mistakes


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


Reged: 03/29/10
Posts: 83
Loc: India
Re: Requirement coverage planning and measurement [Re: mSky]
      #660647 - 02/15/11 07:18 AM

Quote:

how do we know which requirements are a priority and which ones to put on the critical path.




We "normally" follow a risk assesment sheet.
The sheet is a dynamic document and inputs are solicited from multiple stakeholders across the project lifecycle!

--------------------
Regards
Gaurav Pandey
http://www.gauravpandey.co.in/


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


Reged: 11/18/10
Posts: 37
Re: Requirement coverage planning and measurement [Re: GauravPandey]
      #661289 - 02/21/11 01:51 AM

If we go step wise -

1. Take the input from the client
2. Form a complete picture
3. If picture is not clear then find the loop holes in it and patch it up
4. Make a requirements document and enter all the input gathered
5. Based on the major and imp requests of the client requirements become high priority ones.
6. Put them all with ID for each minute requirement in a document and then proceed

If these steps are gone then it will be difficult to patch them later.

--------------------
http://test-givethebest.blogspot.com


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


Reged: 04/12/10
Posts: 17
Loc: Shanghai China
Re: Requirement coverage planning and measurement [Re: Joshna_Samala]
      #663553 - 03/09/11 01:10 AM

follow the requirement.

basic function is the most impotent. Then requirement details.


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


Reged: 04/13/12
Posts: 3
Re: Requirement coverage planning and measurement [Re: mSky]
      #704179 - 04/13/12 06:19 AM

Requirement Coverage can be achieved for functional requirements , if requirements are approved formally by the customer. This can be achieved by maintaining a bi-directional traceability matrix (Vertical Traceability covering dependent requirements and Horizontal traceability covering design, coding and testing artifacts). But this is difficult in projects where requirement change due to changing business requirements of the customer.

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



Extra information
0 registered and 7 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: 7090

Rate this topic

Jump to

Contact Us | Privacy statement SQAForums

Powered by UBB.threads™ 6.5.5