Benefits of requirements traceability

 
 
 
 
 
Download PDF FREE
Value This
Doc
Scribd
Average
     
Pages: 37 43
Words: 1398 13640
Characters: 9566 81678
Lines: 268 623
     
     
Letters per word: 6.84 5.99
Words per line: 5.22 21.89
Words per page: 37.78 317.21

Add to your reading list

Flag_red Flag this document

Document Information

1,048 Reads | 0 Comments

Description

What happens when a requirement is modified?
Is impact analysis done (code, tests, design)?
Are modifications correctly pursued?
Sure?

What happens when a behavior evolution is submitted?
How to estimate the work to be done? Code, Spec,
Design documents, Tests

How to know if the tests covers all the requirements?
How to guarantee that the delivered product (provider) corresponds to the requested one (customer)
What happens when a bug is detected?
How to trace the code related to the bug?
Is the Spec updated?
Are the tests updated?
Planning and management
How to measure the code progression?
How to estimate the charge for the “to be done” stuff?
How to estimate the “remaining work” after tests cycles?
How to manage non regression?
How to guarantee completeness?
How to avoid redundant requirements & data

Powerpoint_16x16 37 Pages


Date Added

02/12/2009

Category
Tags
Groups
Copyright

Attribution Non-commercial

More info »

 

or use Facebook Connect