|
Requirements
engineering has increasingly become a dominant
activity in systems development—the more we
can generate or outsource design and construction,
the more we need requirements that adequately
reflect the stakeholders' desires and needs.
|
|
The IEEE
International Requirements Engineering conference
is the premier requirements engineering conference,
providing a forum for researchers, practitioners,
educators, and students to present and discuss the
most recent innovations, trends, experiences, and
concerns in the field of requirements engineering.
|
|
|
|
Topics of interest
include, but are not restricted to:
|
|
|
Requirements
elicitation, analysis, documentation,
validation, and verification
|
|
|
Requirements
specification languages, methods,
processes, and tools
|
|
|
Requirements
management, traceability, viewpoints,
prioritization, and negotiation
|
|
|
Modeling
of requirements, goals, and domains
|
|
|
Formal
analysis and verification
|
|
|
Prototyping,
simulation, and animation
|
|
|
Evolution
of requirements over time, product
families, and variability
|
|
|
Relating
requirements to business goals,
architecture, and testing
|
|
|
Social,
cultural, and cognitive factors in
requirements engineering
|
|
|
Domain-specific
problems and solutions in the field of
requirements
|
|
|
Paper
categories
|
|
We invite
submissions of high quality papers in the following
categories:
|
|
Technical
solution papers
|
|
Technical
solution papers present solutions for
requirements-related problems which are novel or
significantly improve existing solutions. A
technical solution paper must include a preliminary
validation of the proposed solution.
Evaluation
criteria: The proposed solution
technique or its application to this kind of
problem must be novel and sound. The author(s) must
provide a preliminary validation of the proposed
solution, for example, a proof-of-concept and/or
sound arguments that the solution technique will
work and that it will scale to real-world-sized
problems. Results must be stated clearly enough so
that the author(s) or others can further validate
them in later research. A technical solution paper
should also be clear about its contributions with
respect to related work by others and to previous
work by the author(s).
Size: A paper
of this category must not exceed 10 pages.
|
|
Scientific
evaluation papers
|
|
Scientific
evaluation papers evaluate existing problem
situations or validate proposed solutions with
scientific means, i.e. by empirical studies,
experiments, case studies, simulations, formal
analyses, mathe¬matical proofs, etc.
Scientific reflection on problems and practices in
industry also falls into this category.
Evaluation
criteria: The topic of the evaluation
presented in the paper as well as its causal or
logical properties must be clearly stated. The
research method must be sound and appropriate. The
research must be novel or, otherwise, the results
must constitute a significant increase of
knowledge. The results must be relevant and/or
(statistically) significant. Furthermore, the
research should be situated in the context of
related work by others and previous work by the
author(s).
Size: A paper
of this category must not exceed 10 pages.
|
|
Industrial
practice and experience papers
|
|
Industrial
practice and experience papers present problems or
challenges encountered in practice, relate success
and failure stories, or report on industrial
practice. The focus is on 'what' and on lessons
learned, not on an in-depth analysis of 'why'.
Otherwise, consider submitting a scientific
evaluation paper.
Evaluation
criteria: The practice must be clearly
described and its context must be given. Readers
should be able to follow easily and to draw
conclusions for their own practice.
Size: A paper
of this category should be 4-6 pages long. It must
not exceed 6 pages.
|
|
Vision
papers
|
|
Vision papers
sketch new ways of looking at things, present
creative new ideas, rethink current notions, etc.
Please note that this is not a forum for research
proposals or immature technical solution
papers.
Evaluation
criteria: A vision paper should be
revealing and thought-provoking, thus providing new
insight for the reader. The presented ideas must be
original and look sound. Papers that only sketch an
idea or propose research on some topic will be
rejected.
Size: A paper
of this category must not exceed 6 pages.
|
|
Originality
|
|
Papers must
describe original work that has not been submitted
to or presented at other forums.
[more]
|
|
Submission
information
|
|
Submissions
will be handled electronically at the RE'06
submission
site. Authors without web access must make
advance arrangements with the Program Chair at
least one week before the deadline.
|
|
Submissions
must be formatted according to the 8.5x11 inch IEEE
CS proceedings format. For downloading instructions
and templates, go to the
Author Forms web
page of the IEEE Computer Society.
|
|
Submission
deadlines
|
|
For the
submission deadlines, see the list of
important
dates.
|
|
Reviewing
|
|
All submissions
will be reviewed by members of the
RE'06
Program Committee according to the criteria
stated above. Based on the reviews and on the
discussion of papers in the program committee, the
RE'06
Program Board will decide which papers to
accept for the conference.
|
|
Papers that do
not conform to the submission instructions will be
rejected without review. In particular, this will
be the case for papers that exceed the size limit,
are obviously out of the scope of the conference,
or clearly do not fit the selected paper category.
In the latter case, the Program Chair will first
try to reclassify a submission to a proper
category.
|
|
Publication of
accepted papers
|
|
Accepted papers
will be published in an IEEE CS Press Conference
Proceedings and will be available in the IEEE CS
Digital Library.
|
|
Other
contributions
|
|
We also invite
proposals for
tutorials,
workshops,
panels,
doctoral
symposium contributions,
posters, and
research
demonstrations.
|
