Case Studies or Anecdotal Evidence? Research direction. Research areas. RVS annons 1. Case Study or Anecdotal Evidence? Professor Per Runeson

Size: px

Start display at page:

Download "Case Studies or Anecdotal Evidence? Research direction. Research areas. RVS annons 1. Case Study or Anecdotal Evidence? Professor Per Runeson"

Willis Russell
8 years ago
Views:

1 Case Studies or Anecdotal Evidence? Professor Per Runeson CV Civilingenjör D Konsult (Q-Labs) Forskarstuderande 1998 Tekn. Dr Lektor Docent 22/23 Fulbright grant WSU 24- Professor Rådsforskare VR Research direction Quantifiable Software Quality Management Research areas Empirical software engineering Software process improvement (SPI) Improvement of the V&V process Improvement of V&V techniques Software reliability engineering Estimation of defects after inspection Software quality and management Agile methods in a gate-model context RVS annons 1 Case Study or Anecdotal Evidence? Professor Per Runeson redan efter 45 minuter så hörde jag att motorn tystnade, det som rasslade och skramlade innan var som bortblåst och efter två timmars körning så blev det som en helt annan bil Annons i Teknikens Värld 8/4 1

Software process improvement (SPI) Improvement of the V&V process Improvement of V&V techniques Software reliability engineering Estimation of defects after inspection Software quality and management

2 TV test Egentligen säger ett kompressionstest väldigt lite säger Nils Engström på Rototest RVS annons 2 Teknikens Värld 11/4 Före behandlingen var kompressionen något ojämn, framför allt första cylindern halkade efter. Efter behandlingen var kompressionen betydligt jämnare, som genom ett trollslag hade också ettans cylinder hostat upp sig från 7,4 till 9,4 Annons i Teknikens Värld 17/4 Purpose Approach Control Explore Form Purpose Explain Describe Relationship Scope Frequency Rosengren/Arvidsson 22 Comparisons in research - + Approach Q/Q Qualitative Quantitative 2

Efter behandlingen var kompressionen betydligt jämnare, som genom ett trollslag hade också ettans cylinder hostat upp sig från 7,4 till 9,4

3 Approach F/F Flexible Fixed Control Empirical studies in SE Scale Desktop Laboratory Development project Risk Internal Is the study conducted well? Conclusion/reliability Are the statistics/analyses used correctly? Construct Are we measuring/observing the right thing? External Is the setting representative? of Qualitative Studies Alternative classification Credibility Transferability Dependability Confirmability [Robson 1993, Lincoln and Guba 1985] Internal 3

Construct Are we measuring/observing the right thing? External Is the setting representative?

4 Conclusion Construct External Internal vs external validity Internal External Homogenious Heterogenious - Countermeasures Strategy Prolonged involvement Triangulation Peer debriefing Member checking Negative case analysis Audit trail [Robson 22] Reactivity Researcher Respondent bias bias + Case Study or Anecdotal Evidence? It depends on the procedures! Context Official documents Individual Recorded Transcribed perceptions Interviews Interviews Qualitative analysis Conclusions 4

Audit trail [Robson 22] Reactivity Researcher Respondent bias bias + Case Study or Anecdotal Evidence?

5 Characteristics of a good flexible design of three case studies 1. Rigorous data collection 2. Framed with assumptions 3. Understaning of many traditions 4. Procedures from many traditions 5. Idea leads to understanding 6. Detailed methods for collection, analysis and writing 7. Analysis on multple levels 8. Clear writing Aggregating viewpoints for strategic software process improvement-a method and a case study - Karlström Runeson Wohlin Evaluation of a perspective based review method applied in an industrial setting - Berling Runeson Integrating Agile Software Development into Stage-Gate Managed Product - Karlström Runeson Evaluation of a of the use of two review methods CBRM and PBRM(T) One case: Ericsson Microwave Systems Three documents Three increments Doc 1 Doc 2 Doc 3 BB CBRM BC CBRM Identical documents, but the faults found with CBRM are not reported again, when using PBRM(T). BD CBRM BD PBRM(T) 12/37 12/37 12/37 12/37 34/39 33/38 33/38 2/38 33/38 33/38 55/62 54/61 55/62 55/62 Development order of documents Number under document: Number of reviewed pages/number of pages in document Figure 1. The development and review process of inspected specifications Doc 1-3. Evaluation of a Evaluation of a Purpose Evaluation Approach Quantitative Control Medium Threat Internal History Conclusion Implementation Construct Mono-method External Generalizability Countermeasure Bias adjustment Reporting Bias adjustment Qualitative and quantitative Reporting 5

Clear writing Aggregating viewpoints for strategic software process improvement-a method and a case study - Karlström Runeson Wohlin Evaluation of a perspective based review method applied in an

6 Evaluation of a Results PBRM(T) more effective and efficient than CBRM PBRM(T) provides more confidence to engineers of application of an SPI method One case: Fuji Xerox, Tokyo within the case study sampling, web-based data collection Purpose Feasibility study Approach Quantitative Control Internal Threat Maturation Instrumentation Selection Countermeasure Randomize order Consistency check Conclusion Implementation Japanese translation Construct Apprehension Management decision External Generalizability Reporting Results Methods are adequate SPI methodology Identified similarities and discrepancies between managers and engineers Integrating Agile of application of an XP in project management context Two cases: ABB, EMW 6

Randomize order Consistency check Conclusion Implementation Japanese translation Construct Apprehension Management decision External Generalizability Reporting Results Methods are

7 Integrating Agile Integrating Agile Purpose Describe Approach Qualitative Control Internal Conclusion Construct External Threat Data collection Misunderstanding Other factors Generalizability Countermeasure Several sources Inconsistencies Feedback Peer review Long term involvement Reporting Integrating Agile Results Agile vs. non-agile Managementnvs. engineers EMW vs. ABB 7

Generalizability Countermeasure Several sources Inconsistencies Feedback Peer review Long

Integrating Agile Software Development into Stage-Gate Managed Product Development

Integrating Agile Software Development into Stage-Gate Managed Product Development Daniel Karlström Daniel.Karlstrom@telecom.lth.se Dept. Communication Systems, Lund University, Box 118, SE-221 00 Lund,