Trazabilidad y Comunicación

Transcript

1. Trazabilidad y Comunicación 2016, Junio 28 by Gonzalo Miraballes - QA Lead
2. Agenda • Trazabilidad ◦ Presentación ◦ Discusión de su importancia • Comunicación ◦ Responsabilidad del QA • Presentación del estado de la comunidad • Brainstorming! ◦ Discusión de tópicos ◦ Priorización de propuestas
3. Trazabilidad TMMI “The ability to identify related items in documentation and software, such as requirements with associated tests.” Establece el concepto de trazabilidad en dos dimensiones, a nivel de plan de pruebas o a nivel de rastreo hacia componentes de software.
4. Trazabilidad (2) Horizontal traceability “The tracing of requirements for a test level through the layers of test documentation (e.g., test plan, test design specification, test case specification and test procedure specification or test script).” Vertical traceability “The tracing of requirements through the layers of development documentation to components.”
5. Trazabilidad (3) ISTQB - Foundations “[...] Establishing traceability for test conditions back to the specifications and requirements enables both effective impact analysis when requirements change, and determining requirements coverage for a set of tests.” Introduce el concepto de Test Configuration Management
6. Trazabilidad (4) Test Configuration Management “TCM involves: - All items of testware are identified, version controlled, tracked for changes, related to each other and related to development items (test objects) so that traceability can be maintained throughout the test process. - All identified documents and software items are referenced unambiguously in test documentation.”
7. Trazabilidad (5) IBM “Traceability is a technique that provides a relationship between different levels of requirements in the system. This technique helps you determine the origin of any requirement.”
8. Trazabilidad (6) “Traceability plays several important roles: - Verify that an implementation fulfills all requirements: Everything that the customer requested was implemented. - Verify that the application does only what was requested: Don't implement something that the customer never asked for. - Help with change management: when some requirements change, we want to know which test cases should be redone to test this change.”
9. Trazabilidad - Discutamos! • Errores por falta de trazas que hayan tenido? • En qué medida creen que se nos prepara para afrontarlos? • Cuales creen que son los beneficios de esta técnica? • En qué medida se aplica en su proyecto? • Se puede mejorar?
10. Comunicación ISTQB - Advanced (TM) “Test team communication primarily takes place by the following means: - Documentation of test products - test strategy, test plan, test cases, test summary reports, defect reports, etc. - Feedback provided on reviewed documents - requirements, functional specifications, use cases, component test documentation, etc. - Information gathering and dissemination - interaction with developers, other test team members, management, etc.”
11. Comunicación (2) ISTQB - Advanced (TM) • Professional • Objective • Effective “[...] Diplomacy and objectivity are required when providing feedback, particularly constructive feedback, on the work products of others. In addition, communication should be focused on achieving test objectives and on improving quality both in products and the processes used to produce the software systems.”
12. Comunicación (3) ISTQB - Advanced (TM) Inward communication “[...] Communicate effectively within the testing group to pass on news, instructions, changes in priorities and other standard information that is imparted in the normal process of testing.”
13. Comunicación - Discutamos! • Errores por falta de comunicación que hayan tenido? • En qué medida creen que se promueve la comunicación? • Training toma en consideracion este individual skill? • En qué medida se aplica en su proyecto? • Qué espacio tienen para dar opiniones, participar en decisiones, etc? ◦ Son escuchadas? • Se puede mejorar?
14. Estado de la comunidad Mejoras en vías de implementación • Evaluar posibilidad de hacer el training en equipos • Evaluar herramientas QA (Rally vs. Test Link) • Proceso de selección - prueba técnica ◦ Poll de preguntas by Alejandra Silva • Ingles ◦ Actividades de a pares ◦ Code Names
15. Brainstorming! • Qué tópicos les interesaría discutir/tratar? • Priorización de propuestas
16. Referencias • ISTQB Foundations - http://www.istqb.org/downloads/syllabi/foundation-level- syllabus.html • ISTQB Advanced, Test Manager - http://www.istqb.org/downloads/category/10- advanced-level-syllabus-2012.html • TMMI - http://www.tmmi.org/pdf/TMMi.Framework.pdf • IBM, Requirement Pyramid - http://www.informit.com/articles/article.aspx? p=1152528
17. ¡Muchas Gracias!