Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

00 Opening: Why MaRK


Published on

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

00 Opening: Why MaRK

  1. 1. Managing Requirements Knowledge in conjunction with RE’09 Hans-Jörg Happel , FZI Walid Maalej, TUM Anil Thurimella , Harmann Becker 2nd. International Workshop on
  2. 2. Introduce Yourself in 20 Seconds! <ul><li>Please stand up! </li></ul><ul><li>Your Name </li></ul><ul><li>Your Affiliation </li></ul><ul><li>Your Main Expectation </li></ul>Managing Requirements Knowledge
  3. 3. A Need for a New Community Managing Requirements Knowledge 1 2 3 4 <ul><li>Wi th the semantic web and web 2.0 a new “era” of knowledge management </li></ul><ul><li>Other fields such as design and maintenance have been taking advantages from advancements in knowledge management </li></ul><ul><li>Capturing and sharing tacit knowledge about requirements: </li></ul><ul><ul><li>Enhances reuse </li></ul></ul><ul><ul><li>Supports requirement evolution </li></ul></ul><ul><ul><li>Improves collaboration </li></ul></ul><ul><li>Current RE processes and tools do not give enough room for managing requirements knowledge </li></ul><ul><li>Increasing distribution scale and complexity of RE activities </li></ul>New Challenges Promising Research Results Promising Advances in O ther Fields Status Quo in RE Why MaRK?
  4. 4. MaRK Topics of Interests <ul><li>Approaches for knowledge capture and sharing during requirements elicitation, specification, analysis and change management </li></ul><ul><li>Mining requirements repositories </li></ul><ul><li>Intelligent assistance tools such as semantic search and recommendation on requirements </li></ul><ul><li>Context -awareness tools for supporting requirements elicitation, analysis, traceability and reuse </li></ul><ul><li>Ontology -based requirements and traceability management </li></ul><ul><li>Capture and maintenance of rationale information for volatile and evolving requirements </li></ul><ul><li>Empirical studies on advantages and drawbacks of particular knowledge management approaches </li></ul><ul><li>Applying machine learning to requirements engineering </li></ul><ul><li>Agile and Requirements </li></ul><ul><li>Web 2.0 techniques applied to RE </li></ul>Managing Requirements Knowledge
  5. 5. MaRK’08 Was a Success & Fun! Managing Requirements Knowledge
  6. 6. Some Statistics Managing Requirements Knowledge
  7. 7. Statistics by Country Managing Requirements Knowledge ToDo: Find corrolations between beer consumption and country acceptance rate?
  8. 8. Morning Agenda Managing Requirements Knowledge 9:00 9:20 Opening 9:20 10:30 Session 1: Knowledge Representation and retrieval F Using Defect Reports to Build Requirements Knowledge in Product Lines I Luhmann's slip box - what can we learn from the device for knowledge representation in requirements engineering? F How to Keep Domain Requirements Models Reasonably Sized I The Papyrus tool as an Eclipse UML2-modeling environment for requirements Session Q&A 10:30 11:00 Coffee 11:00 12:00 Session 2: Tacit Knowledge S Making Tacit Requirements Explicit F Capturing, Organizing, and Reusing Knowledge of NFRs: An NFR Patterns Approach S Modeling and Managing Tacit Product Line Requirements Knowledge Session Q&A 12:00 12:40 Session 3: Leightweight Tools / Knowledge Generation I Domain KnowledgeWiki for Requirements Elicitation S On Presuppositions in Requirements
  9. 9. Afternoon Agenda Managing Requirements Knowledge 12:40 14:00 Lunch 14:00 15:00 Session 4: Recommendation Systems S A Machine Learning Approach for Identifying Expert Stakeholders F Towards a Research Agenda for Recommendation Systems in Requirements Engineering S Leveraging Rule Deviations in IT Ecosystems for Implicit Requirements Elicitation Q&A 15:00 15:45 Session 5: Agile and Creativty F Continuous and Collaborative Validation: A Field Study of Requirements Knowledge in Agile S Reasoning on Requirements Knowledge to Support Creativity Q&A 15:45 16:15 Coffee 16:15 17:15 Round discussion table / Open space 17:15 17:40 Summary & closing 19:00 OE Dinner
  10. 10. Feedback Please also fill in the online feedback form
  11. 11. Many Thanks to the Program Committee! <ul><li>Mike Alexander, Seilevel, TX, USA </li></ul><ul><li>Björn Decker, empolis, Germany </li></ul><ul><li>Hans-Jörg Happel, FZI Karlsruhe, Germany </li></ul><ul><li>Jane Cleland-Huang, DePaul University, USA </li></ul><ul><li>Leonid Kof, University of Passau, Germany </li></ul><ul><li>Seok-Won Lee, University of North Carolina, USA </li></ul><ul><li>Walid Maalej, TU Muenchen, Germany </li></ul><ul><li>Gregoris Mentzas, National Technical University of Athens, Greece </li></ul><ul><li>Ivan Mistrik, Independent consultant, Germany </li></ul><ul><li>Bashar Nuseibeh, The Open University, UK </li></ul><ul><li>Barbara Paech, University of Heidelberg, Germany </li></ul><ul><li>Juha Savolainen, Nokia, Finland </li></ul><ul><li>Klaus Schmid, University of Hildesheim, Germany </li></ul><ul><li>Bikram Senguptha, IBM Research, India </li></ul><ul><li>Eric Tsui, Knowledge Management Research Center, Hong Kong </li></ul><ul><li>Anil Kumar Thurimella, Harman Becker, Germany </li></ul><ul><li>Tim Trew, Philips, NXP Semiconductors, Netherlands </li></ul><ul><li>Timo Wolf, Siemens, Germany </li></ul>Managing Requirements Knowledge
  12. 12. Community Portals <ul><ul><li>Scientific portal Aknowledge: Agile Knowledge Sharing, Social Software Engineering </li></ul></ul><ul><ul><li> </li></ul></ul><ul><ul><li>Open source portal on collaboration and knowledge sharing in software engineering </li></ul></ul><ul><ul><li> </li></ul></ul><ul><ul><li>You are welcome to contribute ! </li></ul></ul>Managing Requirements Knowledge
  13. 13. Thank Y ou for Participating! We hope to see you next years at MaRK’ 10 !
  14. 14. Some Related Projects <ul><li>End user in requirements elicitation </li></ul><ul><li>Support of developers during bug tracking through reusing previous experiences </li></ul><ul><li>Decision support in design </li></ul><ul><li>Documentation and maintenance of complex system </li></ul><ul><li>All these project aim at endorcing a leightweight knowledge sharing in software engineering </li></ul>Managing Requirements Knowledge