Ci-dessous, les différences entre deux révisions de la page.
Prochaine révision | Révision précédente Prochaine révision Les deux révisions suivantes | ||
sc_2010 [2010/01/04 18:22] tigli créée |
sc_2010 [2010/01/12 09:07] tigli |
||
---|---|---|---|
Ligne 2: | Ligne 2: | ||
[[http://swcomp2010.appspot.com/ | Site Web]] | [[http://swcomp2010.appspot.com/ | Site Web]] | ||
+ | |||
+ | === Important Dates === | ||
+ | |||
+ | Paper Submission: January 29, 2010 | ||
+ | |||
+ | Acceptance notification: March 24, 2010 | ||
+ | |||
+ | Camera-ready copy: April 21, 2010 | ||
+ | |||
+ | Conference Dates: June 28-July 2, 2010 | ||
+ | |||
+ | === Topics of Interest: === | ||
+ | |||
+ | The SC 2010 program committee seeks original, high quality papers related to Software Composition, such as but not limited to the following: | ||
+ | |||
+ | * Composition and adaptation techniques | ||
+ | * Composition languages, calculi and type systems | ||
+ | * Aspect-oriented software development | ||
+ | * Semantics-based composition and analysis of component systems | ||
+ | * Verification, validation and testing techniques | ||
+ | * Dynamic composition and reconfiguration | ||
+ | * Composition issues in industrial-strength component systems and frameworks | ||
+ | * Composition aspects of service-oriented architectures | ||
+ | * Software composition in pervasive computing environments | ||
+ | * Software composition for the Web (Mashups ...) | ||
+ | * Visual composition environments and tools | ||
+ | * Model-driven composition | ||
+ | * Business process orchestration | ||
+ | * Performance optimization of composite systems | ||
+ | |||
+ | |||
+ | === Submission: === | ||
+ | |||
+ | We solicit high-quality submissions on research results and/or experience (up to 16 pages, LNCS format, including bibliography and figures) describing a technical contribution in depth. Short and position papers are also welcome for the work in progress session (up to 8 pages, LNCS format, including bibliography and figures). Short submissions must concisely capture ongoing work, new ideas, and experiences. | ||
+ | |||
+ | |||
+ | === PLAN : === | ||
+ | |||
+ | * Abstract | ||
+ | * Introduction | ||
+ | * Service for Device Composition | ||
+ | * StateLess versus StateFull service | ||
+ | Statefull service must care about multiple access. | ||
+ | |||
+ | * Synchronous | ||
+ | * Activity Recognition Application | ||
+ | |||
+ | |||
+ | === TITLE : === | ||
+ |