| Accepted papers |
|
A detailed agenda is forthcoming. MaRK'10 Accepted Papers
Nirav Ajmeri , Riddhima Sejpal and Smita Ghaisas . A Semantic and Collaborative platform for Agile Requirements Evolution Abstract: The characteristics of web-based and community-oriented social software are very useful in the context of software engineering in general and requirements engineering in particular. Their ease of use, transparency of communication, user orientation, self organization and emergent nature resulting from a continual social feedback are particularly relevant to an agile requirements definition exercise. The reason is that agile requirements are inherently meant to be collaboration-intensive. However, while the benefits of social platforms are valuable, they are necessary and not sufficient in themselves for making the exercise effective. The emerging social software engineering discipline is about enabling community-driven creation, management and deployment of software by applying methods, processes and tools in online environments [1-4]. In this paper, we report our work on a semantic and collaborative platform that combines the virtues of social software principles and the semantic web concepts to enable knowledge-assisted agile requirements definition. Dewi Mairiza and Didar Zowghi. An Ontological Framework to Manage the Relative Conflicts between Security and Usability Requirements Abstract: Non-Functional Requirements (NFRs) are interacting, which means they tend to interfere, conflict, and contradict with one other. This interacting characteristic arises as a result of inherent contradiction among NFRs. In the literature, this characteristic has been categorized as the positive or negative interrelationships among NFRs. However, as NFRs are also relative, which means the interpretation of NFRs may vary depending on many factors, thus these positive or negative interrelationships are not always obvious. These relationships might change depending on the meaning of NFRs in the system being developed. Consequently, in the NFRs conflicts catalogue, there are some pairs of NFRs that are claimed to be in conflict in the certain cases but they are also claimed as not being in conflict in the other cases. One of them is the relative conflicts between security and usability requirements. This paper focuses on the application of ontology in managing this security-usability relative conflict. The aim is to develop a framework to identify, characterize, and discover the corresponding resolution strategies of the security-usability conflicts. This paper describes our framework to manage the conflicts; summarizes the security-usability conflicts ontology; and demonstrates how the ontology will be used as a basis to assist analysts in managing conflicts between security and usability requirements. Carlos Castro-Herrera. A Hybrid Recommender System for Finding Relevant Users in Open Source Forums Abstract: Open source projects rely heavily on online forums as a key input to the requirements process. These forums are valuable sources for information about the users and their needs. Part of the success of open source projects depends on the collaboration and synergy of community members as they engage in active and productive discussions through posting comments, questions, and advice to online forums. However, the lack of feedback which occurs when initial posts go unanswered can negatively affect the users’ perception of the project, and can subsequently impede adoption, create frustration, and lead to loss of opportunities from not understanding and satisfying the users’ needs.. This problem is quite common in open source forums. Our recent analysis of seven open source projects found that anywhere from 14% to 37% of user posts never get a reply. This paper directly addresses the problem of unanswered posts by presenting a hybrid recommender system that can be used to identify potential users who might be capable of responding to unanswered posts. The proposed system was evaluated using a statistical cross validation, and results show that it significantly outperformed a benchmark random recommender in terms of precision and recall. In addition, an informal analysis of the relationships between the users and the threads is presented to provide further evidence for the potential of recommender systems in this area. Leonid Kof , Ricardo Gacitua, Mark Rouncefield and Pete Sawyer . Concept Mapping as a Means of Requirements Tracing Abstract: Requirements documents often describe the system on different abstraction levels. This results in the fact that the same issues may be described in different documents and with different vocabulary. For analysts who are new to the application domain, this poses a major orientation problem, as they cannot link different concepts or documents with each other. In the presented paper, we propose an approach to map concepts extracted from different documents to each other. This, in turn, allows us to find related passages in different documents, even though the documents represent different levels of abstraction. Practical applicability of the approach was proven in a case study with real-world requirements documents. Dominik Schmitz, Hans W. Nissen, Matthias Jarke and Thomas Rose. Relating Domain Model Based Requirements Management and Situational Method Engineering Abstract: In this paper we revisit our earlier proposed domain model based approach to requirements management from a situational method engineering perspective. The approach has originally been developed dedicatedly for a small- and medium-sized enterprise (SME) in the field of control system development. Broadening the perspective by considering situational method engineering helps to generalize the approach to support any kind of flexible and customer-oriented enterprise that works in highly innovative fields. The investigation has opened up our method for new strategies to make domain model choices and to tailor the requirements-based search for similar projects. Furthermore, the feedback loop that we provide to adapt domain models according to the concrete experiences of an SME within recent projects raises an issue that possibly applies to knowledge management in situational method engineering in general. Achim Menten, Sven Scheibmayr and Lars Klimpke. Using Audio and Collaboration Technologies for Distributed Requirements Elicitation and Documentation Abstract: The success of a software product depends on meeting the requirements and satisfying the needs of the users. The identification of these requirements and needs is the task of requirements engineering. This paper presents a method for the efficient and effective elicitation and documentation of requirements. The method uses collaborative technologies (a wiki system) and audio recordings to allow multiple stakeholders the joint elicitation and documentation of the requirements and their rationales in globally distributed software development settings. Semi-automated linking of the requirements documentation in the wiki with sections of audio recording of stakeholder interviews ensure the traceability of the requirements' rationales. In addition to the method, the concept of a supporting software tool is presented. The results of an evaluation of the method show that the approach is promising. It enables the participation of all relevant stakeholders, supports a common understanding of the requirements and avoids misinterpretations and the dissemination of false information. Peng Liang and Paris Avgeriou . Rationale Management Challenges in Requirements Engineering Abstract: Rationale and rationale management have been playing an increasingly prominent role in software system development mainly due to the knowledge demand during system evaluation, maintenance, and evolution, especially for large and complex systems. The rationale management for requirements engineering, as a commencing and critical phase in software development life cycle, is still under-exploited. In this paper, we first survey briefly the state-of-the-art on rationale employment and applications in requirements engineering. Secondly, we identify the challenges in integrating rationale management in requirements engineering activities in order to promote further investigations and define a research agenda on rationale management in requirements engineering.
|