| |||||||||||||
SHARK 2011 : Sixth Workshop on SHAring and Reusing architectural KnowledgeConference Series : Sharing and Reusing Architectural Knowledge | |||||||||||||
Link: http://www.shark-workshop.org/ | |||||||||||||
| |||||||||||||
Call For Papers | |||||||||||||
--------------------------------------------------------------------------- SHARK 2011 Sixth Workshop on SHAring and Reusing architectural Knowledge (SHARK) www.shark-workshop.org (http://www.shark-workshop.org) In conjunction with the 33rd Int. Conf. on Software Engineering (ICSE 2011) http://2011.icse-conferences.org Waikiki, Honolulu, Hawaii, May 21-28, 2011 --------------------------------------------------------------------------- Important Dates: 21st January 2011 - paper submission 10th February 2011 - notification of acceptance 10th March 2011 - camera-ready 24th May 2011 - workshop --------------------------------------------------------------------------- Workshop theme and goals ------------------------ SHARK focuses on current and emerging methods, languages, notations, technologies and tools to extract, represent, share, use and re-use architectural knowledge. Architectural Knowledge (AK) is the integrated representation of the software architecture of a software-intensive system (or a family of systems), the architectural design decisions, and the external context/environment. It is recognized as the means for architecture governance; it facilitates and supports collaboration and the transfer of expertise. In this sixth SHARK edition we will investigate the approaches for AK personalization, where knowledge is not codified through templates or annotations, but it is exchanged through the discussion between the different stakeholders. Therefore, the emphasis does not lie on resource-intensive documentation but on lightweight, just-in-time conversations facilitated by 'knowledge yellow pages' (who knows what). The AK community has not explored AK personalization in depth, even though it has acknowledged its value as a viable approach. In good tradition, SHARK aims to bring together researchers and practitioners that are interested in sharing and reusing architectural knowledge. The workshop will kick-start with short position statements from the paper authors. The main focus will be on fostering creative discussion between the participants, on specific themes. Attendance will be limited to a maximum of 30 participants. Topics of the workshop include but are not limited to: * Types of architectural knowledge in industrial settings * Notations and languages to model or visualize architectural knowledge; use of viewpoints and ADL to transfer AK * Ontologies, domain models and meta-models for architectural knowledge * Communicating, sharing and using architectural knowledge approaches and case studies, especially in an industrial setting. * Tools to extract, visualize, share or use architectural knowledge * Evolution of architectural knowledge * Sharing architectural knowledge in the context of SOA or MDE * Architectural knowledge in Global Software Engineering * Communicating architectural knowledge in open, inner and private communities * Sharing architectural knowledge in agile development projects * Architectural knowledge for requirements engineering * Traceability between requirements, architectural design decisions and architectural solutions (e.g. patterns, tactics, reference architectures) * Architectural knowledge in the process of architecting * AK reasoning techniques * Methods and tools for AK personalization * Hybrid approaches: making the best of both personalization and codification * Industrial case studies of AK personalization * Applying knowledge management theory on knowledge personalization Workshop Organizers: -------------------- Patricia Lago, VU University Amsterdam, The Netherlands Paris Avgeriou, University of Groningen, The Netherlands Philippe Kruchten, University of British Columbia, Canada Program committee ----------------- Pierre America, Philips Research, Netherlands M. Ali Babar, IT University of Copenhagen, Denmark Remco de Boer, ArchiXL, Netherlands Janet Burge, Miami University, USA Jan Bosch, Intuit, Mountain View, California Rafael Capilla, Universidad Rey Juan Carlos, Spain Paul Clements, Software Engineering Institute, USA Torgeir Dingsoyr, Sintef, Trondheim, Norway Peter Eeles, IBM, UK Bart van den Hooff, VU University Amsterdam, Netherlands Rich Hilliard, independent consultant, USA Anton Jansen, ABB research, Sweden Kai Koskimies, Tampere University of Technology, Finland Peng Liang, Wuhan University, China Ivan Mistrik, independent consultant, Germany Henry Muccini, University of L'Aquila, Italy Eltjo Poort, Logica, Netherlands Antony Tang, Swinburne University of Technology, Australia Hans van Vliet, VU University Amsterdam, Netherlands Eoin Woods, BlackRock, UK Uwe Zdun, University of Vienna, Austria Olaf Zimmermann, IBM Research, Switzerland Guidelines for Submission ------------------------- We are soliciting papers in three distinct categories: 1) future trend papers, describing ongoing research, new results, and future trends (maximum 4 pages); 2) research papers describing innovative and significant original research in the field (maximum 8 pages); 3) industrial papers describing industrial experience, case studies, challenges, problems and solutions (maximum 8 pages). A special kind of industrial paper submission is an example of a document that shares some kind of architectural knowledge, together with an evaluation of it or a description of the techniques that it uses. Please submit your paper online at the ICSE cyberchair site. Submissions should be original and unpublished work. Each submitted paper will undergo a rigorous review process by three members of the Program Committee. All types of papers must conform to the ICSE submission format and guidelines. All accepted papers will appear in the ACM Digital Library. Special issue ------------- Authors of selected papers will be invited to submit their papers to the Journal of Systems and Software www.elsevier.com/locate/jss (http://www.elsevier.com/locate/jss). |
|