Si la gestión y desarrollo de requisitos es tan importante... ¿Por qué no la mejoramos??
1. 5 Consejos Rápidos … Jordi Borja Director General Borland Ibérica Madrid, 20 de Junio de 2008
2. Esto ya os lo sabéis… 0 10 20 30 40 50 60 70 Requirements Design Code Development Testing Acceptance Testing Operation Relative Cost to Correct a Defect
9. Los 5 subprocesos RDM básicos Requirements Definition & Management IIT Management & Governance Technique | Stakeholders System Boundaries | Glossary IT Management & Governance Strategic & Operational Demand Business Demand IT Operations ELICITATION 1 Elicitation Identify Stakeholders Select Elicitation Techniques 1 Define User Scenarios Set System Boundaries Manage Dependencies Create Glossary / Domain Model
10. Los 5 subprocesos RDM básicos Requirements Definition & Management IIT Management & Governance Technique | Stakeholders System Boundaries | Glossary Prioritization | Verify Risk | Estimation IT Management & Governance Strategic & Operational Demand Business Demand IT Operations ELICITATION ANALYSIS 1 2 Analysis Prioritize High-Level User Scenarios Verification & Analysis
11. Los 5 subprocesos RDM básicos Requirements Definition & Management IIT Management & Governance Technique | Stakeholders System Boundaries | Glossary Prioritization | Verify Risk | Estimation Detail Requirements | Business Model Scenarios | UC Model | Prototype IT Management & Governance Strategic & Operational Demand Business Demand IT Operations ELICITATION ANALYSIS SPECIFICATION 1 3 2 Specification Detail User Scenarios Create Use Case Model Construct/Enhance Business Model Create UI Prototype
12. Los 5 subprocesos RDM básicos Requirements Definition & Management IIT Management & Governance Technique | Stakeholders System Boundaries | Glossary Prioritization | Verify Risk | Estimation Detail Requirements | Business Model Scenarios | Use Case Model | Prototype Review | Signoff | Baseline IT Management & Governance Strategic & Operational Demand Business Demand IT Operations ELICITATION ANALYSIS SPECIFICATION VALIDATION 1 3 2 4 Validation Review / Validate Requirements
18. Hay, la comunicación … tiempo Lo que el cliente NECESITA Lo DESARROLLADO } Expectation Gap Crítico! Esto no me vale! … pero funciona! PERFECTO… lo voy a probar! FUNCIONA! Customer Developer
25. Requirements Based Testing Una solución que valida que los requisitos son correctos, completos y sin ambigüedades ; y que define automáticamente el conjunto óptimo de casos de prueba a partir de los requisitos para asegurar la calidad del producto Requirements Quality Validate against Business Objectives Map Against Use Cases Ambiguity Analysis Domain Expert Reviews Validated Requirements Logical Test Cases Fix Requirements Validated Test Cases Validate Apps Test Case Design Formalize Requirements Define / Optimize Test Cases Test Cases Quality Review Test Cases by Reqs Authors Review Test Cases by Domain Experts Design & Code Quality Review Test Cases by Developers Review Design & Code with Test Cases Test Execution Complete Test Cases Execution Tests
26. Requirements Based Testing Formalize Requirements For Test Design Cálculo automático de los casos de prueba Exportación directa a herramienta de pruebas
36. ¿A que me ayuda la trazabilidad? task USER goal strategy MARKETING BUSINESS conversation system feature FUNCTIONAL INTERFACE ¿Están todas mis necesidades satisfechas? Cliente
37. ¿A que me ayuda la trazabilidad? task USER conversation system feature FUNCTIONAL INTERFACE ¿Es necesario esto que estoy implementando? Desarrollador goal strategy MARKETING BUSINESS
38. Impacto del Cambio … el impacto de un cambio en los requisitos en las pruebas (y viceversa) está claramente gestionado.
