Software Defects

  • 622 views
Uploaded on

A summary of my Master's thesis "Software Defect Analysis: An Empirical Study of Causes and Costs in the Information Technology Industry" which were supervised by professor Reidar Conradi and …

A summary of my Master's thesis "Software Defect Analysis: An Empirical Study of Causes and Costs in the Information Technology Industry" which were supervised by professor Reidar Conradi and co-supervised by post.doc. Jingyue Li.

http://daim.idi.ntnu.no/masteroppgave?id=5580

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
622
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. THE TASKAnalysis of defect reports, evaluation of implemented ODC classification scheme, and suggest areas for improvement.Problem: 20% of the defect reports takes 80% of the available resources.EVISOFT-project: Evidence based Software Process Improvement 2
  • 2. COMPANY A RESULTS 40 35 30 25 20 15 Core 10 B2C 5 B2B 0 3
  • 3. PROJECT PROFILES (EXTENSIVE EFFORT)Core is low level, algorithms, design phase and high risk of regressions.B2C is high level, algorithms, functions, classes and objects, design phase.B2B assignation and initialisation,code phase. 4
  • 4. PROJECT PROFILES (LITTLE EFFORT)Core: Assignation and intialisation, function classes and objects, code phase, and low regression riskB2C: checking statements, code phase and low regression risk.B2B: checking statements and interfaces, requirements phase.In general: High level of unspecified values 5
  • 5. COMPARISON VERSUS ANOTHER COMPANYDifferent reasons for both extensive and little effort to correct defectsExtensive effort: Logical errors in codeLittle effort: UI defects,In general: domain knowledge 6
  • 6. FACTORSSize of the systemComplexity of the systemThe phase a defect is discoveredThe maintainers’ experience with the system and the domainTools and processes 7
  • 7. SOURCESJan Maximilian Winther Kristiansen «Software Defect Analysis - An Empirical Study of Causes and Costs in the Information Technology Industry» (http://www.idi.ntnu.no/grupper/su/su-diploma-2010/dipl10- janmaxim.pdf)Jan Maximilian Winther Kristiansen, Jingyue Li, Tor Stålhane and Reidar Conradi «Cost Drivers of Software Corrective Maintenance: An Empirical Study in Two Companies» ,In proceedings of ICSM ’10: International Conference on Software MaintenanceJingyue Li, Jan Maximilian Winther Kristiansen, Tor Stålhane and Reidar Conradi «Enhancing Software Defect Tracking System to Facilitate Continuous Software Quality Assessment and Improvement», Submitted to IEEE Software journal for review. 8