Julho 06
Prof. Ismael H. F. Santos                                                                 2
Active and Passive quality checks are both required…
… but moving to active is the direction to take
-Example: for trends, tracking stuff. For example mean time between a bug is fixed. Or number of tests. Or code reviews (active = pair programming or distributed pair programming when IDEs support it)
-Problem with passive quality is that you need to look at it for it to have any effect, whereas activate quality is always applied.
-Active quality very important when working within a team (distributed or not) to maintain consistency in quality
-Active quality is a way to increase project quality without requiring extra budget