ICSE 2014
99 papers
- A critical review of "automatic patch generation learned from human-written patches": essay on the problem statement and the evaluation of automatic software repair
- A study and toolkit for asynchronous programming in c#
- A study of equivalent and stubborn mutation operators using human analysis of equivalence
- APE: an annotation language and middleware for energy-efficient mobile application development
- AR-miner: mining informative reviews for developers from mobile app marketplace
- Achieving accuracy and scalability simultaneously in detecting application clones on Android markets
- Alternate refactoring paths reveal usability problems
- An analysis of the relationship between conditional entropy and failed error propagation in software testing
- An exploratory study of the pull-based software development model
- Analyze this! 145 questions for data scientists in software engineering
- AsDroid: detecting stealthy behaviors in Android applications by user interface and program behavior contradiction
- Automated design of self-adaptive software with control-theoretical formal guarantees
- Automated goal operationalisation based on interpolation and SAT solving
- Automated memory leak detection for production use
- Brownout: building more robust cloud applications
- Building it together: synchronous development in OSS
- CARE: cache guided deterministic replay for concurrent Java programs
- Case studies and tools for contract specifications
- Characterizing and detecting performance bugs for smartphone applications
- Checking app behavior against app descriptions
- Code coverage for suite evaluation by developers
- CodeHint: dynamic and interactive synthesis of code snippets
- Comparing static bug finders and statistical prediction
- ConLock: a constraint-based approach to dynamic checking on deadlocks in multithreaded programs
- Controlled modeling environment using flexibly-formatted spreadsheets
- Coverage is not strongly correlated with test suite effectiveness
- Cowboys, ankle sprains, and keepers of quality: how is video game development different from software development?
- Cross-checking oracles from intrinsic software redundancy
- Data-guided repair of selection statements
- Design rule spaces: a new form of architecture insight
- Detecting differences across multiple instances of code clones
- Detecting memory leaks through introspective dynamic behavior modelling using machine learning
- Detecting performance anti-patterns for applications developed using object-relational mapping
- Dictionary learning based software defect prediction
- Distilling privacy requirements for mobile applications
- Does latitude hurt while longitude kills? geographical and temporal separation in a large scale software development project
- Easing software component repository evolution
- Effects of using examples on structural model comprehension: a controlled experiment
- Enhancing symbolic execution with veritesting
- Exploring variability-aware execution for testing plugin-based web applications
- Feature maintenance with emergent interfaces
- Hope for the best, prepare for the worst: multi-tier control for adaptive systems
- How do API documentation and static typing affect API usability?
- How do centralized and distributed version control systems impact software changes?
- How do professionals perceive legacy systems and software modernization?
- How to make best use of cross-company data in software effort estimation?
- Improving automated source code summarization via an eye-tracking study of programmers
- Inductive verification of data model invariants for web applications
- Inferring models of concurrent systems from logs of their behavior with CSight
- Influence of social and technical factors for evaluating contribution in GitHub
- Integrating adaptive user interface capabilities in enterprise applications
- Interpolated n-grams for model based testing
- Is spreadsheet ambiguity harmful? detecting and repairing spreadsheet smells due to ambiguous computation
- Lifting model transformations to product lines
- Live API documentation
- Making web applications more energy efficient for OLED smartphones
- Manual refactoring changes with automated refactoring validation
- Micro execution
- Mind the gap: assessing the conformance of software traceability to relevant guidelines
- Mining behavior models from user-intensive web applications
- Mining billions of AST nodes to study actual and potential usage of Java language features
- Mining configuration constraints: static analyses and empirical results
- Mining fine-grained code changes to detect unknown change patterns
- Mining interprocedural, data-oriented usage patterns in JavaScript web applications
- MintHint: automated synthesis of repair hints
- Patch verification via multiversion interprocedural control flow graphs
- Performance regression testing target prioritization via performance risk analysis
- Perturbation analysis of stochastic systems with empirical distribution parameters
- Programmers' build errors: a case study (at google)
- Property differencing for incremental checking
- Requirements fixation
- Reuse-oriented reverse engineering of functional components from x86 binaries
- Reviser: efficiently updating IDE-/IFDS-based data-flow analyses in response to incremental program changes
- SEEDS: a software engineer's energy-optimization decision support framework
- Self-adaptation through incremental generative model transformations at runtime
- SimRT: an automated framework to support regression testing for data races
- Software engineering at the speed of light: how developers stay current using twitter
- Spotting working code examples
- Symbolic assume-guarantee reasoning through BDD learning
- The dimensions of software engineering success
- The strength of random search on automated program repair
- Time pressure: a controlled experiment of test case development and requirements review
- Towards efficient optimization in package management systems
- TradeMaker: automated dynamic analysis of synthesized tradespaces
- Trading robustness for maintainability: an empirical study of evolving c# programs
- Transition from centralized to decentralized version control systems: a case study on reasons, barriers, and outcomes
- Two's company, three's a crowd: a case study of crowdsourcing software development
- Uncertainty, risk, and information value in software requirements and architecture
- Understanding JavaScript event-based interactions
- Understanding and improving software build teams
- Understanding understanding source code with functional magnetic resonance imaging
- Unit test virtualization with VMVM
- Unleashing concurrency for irregular data structures
- Us and them: a study of privacy requirements across north america, asia, and europe
- Using dynamic analysis to generate disjunctive invariants
- Using psycho-physiological measures to assess task difficulty in software development
- Vejovis: suggesting fixes for JavaScript faults
- Verifying component and connector models against crosscutting structural views
- Which configuration option should I change?