FSE 2012
60 papers
- A case study of cross-system porting in forked projects
- A field study of refactoring challenges and benefits
- AUSUM: approach for unsupervised bug report summarization
- An industrial study on the risk of software changes
- Assessing the value of branches with what-if analysis
- Asynchronous programs with prioritized task-buffers
- Automated concolic testing of smartphone apps
- Automated extraction of security policies from natural-language software documents
- Automating adaptive maintenance changes with SrcML and LINQ
- Automating presentation changes in dynamic web applications via collaborative hybrid analysis
- CarFast: achieving higher statement coverage faster
- Concept-based failure clustering
- Conditional model checking: a technique to pass information between verifiers
- DTAM: dynamic taint analysis of multi-threaded programs for relevancy
- Dealing with uncertainty in early software architecture
- Detecting and analyzing insecure component usage
- Dione: an integrated measurement and defect prediction solution
- Do crosscutting concerns cause modularity problems?
- Efficiently scripting change-resilient tests
- FaultTracer: a change impact and regression fault analysis tool for evolving Java programs
- From pixels to bytes: evolutionary scenario based design with video
- Green: reducing, reusing and recycling constraints in program analysis
- Has this bug been reported?
- History slicing: assisting code-evolution tasks
- How do developers react to API deprecation?: the case of a smalltalk ecosystem
- How do developers use parallel libraries?
- How do software engineers understand code changes?: an exploratory study in industry
- Improving software developers' fluency by recommending development environment commands
- Inference and checking of context-sensitive pluggable types
- MayPar: a may-happen-in-parallel analyzer for concurrent objects
- Mining the execution history of a software system to infer the best time for its adaptation
- Multi-layered approach for recovering links between bug reports and fixes
- Practical change impact analysis based on static program slicing for industrial software systems
- Predicting null-pointer dereferences in concurrent programs
- REPERTOIRE: a cross-system porting analysis tool for forked software projects
- ReImInfer: method purity inference for Java
- Recalling the "imprecision" of cross-project defect prediction
- Retargeting Android applications to Java bytecode
- Rubicon: bounded verification of web applications
- Sando: an extensible local code search framework
- Scalable malware clustering through coarse-grained behavior modeling
- Scalable test data generation from multidimensional models
- Searching connected API subgraph via text phrases
- SecuriTAS: a tool for engineering adaptive security
- Seeing the forest and the trees: focusing team interaction on value and effort drivers
- Seeking the ground truth: a retroactive study on the evolution and migration of software libraries
- SelfMotion: a declarative language for adaptive service-oriented mobile apps
- Semantic fault diagnosis: automatic natural-language fault descriptions
- Service selection for happy users: making user-intuitive quality abstractions
- Software change contracts
- T-Morph: revealing buggy behaviors of TinyOS applications via rule mining and visualization
- Test input generation using dynamic programming
- Testing mined specifications
- TouchDevelop: app development on mobile devices
- Toward measuring program comprehension with functional magnetic resonance imaging
- Toward semantic search via SMT solver
- UMLtoCSP (UOST): a tool for efficient verification of UML/OCL class diagrams through model slicing
- Understanding myths and realities of test-suite evolution
- Variability points and design pattern usage in architectural tactics
- Who is going to mentor newcomers in open source projects?