Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/zhenxiangba/zhenxiangba.com/public_html/phproxy-improved-master/index.php on line 456
-->
ASE-LP Home Page
JICSLP'98 Post-Conference Workshop on
Automated Software Engineering and Logic Programming
The meeting was conducted as a round-table discussion by Kung-Kiu
Lau in an informal manner. A brief summary follows.
Themes and Goals
The discussion was focused on 2 themes:
automated software engineering and logic programming (LP)
relations/links between the conferences LOPSTR (Logic-based
Program Synthesis and Transformation, formerly Logic Program
Synthesis and Transformation) and ASE (IEEE
International Automated Software Engineering Conference - formerly
Knowledge-based Software Engineering)
Whilst the first theme was mainly intended for the LOPSTR people present
(who were the majority), the second theme benefited from the
presence of Tim Kremann, Brad Martin and Steven Roach, who are
associated with the ASE conference. The ASE/LOPSTR theme took up most
of the discussion time, since the ase/lp theme was too broad an
issue to tackle in such a brief time.
On the automated software engineering/LP theme, it was generally
agreed that LP,
in particular
its relevance for Software Engineering (SE), is somewhat
misunderstood by the SE community. It was also agreed that the LP
community should identify more clearly the role of lp in the Software
Life Cyle. On the whole, the LP community has so far failed to address SE properly,
despite the Practical Applications conferences.
Both LOPSTR and ASE aim to take up the challenge of making an impact
on mainstream SE. LOPSTR will continue to place its emphasis on
logic-based techniques, while ASE will take a more general Formal
Methods stance but with automation as its key objective. Both ASE and
LOPSTR agree that the way to achieve this goal is to study relevant theory,
design practical techniques and tools, and conduct suitable empirical
studies.
Where we are now (ASE and LOPSTR)
A brief survey of LOPSTR and ASE, and a comparison between the two,
concluded that:
both LOPSTR and ASE tend to concentrate on very narrow
theoretical perspectives, and tend to use only toy examples (althouh
ASE does have some large examples).
ASE has some real applications and systems (KIDS, Amphion,
Specware, Planware). LOPSTR at
present has no real applications/systems, though the potential is there.
What we should do (ASE and LOPSTR)
It was agreed that it would be desirable for ASE and LOPSTR to
encourage their respective communities to submit papers to
each other's conferences
encourage invitations to each other to
present tutorials at each other's conferences
select suitable PCs in order to ensure a
balance between theoretical and practical/empirical papers, so that
papers will be relevant to ase in general
co-locate when and if possible.
What LOPSTR should do
On top of these, the LOPSTR people present also agreed that
the LOPSTR home page should be improved, with a clear mission
statement on LOPSTR's 3 main goals:
to study relevant theory for SE
to emphasise engineering aspects of proposed methods
to demonstrate relevance of theory and proposed methods to SE