now browsing by category
Our research group was represented at this year’s ICSE, the 39th International Conference on Software Engineering.
Dr. Davide Fucci presented his work originally published in Transactions of Software Engineering (TSE):
Davide Fucci, Hakan Erdogmus, Burak Turhan, Markku Oivo, Natalia Juristo: A Dissection of Test-Driven Development: Does It Really Matter to Test-First or to Test-Last?
Daniel Martens and Timo Johann presented their work at the Second International Workshop on Emotion Awareness in Software Engineering co-organized by Prof. Dr. Walid Maalej:
Daniel Martens and Timo Johann: On the Emotion of Users in App Reviews
More information about the conference and the schedule of the presentations can be found at the ICSE website.
Our paper “Bug Report, Feature Request, or Simply Praise? On Automatically Classifying App Reviews” authored by Walid Maalej and Hadeer Nabil has been selected at the 23rd International IEEE Requirements Engineering Conference (RE15) as Best Research Paper.
The awarded paper was a.o the result of the research visit of Hadeer Nabil and her Master thesis supervised by Prof. Maalej.
RE is the primer research conference in the field of requirements engineering. It has an acceptance rate of ~15-25% and yearly attracts 250-400 researchers and experts in the field. This year the conference took place Ottowa Canada. More information.
The most influential paper went this year to Paolo Giorgini, Fabio Massacci, John Mylopoulos and Nicola Zannone and was awarded for the Paper “Modeling security requirements through ownership, permission and delegation”
You can download our awarded Paper here.
Our research group is strongly represented at this year’s RE, the 22nd IEEE International Requirements Engineering Conference. MOBIS members will present the following 2 papers at the main conference:
- How Do Users Like this Feature? A Fine Grained Sentiment Analysis of App Reviews (Emitza Guzman, Walid Maalej)
- Capturing and Sharing Domain Knowledge with Business Rules: Lessons Learned from a Global Software Vendor (Walid Maalej, Smita Ghaisas)
Furthermore, MOBIS members will present the following 3 papers at the conference collocated workshops:
- On Lawful Disclosure of Personal User Data: What Should App Developers Do? (Yung Shin Van Der Sype, Walid Maalej) at the 7th International Workshop on Requirements Engineering and Law.
- What Stakeholders Need to Know About Requirements (Walid Maalej, Zijad Kurtanović, Alexander Felfernig) at the 4th Workshop on Empirical Requirements Engineering
- Liquid Democracy for a Sustainable and Scalable Participation in Requirements Engineering (Timo Johann and Walid Maalej) at the 3rd International Workshop on Requirements Engineering for Sustainable Systems
More information about the conference and the schedule of the presentations can be found at the RE website.
“User Feedback in the AppStore: An Empirical Study” is the title of the new paper by Prof. Maalej and Dennis Pagano which has been recently accepted for publication at the renowned conference “IEEE International Conference on Requirements Engineering” RE 2013.
This research will be presented by Prof. Maalej at RE 2013 in Rio De Janeiro.
Dennis Pagano and Walid Maalej
Application distribution platforms – or app stores – such as Google Play or Apple AppStore allow users to submit feedback in form of ratings and reviews to downloaded applications. In the last few years, these platforms have become very popular to both application developers and users. However, their real potential for and impact on requirements engineering processes are not yet well understood. This paper reports on an exploratory study, which analyzes over one million reviews from the Apple AppStore. We investigated how and when users provide feedback, inspected the feedback content, and analyzed its impact on the user community. We found that most of the feedback is provided shortly after new releases, with a quickly decreasing frequency over time. Reviews typically contain multiple topics, such as user experience, bug reports, and feature requests. The quality and constructiveness vary widely, from helpful advices and innovative ideas to insulting offenses. Feedback content has an impact on download numbers: positive messages usually lead to better ratings and vice versa. Negative feedback such as shortcomings is typically destructive and misses context details and user experience. We discuss our findings and their impact on software and requirements engineering teams.
“Patterns of Knowledge in API Reference Documentation” is the title of the new paper by Prof. Maalej and Prof. Robillard, which has been recently accepted for publication at the renowned journal IEEE Transactions on Software Engineering.
Walid Maalej and Martin P. Robillard
Reading reference documentation is an important part of programming with APIs. Reference documentation complements the API by providing information not obvious from the API syntax. To improve the quality of reference documentation and the efficiency with which the relevant information it contains can be accessed, we must first understand its content. We report on a study of the nature and organization of knowledge contained in the reference documentation of the hundreds of APIs provided as part of two major technology platforms: Java SDK 6 and .NET 4.0. Our study involved the development of a taxonomy of knowledge types based on grounded methods and independent empirical validation. Seventeen trained coders used the taxonomy to rate a total of 5574 randomly-sampled documentation units to assess the knowledge they contain. Our results provide a comprehensive perspective on the patterns of knowledge in API documentation: observations about the types of knowledge it contains, and how this knowledge is distributed throughout the documentation. The taxonomy and patterns of knowledge we present in this paper can be used to help practitioners evaluate the content of their API documentation, better organize their documentation, and limit the amount of low-value content. They also provides a vocabulary that can help structure and facilitate discussions about the content of APIs.
*This is the authors’ version of the work. The final formal version should be accessed via IEEE DL and might slightly differ from this preprint version