<?xml version="1.0" standalone="yes"?>
<Paper uid="A88-1004">
  <Title>TIHE PRESENT :SYHPTOH (*PAIN :LOCATION (*BOOY-PART :NAHE *THROAT</Title>
  <Section position="3" start_page="0" end_page="0" type="intro">
    <SectionTitle>
2 Design guidelines
</SectionTitle>
    <Paragraph position="0"> When we designed and implemented the initial SEMSYN generator we tried to base this work on guidelines like the following \[Rfsner 86b\]: * The implemented system should not be confined by its/irst application.</Paragraph>
    <Paragraph position="1"> Since we had only little influence on the format of the output of our partner's parser for Japanese we designed a more general frame language that served as input to our system.</Paragraph>
    <Paragraph position="2"> The generator should be easily extensible and transportable to other applications.</Paragraph>
    <Paragraph position="3"> This gave strong motivation for choosing an object-oriented implementation technique. null The generator should be integrated in an environment of software tools supporting ~every day&amp;quot; work (e.g. testing, debuggi~zg, experimentation) with the system.</Paragraph>
    <Paragraph position="4"> This led to the implementation of a whole system of utilities: e. g. menu-based tools for lexicon update and maintenance or an interactive editor for semantic structures.</Paragraph>
  </Section>
class="xml-element"></Paper>