Submissions Deadline: June 15th, 2009

The Second International Workshop on Managing Requirements Knowledge (MaRK'09)Workshop is in conjunction with the 17th IEEE Requirements Engineering Conference Atlanta, USA - September 1st, 2009 (http://www.re09.org/)

Research has shown that capturing and sharing of tacit knowledge about requirements enhances re-use, enables traceability, supports requirement evolution and improves collaboration between participants in distributed projects. Adding to this, recent results have shown that rationale approaches could be effectively used to manage product line variability and could enhance the longevity of software systems. From an industrial perspective, to accept a requirement, this is critical to know why the requirement is required and in which project context is the requirement needed. These issues are often discussed in telephone calls and emails, which makes it difficult to maintain and share the information during the life of a requirement.

In the age of agile methodologies and with the increasing distribution, scale and complexity of development projects, the need for managing requirements knowledge continues to increase. The major constraint is to have a lightweight, usable, intelligent, contextualized and personalized capturing and sharing approach. 

Requirement engineering infrastructures should capture and formalize tacit knowledge and stakeholders should be able to answer questions about requirements at any time, using their common vocabularies. Recent advancements in knowledge management such as ontological engineering, mining techniques, semantic annotation as well as search and assistance tools brings new potentials for the requirements engineering community. Therefore, this workshop discusses the issues, approaches and tools regarding capturing, externalizing, accessing, sharing and maintaining of knowledge in requirements engineering

The topics of the workshop include:

• Approaches for knowledge capture and sharing during requirements elicitation, specification, analysis and change management
• Automatic and context-aware capture of problem domain knowledge
• Mining requirements repositories
• Intelligent assistance tools such as semantic search and recommendation on requirements
• Context-awareness tools for supporting requirements elicitation, analysis, traceability and reuse
• Ontology-based requirements and traceability management
• Capture and maintenance of rationale information for volatile and evolving requirements
• Rationale management for variability, product lines and service- oriented architectures
• Empirical studies on advantages and drawbacks of particular knowledge management approaches
• Applying machine learning to requirements engineering

A PDF is available at http://www1.cs.tum.edu/mark09/images/cfp.pdf