<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>” Journal of Systems
and Software</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Design Patterns across the Modeling Process</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jeff Gray</string-name>
          <email>gray@cs.ua.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Computer Science, University of Alabama Tuscaloosa</institution>
          ,
          <addr-line>Alabama</addr-line>
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>1994</year>
      </pub-date>
      <volume>13</volume>
      <issue>2</issue>
      <abstract>
        <p>Modeling has always served as a descriptive means for documenting design patterns. For example, the Gang of Four (GoF) [1] book used a pre-UML graphical notation for describing the participants and their collaborations across design patterns. However, numerous researchers are also understanding the complimentary role that design patterns can offer to the modeling process. As observed by the PAME Call for Papers, design patterns can be found across many topics related to model-driven engineering. In this talk, we will survey some of the works used in applying patterns to the earliest phases of modeling that are related to metamodel creation [2, 3], which help to document best practices of modeling language definition. We will also consider the potential benefits of documenting frequently observed patterns in model transformations [4, 5]. There is also great opportunity to catalog various patterns that emerge in refactoring and evolution of modeling assets in the presence of change requests [6, 7, 8]. The talk outlines some of my own work with colleagues in these areas, as well as a summary of work done by others.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1.
4.
5.
6.
7.</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>