Export Citations
Save this search
Please login to be able to save your searches and receive alerts for new content matching your search criteria.
- articleJanuary 2014
Software That Checks Software: The Impact of PC-lint
James Gimpel gives some fascinating insights into the growth, technology, and impact of the very widely used static analyzer, PC-lint in the never-ending battle against the bug.
- research-articleJuly 2013
CODEMINE: Building a Software Development Data Analytics Platform at Microsoft
The scale and speed of today's software development efforts impose unprecedented constraints on the pace and quality of decisions made during planning, implementation, and postrelease maintenance and support for software. Decisions during the planning ...
- research-articleJuly 2013
Developer Dashboards: The Need for Qualitative Analytics
Prominent technology companies including IBM, Microsoft, and Google have embraced an analytics-driven culture to help improve their decision making. Analytics aim to help practitioners answer questions critical to their projects, such as "Are we on ...
- ArticleJune 2013
Analysis of bugs in Apache Virtual Computing Lab
DSN '13: Proceedings of the 2013 43rd Annual IEEE/IFIP International Conference on Dependable Systems and Networks (DSN)Pages 1–6https://doi.org/10.1109/DSN.2013.6575324Understanding the bugs in software platforms is extremely valuable for developers, especially during the testing phase. However, this is a rarely investigated issue for open source Cloud platforms till date. In this paper, we present the analysis of 146 ...
- ArticleJune 2013
Automating the debugging of datacenter applications with ADDA
DSN '13: Proceedings of the 2013 43rd Annual IEEE/IFIP International Conference on Dependable Systems and Networks (DSN)Pages 1–12https://doi.org/10.1109/DSN.2013.6575303Debugging data-intensive distributed applications running in datacenters is complex and time-consuming because developers do not have practical ways of deterministically replaying failed executions. The reason why building such tools is hard is that non-...
-
- research-articleJune 2013
A Three-Step Program for Recovering Hackers
Following a three-step program can help software developers rely less on users to catch their bugs.
- research-articleFebruary 2013
Automated Behavioral Testing of Refactoring Engines
IEEE Transactions on Software Engineering (ISOF), Volume 39, Issue 2Pages 147–162https://doi.org/10.1109/TSE.2012.19Refactoring is a transformation that preserves the external behavior of a program and improves its internal quality. Usually, compilation errors and behavioral changes are avoided by preconditions determined for each refactoring transformation. However, ...
- ArticleNovember 2012
Adaptive test selection for post-silicon timing validation: A data mining approach
ITC '12: Proceedings of the 2012 IEEE International Test Conference (ITC)Pages 1–7https://doi.org/10.1109/TEST.2012.6401540Test failure data produced during post-silicon validation contain accurate design- and process-specific information about the DUD (design-under-debug). Prior research efforts and industry practice focused on feeding this information back to the design ...
- ArticleNovember 2012
On efficient silicon debug with flexible trace interconnection fabric
ITC '12: Proceedings of the 2012 IEEE International Test Conference (ITC)Pages 1–9https://doi.org/10.1109/TEST.2012.6401539Trace-based debug solutions facilitate to eliminate bugs escaped from pre-silicon verification and have gained wide acceptance in the industry. Generally speaking, a number of “key” signals in the circuit are tapped, but not all of them can be observed ...
- ArticleSeptember 2012
Adapting Linux for mobile platforms: An empirical study of Android
ICSM '12: Proceedings of the 2012 IEEE International Conference on Software Maintenance (ICSM)Pages 629–632https://doi.org/10.1109/ICSM.2012.6405339To deliver a high quality software system in a short release cycle time, many software organizations chose to reuse existing mature software systems. Google has adapted one of the most reused computer operating systems (i.e., Linux) into an operating ...
- ArticleSeptember 2012
Retrieving software maintenance history with topic models
ICSM '12: Proceedings of the 2012 IEEE International Conference on Software Maintenance (ICSM)Pages 621–624https://doi.org/10.1109/ICSM.2012.6405337Software maintenance history is a chronological record of significant maintenance events. It provides high level knowledge to software stakeholders, helps them to make important decisions. Unfortunately, retrieving software maintenance history is a ...
- ArticleSeptember 2012
Domain specific warnings: Are they any better?
ICSM '12: Proceedings of the 2012 IEEE International Conference on Software Maintenance (ICSM)Pages 441–450https://doi.org/10.1109/ICSM.2012.6405305Tools to detect coding standard violations in source code are commonly used to improve code quality. One of their original goals is to prevent bugs, yet, a high number of false positives is generated by the rules of these tools, i.e., most warnings do ...
- ArticleSeptember 2012
Modelling the ‘Hurried’ bug report reading process to summarize bug reports
ICSM '12: Proceedings of the 2012 IEEE International Conference on Software Maintenance (ICSM)Pages 430–439https://doi.org/10.1109/ICSM.2012.6405303Although bug reports are frequently consulted project assets, they are communication logs, by-products of bug resolution, and not artifacts created with the intent of being easy to follow. To facilitate bug report digestion, we propose a new, ...
- ArticleSeptember 2012
When would this bug get reported?
ICSM '12: Proceedings of the 2012 IEEE International Conference on Software Maintenance (ICSM)Pages 420–429https://doi.org/10.1109/ICSM.2012.6405302Not all bugs in software would be experienced and reported by end users right away: Some bugs manifest themselves quickly and may be reported by users a few days after they get into the code base; others manifest many months or even years later, and may ...
- ArticleSeptember 2012
The impact of bug management patterns on bug fixing: A case study of Eclipse projects
ICSM '12: Proceedings of the 2012 IEEE International Conference on Software Maintenance (ICSM)Pages 264–273https://doi.org/10.1109/ICSM.2012.6405281An efficient bug management process is critical for the success of software projects. Prior work has focused on improving this process, for example, by automating bug triaging, detecting duplicate bugs, and understanding the rationale for re-opening ...
- ArticleSeptember 2012
Making automatic repair for large-scale programs more efficient using weak recompilation
ICSM '12: Proceedings of the 2012 IEEE International Conference on Software Maintenance (ICSM)Pages 254–263https://doi.org/10.1109/ICSM.2012.6405280For large-scale programs, automatically repairing a bug by modifying source code is often a time-consuming process due to plenty of time spent on recompiling and reinstalling the patched program. To suppress the above time cost and make the repair ...
- ArticleSeptember 2012
How often do unintended inconsistencies happen? Deriving modification patterns and detecting overlooked code fragments
ICSM '12: Proceedings of the 2012 IEEE International Conference on Software Maintenance (ICSM)Pages 222–231https://doi.org/10.1109/ICSM.2012.6405275It is difficult to keep consistent source code. Unintended inconsistencies occur unless we recognize all the code fragments that need to modify in a given bug fix or functional addition. Before modifying source code, keyword-based search tools like grep ...
- research-articleSeptember 2012
Quantifying the Effect of Using Kanban versus Scrum: A Case Study
Proponents of various processes and methods in the agile and lean communities have made many bold claims about usefulness, but those claims are rarely supported by empirical investigations. Data gathered from more than 12,000 work items collected over ...
- articleJanuary 1986
Software reliability modeling and analysis
IEEE Transactions on Software Engineering (ISOF), Volume 12, Issue 1Pages 25–31https://doi.org/10.1109/TSE.1986.6312916A discrete and, as approximation to it, a continuous model for the software reliability growth process are examined. The discrete model is based on independent multinomial trials and concerns itself with the joint distribution of the first occurrence ...
- articleJanuary 1986
Exponential order statistic models of software reliability growth
IEEE Transactions on Software Engineering (ISOF), Volume 12, Issue 1Pages 12–24https://doi.org/10.1109/TSE.1986.6312915Failure times of a software reliability growth process are modeled as order statistics of independent nonidentically distributed exponential random variables. The Jelinsky-Moranda, Goel-Okumoto, Littlewood, Musa-Okumoto logarithmic, and power law models ...