ESEC/FSE '11最新文献

Semistructured merge: rethinking merge in revision control systems 半结构化合并:重新思考修订控制系统中的合并

ESEC/FSE '11 Pub Date : 2011-09-09 DOI: 10.1145/2025113.2025141

S. Apel, Jörg Liebig, B. Brandl, C. Lengauer, Christian Kästner

{"title":"Semistructured merge: rethinking merge in revision control systems","authors":"S. Apel, Jörg Liebig, B. Brandl, C. Lengauer, Christian Kästner","doi":"10.1145/2025113.2025141","DOIUrl":"https://doi.org/10.1145/2025113.2025141","url":null,"abstract":"An ongoing problem in revision control systems is how to resolve conflicts in a merge of independently developed revisions. Unstructured revision control systems are purely text-based and solve conflicts based on textual similarity. Structured revision control systems are tailored to specific languages and use language-specific knowledge for conflict resolution. We propose semistructured revision control systems that inherit the strengths of both: the generality of unstructured systems and the expressiveness of structured systems. The idea is to provide structural information of the underlying software artifacts --- declaratively, in the form of annotated grammars. This way, a wide variety of languages can be supported and the information provided can assist in the automatic resolution of two classes of conflicts: ordering conflicts and semantic conflicts. The former can be resolved independently of the language and the latter using specific conflict handlers. We have been developing a tool that supports semistructured merge and conducted an empirical study on 24 software projects developed in Java, C#, and Python comprising 180 merge scenarios. We found that semistructured merge reduces the number of conflicts in 60% of the sample merge scenarios by, on average, 34%, compared to unstructured merge. We found also that renaming is challenging in that it can increase the number of conflicts during semistructured merge, and that a combination of unstructured and semistructured merge is a pragmatic way to go.","PeriodicalId":184518,"journal":{"name":"ESEC/FSE '11","volume":"42 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-09-09","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117132751","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 112

The 4th international workshop on social software engineering (SSE'11) 第四届社会软件工程国际研讨会(SSE'11)

ESEC/FSE '11 Pub Date : 2011-09-09 DOI: 10.1145/2025113.2025211

W. Maalej, Raian Ali

{"title":"The 4th international workshop on social software engineering (SSE'11)","authors":"W. Maalej, Raian Ali","doi":"10.1145/2025113.2025211","DOIUrl":"https://doi.org/10.1145/2025113.2025211","url":null,"abstract":"Software is created by people and for people. People are heterogeneous in their beliefs, backgrounds, and preferences. Accommodating and exploiting the social variety is crucial for successful engineering and usage of software. On the one hand, software engineering is a social activity, performed by different individuals and teams. This necessitates methodologies and tools to deal with issues such as communication, coordination, knowledge sharing, compensation, and reconciliation. On the other hand, Social Software (Internet Forums, Wikis, Social Networks, Blogs, etc.) is an expanding computing paradigm, which inherently incorporates intensive social interactions and implications. Engineering Social Software magnifies a spectrum of challenges like group requirements engineering, social-awareness, privacy, security, and trust.\u0000 Both directions -- engineering Social Software and treating software engineering as a social activity -- require competency from other disciplines as diverse as psychology, sociology, and organizational science. While both directions receive considerable attention, research in both fields is fragmented, uncoordinated, and partially redundant. The goal of this workshop is to confluence the research on social aspects in software engineering and engineering of Social software into a new field of Social Software Engineering (SSE).","PeriodicalId":184518,"journal":{"name":"ESEC/FSE '11","volume":"101 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-09-09","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127990237","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 1

jStar-eclipse: an IDE for automated verification of Java programs jStar-eclipse:用于自动验证Java程序的IDE

ESEC/FSE '11 Pub Date : 2011-09-05 DOI: 10.1145/2025113.2025182

Daiva Naudziuniene, M. Botincan, Dino Distefano, Mike Dodds, Radu Grigore, Matthew J. Parkinson

引用次数: 4

EAGLE: engineering software in the ubiquitous globe by leveraging uncErtainty EAGLE:利用不确定性在无处不在的全球范围内开发工程软件

ESEC/FSE '11 Pub Date : 2011-09-05 DOI: 10.1145/2025113.2025199

M. Autili, V. Cortellessa, D. D. Ruscio, P. Inverardi, Patrizio Pelliccione, Massimo Tivoli

{"title":"EAGLE: engineering software in the ubiquitous globe by leveraging uncErtainty","authors":"M. Autili, V. Cortellessa, D. D. Ruscio, P. Inverardi, Patrizio Pelliccione, Massimo Tivoli","doi":"10.1145/2025113.2025199","DOIUrl":"https://doi.org/10.1145/2025113.2025199","url":null,"abstract":"In the next future we will be surrounded by a virtually infinite number of software applications that provide computational software resources in the open Globe. This will radically change the way software will be produced and used. Users will be keen on producing their own piece of software, by also reusing existing software, to better satisfy their needs, therefore with a goal oriented, opportunistic use in mind. The produced software will need to be able to evolve, react and adapt to a continuously changing environment, while guaranteeing dependability. The strongest adversary to this view is the lack of knowledge on the software's structure, behavior, and execution context. Despite the possibility to extract observational models from existing software, a producer will always operate with software artifacts that exhibit a degree of uncertainty in terms of their functional and non functional characteristics. We believe that uncertainty can only be controlled by making it explicit and by using it to drive the production process itself. In this paper, we introduce a novel paradigm of software production process that explores available software and assesses its degree of uncertainty in relation to the opportunistic goal G, assists the producer in creating the appropriate integration means towards G, and validates the quality of the integrated system with respect to G and the current context.","PeriodicalId":184518,"journal":{"name":"ESEC/FSE '11","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-09-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129564762","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 23

Fault localization for data-centric programs 以数据为中心的程序的故障定位

ESEC/FSE '11 Pub Date : 2011-09-05 DOI: 10.1145/2025113.2025137

Diptikalyan Saha, M. Nanda, P. Dhoolia, V. K. Nandivada, Vibha Sinha, S. Chandra

引用次数: 31

Proactive detection of collaboration conflicts 主动检测协作冲突

ESEC/FSE '11 Pub Date : 2011-09-05 DOI: 10.1145/2025113.2025139

Yuriy Brun, Reid Holmes, Michael D. Ernst, D. Notkin

引用次数: 227

Understanding failures through facts 通过事实理解失败

ESEC/FSE '11 Pub Date : 2011-09-05 DOI: 10.1145/2025113.2025174

Jeremias Rößler

引用次数: 2

Experimental specification mining for enterprise applications 用于企业应用的实验性规范挖掘

ESEC/FSE '11 Pub Date : 2011-09-05 DOI: 10.1145/2025113.2025169

M. Schur

引用次数: 4

Managing performance vs. accuracy trade-offs with loop perforation 通过循环穿孔管理性能与精度之间的权衡

ESEC/FSE '11 Pub Date : 2011-09-05 DOI: 10.1145/2025113.2025133

Stelios Sidiroglou, Sasa Misailovic, H. Hoffmann, M. Rinard

引用次数: 500

Stateful breakpoints: a practical approach to defining parameterized runtime monitors 有状态断点:定义参数化运行时监视器的实用方法

ESEC/FSE '11 Pub Date : 2011-09-05 DOI: 10.1145/2025113.2025201

E. Bodden

{"title":"Stateful breakpoints: a practical approach to defining parameterized runtime monitors","authors":"E. Bodden","doi":"10.1145/2025113.2025201","DOIUrl":"https://doi.org/10.1145/2025113.2025201","url":null,"abstract":"A runtime monitor checks a safety property during a program's execution. A parameterized runtime monitor can monitor properties containing free variables, or parameters. For instance, a monitor for the regular expression \"close(s)+ read(s)\" will warn the user when reading from a stream s that has previously been closed. Parameterized runtime monitors are very expressive, and research on this topic has lately gained much traction in the Runtime Verification community. Existing monitoring algorithms are very efficient. Nevertheless, existing tools provide little support for actually defining runtime monitors, probably one reason for why few practitioners are using runtime monitoring so far.\u0000 In this work we propose the idea of allowing programmers to express parameterized runtime monitors through stateful breakpoints, temporal combinations of normal breakpoints, a concept well known to programmers. We show how we envision programmers to define runtime monitors through stateful breakpoints and parameter bindings through breakpoint expressions. Further, we explain how stateful break- points improve the debugging experience: they are more expressive than normal breakpoints, nevertheless can be evaluated more efficiently. Stateful breakpoints can be attached to bug reports for easy reproducibility: they often allow developers to run directly to the bug in one single step. Further, stateful breakpoints can potentially be inferred from a running debugging session or using property inference and fault localization tools.","PeriodicalId":184518,"journal":{"name":"ESEC/FSE '11","volume":"6 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2011-09-05","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133861805","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

引用次数: 13