1 / 11

Process Improvement

Process Improvement. Improving the Test Process. In the Software V&V course, Prof. Uwe asked the question:. How to improve the Testing Process?. Improving the Test Process (2). Some answers: Develop a test strategy Use Guidance such as: checklists guidelines templates

Pat_Xavi
Télécharger la présentation

Process Improvement

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Process Improvement

  2. Improving the Test Process In the Software V&V course, Prof. Uwe asked the question: How to improve the Testing Process?

  3. Improving the Test Process (2) Some answers: • Develop a test strategy • Use Guidance such as: • checklists • guidelines • templates • Improve communication >> How to improve communication? • Learn from past experience >> How to consistently learn from the past?

  4. How to Improve Communication? Review: • Request a review of the testing plan • Don't wait for a request Benefits of Review • Improves understanding between members • Team members learn from each other (knowledge transfer) • Improve motivation & sense of participation • Chance to involve senior developers who don't have time to involve directly in testing

  5. What is a Review?

  6. How to Conduct a Review

  7. Inspection • Systematic approach to examining a program (work product) in detail • Goal is to assess the quality of the software product • not the quality of the process • ensure program is correct • verify coding standard

  8. Handling complexity • Use divide and conquer • Examine small parts

  9. Three techniques • checklist Problems with Checklists: • questions too general • instruction missing • detection biased towards previous defects

  10. Three techniques • Use cases • check that each object is capable of responding correctly to all scenarios • forces the inspector to consider the context in which an object is used • interaction diagram is useful • create scenarios • ...

  11. Three Techniques • Abstraction driven • start with least dependent class • create a natural language abstraction for each part (method) • analyze interdependencies between classes • analyze dependencies between methods • reverse engineer an abstract spec for each method

More Related