WOP:2012/Submission
From Odp
Contents |
Submission Instructions for WOP 2012
This page contains instructions for submitting to WOP 2012. Submission will be possible in the following two categories:
- Research papers (through easychair)
- Patterns (through the ODP portal + extended abstract describing pattern through easychair)
Research Paper Submissions
We invite the submission of original research results related to the focus areas of the workshop. Research papers (maximum 12 pages LNCS style) should present mature work and document established results, or be position papers presenting proposed research directions and novel ideas (maximum 4 pages LNCS style).
Submission guidelines
- Research papers should be no longer than 12 pages, following the Springer LNCS formatting style (see LNCS style templates). Note that papers not adhering to the style guidelines or the maximum page limit will be rejected without review.
- Position papers should be no longer than 4 pages, following the same template.
- Submissions should be in English, and non-native speakers are encouraged to seek assistance from native English speakers to ensure a correct language.
- Submission of the papers should be done through the EasyChair WOP conference site before July 31st 11:59pm (Hawaii time).
Pattern Submissions
Submitting your pattern
- Request an account at the ODP portal, in case you do not have already one. Note that account requests are processed by hand, so do this step with a few days to spare before the submission deadline.
- Go to the ODP portal pattern submission page.
- Submit your pattern by following the instructions, and make sure you enter as much information about your pattern as possible (clarity and completeness of the information will be a review criteria for patterns), i.e. fill out all applicable fields.
- Once created, edit your pattern page (edit tab at the top of the page) and under the "Submit for event" tab enter "WOP:2012".
- Go back to this page and check that your pattern appears in the table below.
- Write a document briefly describing your pattern (maximum 4 pages in LNCS style), and submit this pattern description through EasyChair. Both pattern and pattern description need to be submitted by July 31st 11:59pm (Hawaii time).
- If you are experiencing any problems, or have questions about how to submit patterns, please contact Karl Hammar.
Review Process
Each submission will be reviewed by at least two members of the Pattern PC (in case of disagreement a third reviewer will be assigned). Note that all reviews and discussions of patterns done in ODP portal are public and not anonymous, hence, all visitors of the portal can see the reviews and any subsequent discussion. Your pattern will be reviewed based on the following set of criteria:
- the practical utility and reusability of the pattern by a community,
- the relevance of the problem addressed by the pattern,
- if the pattern encodes some best practice within a community,
- and the completeness and clarity of the pattern submission, i.e., if all fields have been filled and all aspects properly explained.
Accepted patterns have to be improved based on the review comments, i.e., an update of the patterns in the ODP portal is mandatory. Accepted patterns will be presented at the workshop as posters in the pattern session. After the workshop, the patterns may be considered for certification in the ODP portal.
Attending WOP
If accepted, at least one author of each pattern must register for the workshop and attend the workshop poster session to present their pattern. Further instructions on poster size and other practical details will follow after the selection has been finalized. In the case of acceptance of both a pattern and a research paper describing the same pattern, only one registration is necessary but it is expected that you prepare both an oral presentation and a poster.
Current list of received pattern submissions
| SubmittedBy | HasIntent | |
|---|---|---|
| OOPMetrics | IonelVirgilPop | To represent software metrics especially for the purpose of detecting design-flaws in software systems based on these metrics. This is useful for re-engineering the software system., De a reprezenta metricile soft in special in scopul detectarii defectelor de proiectare din sistemele soft pe baza acestor metrici. Acest lucru este folositor pentru reingineria sistemului soft. |
| PeriodicInterval | MariaPoveda MariCarmenSuarezFigueroa |
The goal of this pattern is to represent non-convex intervals where the duration of each internal interval and the duration of the gaps between intervals are constant. These intervals are called periodic intervals within the context of this pattern. |
| Reactor pattern | MonikaSolanki | The remit of the reactor pattern is to enable the modelling of reactive processes that consume inputs and produce outputs under specific environmental conditions and on being triggered by certain events. |
| Standard Enforcer Pattern | MonikaSolanki | The remit of the SEP content pattern is to represent the relation between standards and the processes, operations, activities and services that enforce them, the domains they cater to and the scope of that specific process, operation, activity, service within the context of the domain. |
| Template Instance | CsongorNyulas | The Template Instance pattern proposes a way of reducing the number of reified instances and the related property assertion axioms in an ontology, especially for the cases in which the reified relations are identical for multiple entities. |
