[apologies if you receive multiple copies of this message]
------------------------------------------------------------------

                       CALL FOR PAPERS

       Domain-Specific Languages for Software Engineering
              http://marcel.uni-mb.si/marjan/hicss-34/

     This Minitrack is Part of the Software Technology Track
                     of HICSS-34

            Maui, Hawai'i, January 3-6, 2001


The primary function of programming languages and tools has always been
to make the programmer more effective. Appropriate programming languages
and tools may drastically reduce the costs for building new applications
as well as for maintaining existing ones. It is well known that
programming languages can greatly increase programmer productivity by
allowing the programmer to write high-scalable, generic, readable and
maintainable code. Also, new domain specific languages can be used to
enhance different aspects of software engineering. The development of
these languages is itself a significant software engineering task,
requiring a considerable investment of time and resources.
Domain-specific languages have been used in various domains and these
applications have clearly illustrated the advantages of domain
specific-languages over general purpose languages in areas such as
productivity, reliability, and flexibility. The purpose of the minitrack
is to bring together an international audience of researchers and
practitioners actively involved in the development of languages for
software engineering. It covers a wide range of
domain-specific languages applied on different software engineering
problems. Topics of interest, but not limited to, for this mini-track
are:
- design and implementation of domain-specific languages
- use of domain-specific languages affecting the software engineering
process
- role of domain-specific languages in software engineering
- tools, environments, and techniques needed to support domain-specific
languages

           Important Deadlines in 2000

 A 300-word abstract by April 1
 Feedback to author on abstract by May 1
 Eight copies of the manuscript by June 1
 Notification of accepted papers by August 31
 Camera-ready copies of accepted manuscripts are due by October 1
 Tutorial Proposals by April 1
 Notification of accepted tutorials by May 15

It is not necessary to submit an abstract to the minitrack organiser
before the full paper deadline. However, we would prefer to receive a
short abstract from interested authors to give us advance warning of the
arrival of a full paper.


               Instructions for the Authors

Submit a 300-word abstract to one of the minitrack coordinators by April
1, 2000. The preferred mode of submission is via e-mail.
Feedback on the appropriateness of the abstract will be sent to you by
May 1, 2000. Submit the full manuscript by June 1, 2000. The preferred
mode of submission is via e-mail. Manuscripts should have an abstract
and be 22-25 typewritten, double-spaced pages in length. Papers must not
have been previously presented or published, nor currently submitted for
journal publication.
Each manuscript will be subjected to a rigorous refereeing process.
Individuals interested in refereeing papers should contact the minitrack
coordinators directly.

                     Tutorials

Tutorials will be offered on Tuesday, January 3, 2001. Interested
speakers should submit full-day or half-day proposals to the track
chairman by April 1, 2000. Proposals should include an outline of the
topics to be covered and a short biography.

                 Minitrack organizers

Marjan Mernik
Faculty of Electrical Engineering  and Computer Science
University of Maribor, Slovenia
email:[EMAIL PROTECTED]

Viljem Zumer
Faculty of Electrical Engineering and Computer Science
University of Maribor, Slovenia
email: [EMAIL PROTECTED]

Robert Manderson
School of Computer Science
University of Westminster, UK
email:[EMAIL PROTECTED]


Homepage of the Software Technology Track
  http://cs.unomaha.edu/~rewini/CFP-h34.html
Homepage of the HICSS-34
  http://www.hicss.hawaii.edu/




Reply via email to