FSE 2015
124 papers
- A method to identify and correct problematic software activity data: exploiting capacity constraints and data redundancies
- A textual domain specific language for requirement modelling
- A user-guided approach to program analysis
- An empirical study of goto in C code from GitHub repositories
- Assertion guided symbolic execution of multithreaded programs
- Assertions are strongly correlated with test suite effectiveness
- Auto-completing bug reports for Android applications
- Auto-patching DOM-based XSS at scale
- Automated attack surface approximation
- Automated generation of programming language quizzes
- Automated multi-objective control for self-adaptive software design
- Automated unit test generation for evolving software
- Automatically computing path complexity of programs
- Automatically deriving pointer reference expressions from binary code for memory dump analysis
- Automatically recommending test code examples to inexperienced developers
- Barriers and enablers for shortening software development lead-time in mechatronics organizations: a case study
- Behavioral log analysis with statistical guarantees
- Bespoke tools: adapted to the concepts developers know
- CLAPP: characterizing loops in Android applications
- CLOTHO: saving programs from malformed strings and incorrect string-handling
- Clone-based and interactive recommendation for modifying pasted code
- Combining eye tracking with navigation paths for identification of cross-language code dependencies
- Commit guru: analytics and risk prediction of software commits
- Comparing and combining test-suite reduction and regression test selection
- Comprehensive service matching with MatchBox
- Crash reproduction via test case mutation: let existing test cases help
- Cross-language program slicing for dynamic web applications
- Crowd debugging
- Decentralized self-adaptation in large-scale distributed systems
- Detecting JavaScript races that matter
- Detecting event anomalies in event-based systems
- Detecting semantic merge conflicts with variability-aware execution
- Developer onboarding in GitHub: the role of prior social links and language experience
- DexterJS: robust testing platform for DOM-based XSS vulnerabilities
- Don't panic: reverse debugging of kernel drivers
- Effective and precise dynamic detection of hidden races for Java programs
- Effective test suites for mixed discrete-continuous stateflow controllers
- Efficient and reasonable object-oriented concurrency
- Efficient dependency detection for safe Java test acceleration
- Enhancing Android application bug reporting
- Evaluating a formal scenario-based method for the requirements analysis in automotive software engineering
- Finding schedule-sensitive branches
- FlexJava: language support for safe and modular approximate programming
- GR(1) synthesis for LTL specification patterns
- Gamification for enforcing coding conventions
- Generating TCP/UDP network data for automated unit test generation
- Getting to know you: towards a capability model for Java
- GitSonifier: using sound to portray developer conflict history
- Guided differential testing of certificate validation in SSL/TLS implementations
- Heterogeneous cross-company defect prediction by unified metric representation and CCA-based transfer learning
- Heterogeneous defect prediction
- Hey, you have given me too many knobs!: understanding and dealing with over-designed configuration in system software
- Hidden truths in dead software paths
- How developers search for code: a case study
- How practitioners perceive the relevance of software engineering research
- I heart hacker news: expanding qualitative research findings by analyzing social news websites
- Impact of developer turnover on quality in open-source software
- Improving energy consumption in Android apps
- Improving model-based test generation by model decomposition
- Increasing the efficiency of search-based unit test generation using parameter control
- Information retrieval and spectrum based bug localization: better together
- Inner oracles: input-specific assertions on internal states
- Is the cure worse than the disease? overfitting in automated program repair
- Iterative distribution-aware sampling for probabilistic symbolic execution
- JITProf: pinpointing JIT-unfriendly JavaScript code
- JSketch: sketching for Java
- MatrixMiner: a red pill to architect informal product descriptions in the matrix
- Measure it? Manage it? Ignore it? software practitioners and technical debt
- MemInsight: platform-independent memory debugging for JavaScript
- Mimic: computing models for opaque code
- Modeling readability to improve unit tests
- MultiSE: multi-path symbolic execution using value summaries
- NARCIA: an automated tool for change impact analysis in natural language requirements
- Navigating through the archipelago of refactorings
- Nyx: a display energy optimizer for mobile web apps
- OSSMETER: a software measurement platform for automatically analysing open source software projects
- On the use of delta debugging to reduce recordings and facilitate debugging of web applications
- OnSpot system: test impact visibility during code edits in real software
- Optimizing energy consumption of GUIs in Android apps: a multi-objective approach
- P3: partitioned path profiling
- Performance-influence models for highly configurable systems
- Pockets: a tool to support exploratory programming for novices and educators
- Predicting field reliability
- Proactive self-adaptation under uncertainty: a probabilistic model checking approach
- Product lines can jeopardize their trade secrets
- Products, developers, and milestones: how should I build my N-Gram language model
- Quality and productivity outcomes relating to continuous integration in GitHub
- Quantifying architectural debts
- Quantifying developers' adoption of security tools
- Query-based configuration of text retrieval solutions for software engineering tasks
- Questions developers ask while diagnosing potential security vulnerabilities with static analysis
- RDIT: race detection from incomplete traces
- REMI: defect prediction for efficient API testing
- Requirements, architecture, and quality in a mission critical system: 12 lessons learned
- Responsive designs in a snap
- Rule-based extraction of goal-use case models from text
- Semantic degrees for Industrie 4.0 engineering: deciding on the degree of semantic formalization to select appropriate technologies
- Spotting familiar code snippet structures for program comprehension
- Staged program repair with condition synthesis
- String analysis for Java and Android applications
- Suggesting accurate method and class names
- Summarizing and measuring development activity
- Symbolic execution of programs with heap inputs
- Synthesizing tests for detecting atomicity violations
- Systematic testing of asynchronous reactive systems
- T3i: a tool for generating and querying test suites for Java
- TACO: test suite augmentation for concurrent programs
- TLV: abstraction through testing, learning, and validation
- Targeted program transformations for symbolic execution
- Test report prioritization to assist crowdsourced testing
- The making of cloud applications: an empirical study on software development for the cloud
- Towards automating the security compliance value chain
- Tracing software developers' eyes and interactions for change tasks
- Turning programs against each other: high coverage fuzz-testing using binary-code mutation and dynamic slicing
- UEDashboard: awareness of unusual events in commit histories
- UMTG: a toolset to automatically generate system test cases from use case specifications
- User-centric security: optimization of the security-usability trade-off
- Users beware: preference inconsistencies ahead
- Using software theater for the demonstration of innovative ubiquitous applications
- Vehicle level continuous integration in the automotive industry
- What change history tells us about thread synchronization
- When, how, and why developers (do not) test in their IDEs
- Witness validation and stepwise testification across software verifiers
- iTrace: enabling eye tracking on software artifacts within the IDE to support software engineering tasks