2nd Workshop on Mining Unstructured Data (MUD’12)

Alberto Bacchelli, Faculty of Informatics, University of Lugano, Lugano, Switzerland
Nicolas Bettenburg, Software Analysis and Intelligence Lab, Queen’s University, Kingston, Ontario, Canada
Latifa Guerrouj, SOCCER Lab, École Polytechnique de Montréal, Montréal, Québec, Canada

Today’s software developers are supported by a variety of tools, such as version control systems like GIT, Issue Tracking Systems like BugZilla, and mailing list services. As such we have a wide range of information recorded in the repositories in which these tools store their data. These repositories comprise two types of data: Structured Data and Unstructured Data. Structured data, such as source code or execution traces, has a well-established structure and grammar, and is straightforward to parse and use with computer machinery. Unstructured data, such as documentation, discussions, comments, customer support requests, consists of a mixture of natural language text, snippets of structured data, and noise. Mining unstructured data poses many hard challenges, since out-of-the box approaches adopted from related fields such as Natural Language Processing (NLP) and Information Retrieval (IR) cannot be directly applied in the Software Engineering domain. The goal of this half-day workshop is to address these challenges and aims to make the knowledge contained in unstructured data repositories accessible to practitioners and researchers.

More information is available on the workshop web site:

Workshop on The Law and Reverse Engineering

Keith Gallagher, Department of Computing Sciences, Florida Institute of Technology
Cem Kaner, Department of Computing Sciences, Florida Institute of Technology
Jenifer Deignan, Department of Computing Sciences, Florida Institute of Technology

Almost all software contracts that are not open-source contain broad bans on reverse engineering, but as far as we can tell, almost all professional software development does reverse engineering to some degree. This is a fundamental, unresolved conflict. Every student and practitioner of software engineering will face reverse engineering issues and they will have to make their own decisions about what is fair and reasonable in their situation, what risks they are willing to accept, and what corporate policies they should follow, support, or challenge. The industry is polarized and it will probably be a decade or more before the next generation of leadership revisits this conflict in a constructive way. For now, the statutes and the courts offer insufficient guidance. We plan to highlight the issues of the law and reverse engineering through examples. Each exemplar case will be drawn either from an actual lawsuit or from a technical advance in reverse engineering. Rather than telling particiants what to do, we will lay out the factors that we think they should consider.

WCRE 2012 – 19th Working Conference on Reverse Engineering