Back to 2015-proposals
Title: Design For Testability: What, Why and How
Proposer: Giovanni Asproni
Type: Tutorial
Duration: 90 mins
Description:
'To be tested a system has to be designed to be tested' Eberhardt Rechtin, 'The Art Of System Architecting'
Testing is one of the main activities through which we gather data to assess the quality of our software; this makes testability an important attribute of software - not only for development, but also for maintenance and bug fixing.
Design for testability is a term that has its origin in hardware design, where the concept was introduced in order to make it easier testing circuits while reducing the costs of doing so.
In this talk I'll show how to translate this concept to the software domain along with the consequences on various aspects of the development activities, both from the technical point of view (e.g., design, code quality, choice of frameworks, etc.), and the product management point of view (e.g., management of team dependencies, delivery time, costs, etc.). I'll provide examples based on real world experience, both for the technical and the management aspects.
2015:design_for_testability_-_what_why_and_how
2015/design_for_testability_-_what_why_and_how.txt · Last modified: 2016/06/11 14:05 by 127.0.0.1