Academic
Publications
Debugging Process Models based on Changes in Impressions of Software Modules

Debugging Process Models based on Changes in Impressions of Software Modules,Shinji Uchida,Akito Monden,Hajimu Iida,Ken-ichi Matsumoto,Katsuro Inoue,H

Debugging Process Models based on Changes in Impressions of Software Modules   (Citations: 3)
BibTex | RIS | RefWorks Download
This paper proposes analysis models for representing processes of debugging unfamiliar programs focusing on how engineers comprehend each software module and locate a bug. Since actual debugging strategies relate to engineers' impressions of each software module - either the module is faulty, not faulty or uncertain, proposed models consider both mental- and external- activities of engineers. We applied periodic interviewing method for quantitatively capturing engineers' mental activities. By characterizing target programs from multiple viewpoints such as module dependences and program slicing, engineers' debugging activities were analyzed in details based on the models.
Published in 2000.
Cumulative Annual
View Publication
The following links allow you to view full publications. These links are maintained by other sources not affiliated with Microsoft Academic Search.
    • ...Three steps of debugging process have been recognized by Uchina et al. [16]: program reading, bug location and bug correction...

    Shaochun Xuet al. Cognitive Process during Program Debugging

    • ...We need to investigate subjects’ intentions – “Why did they read?” In our previous researches [11][12], we have observed that strategies to select a module (= an area that should be comprehended) strongly relate to engineers’ impressions of each module – either the module is faulty, not faulty or uncertain...
    • ...We propose a new modeling schema: Multiple-View Analysis Model of Debugging Process[12][13]...

    Shinji Uchidaet al. Analysis of Program Reading Process in Software Debugging Based on Mul...

    • ...We need to investigate the subjects’ intentions – “Why did they read?” In our previous researches [13][14], we have observed that strategies to select a module (= an area that should be comprehended) strongly relates to the engineers’ impressions of each module – either the module is faulty, not faulty, or uncertain...
    • ...The following four characteristics are presented: - Control dependence between modules (in this case, this is equivalent to a module call structure) (Fig. 2- (a)), - Data dependence between modules (Fig. 2-(b)), - Static slice [13][14] calculated from the wrong output value (Fig. 2-(c)), and - Faulty execution path (Fig. 2-(d))...

    Shinji Uchidaet al. A Multiple-View Analysis Model of Debugging Processes

Sort by: