<!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 />
    <article-meta>
      <title-group>
        <article-title>On Understanding Teaching Modeling in Computer Science as an Ecosystem</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Martin Gogolla University of Bremen</institution>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>-This contribution views teaching modeling as an ecosystem. We identify the factors that make up the ecosystem and establish some relationships between the constituing factors. We discuss some of the factors that need further work and improvement.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>II. NINE FACTORS IN TEACHING MODELING BY EXAMPLE</p>
    </sec>
    <sec id="sec-2">
      <title>We identify nine main dimensions and factors and explain</title>
      <p>them first by naming them and by giving a short, sketchy
example.</p>
      <p>According to the wikipedia an ecosystem is characterized
as follows: An ecosystem is a community of living
organisms (e.g. animals, plants) in conjunction with nonliving
components of the environment (e.g. water, air, soil) interacting
as a system. In an ecosystem there are biotic factors as well
as abiotic factors. An ecosystem is self supporting, and the
components are linked through nutrient cycles and energy
flows. It is a network of interactions among organisms, and
between organisms and their environment that can be of any
size, but usually encompasses limited space.</p>
      <p>Our view on teaching modeling is that of an ecosystem as
well. Let us first turn to the factors (or dimensions as we also
call them) and then to the interplay of the factors. We identify
nine factors due to our subjective view and counting. Thus,
the influencing factors for teaching modeling are manyfold,
and these factors are highly connected.</p>
    </sec>
    <sec id="sec-3">
      <title>Let us go through the nine factors one by one and explain</title>
      <p>them in some more detail.</p>
      <p>Teaching content is a highly important and structured factor.</p>
      <p>There are many modeling techniques like class diagrams or
state charts that may concern model structure or model
behavior; the taught techniques may regard model organisation like
handling of profiles, and the techniques may concern model
relationships, in particular model transformations. Model
qualities and model characteristics are captured by general,
admittedly vague notions like classification, abstraction,
structuredness, appropriateness, clearness, and understandability (of a
model) as well as by terms like verifiability and executability.</p>
      <p>Modeling styles can be caught by contrastive pairs as
textual..graphical, universal..domain-specific or informal..formal.</p>
      <p>
        The teaching medium may be a blackboard or a sheet of
paper. It may be a combination of a modeling language used
in a particular tool like UML [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] or OCL [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] in MagicDraw,
USE [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], Umple [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], EMFtoCSP [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] or ATL [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. The
teaching medium may also be some non-mainstream modeling
tool like Excel, PowerPoint, or yEd, or the medium could be
a programming or database language like Java or SQL.
(1) Teaching content which has three subfactors: the taught Demonstrations in form of examples or case studies are
modeling technique; example: use case modeling; the essential for teaching. The spectrums may be classified
taught model qualities; example: abstraction; the used by contrastive pairs like tiny..large, vague..detailed,
modeling style; example: a domain-specific modeling concrete..abstract, positive..negative, academic..industrial.
style. Demonstrations may be classified by their suitability for the
(2) Used teaching medium; example: Excel. taught modeling technique. Demonstration cases can come
(3) The demonstrations employed for teaching; example: an from different software development stages and refinement
industrial case study. levels.
(4) The actors involved in teaching; example: a tutor. Actors in teaching may take roles as teacher, lecturer,
(5) Teaching timing; example: teaching undergraduates in researcher or tutor in a pro-active position or student in the
the third year. first place in a more reactive position. One may consider
(6) Teaching form; example: a student project with 10 ECTS project level-specific roles as programmer or designer and also
points. more organisational positions as examination administrators,
(7) Teaching style; example: a style involving gamification. technicians or curriculum deans.
      </p>
    </sec>
    <sec id="sec-4">
      <title>Timing in teaching classically decides on wether a teaching</title>
      <p>
        activity concerns undergraduate, graduate, or phd students,
but one could also consider education for professionals in
order to improve skills needed in the job [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]; teaching
modeling to professionals is currently under-represented in the
teaching modeling literatue, like e.g. the MODELS Educators
Symposium. The author has longer experience in teaching
the university courses ‘Basics of Databases’ for the 2nd
year, ‘Database Systems’ for the 3rd year, and ‘Design of
Information Systems’ for the 4th and 5th year (in the context of
university Computer Science curricula like Diploma, Bachelor,
and Master).
      </p>
      <p>As the teaching form one can distinguish between lectures,
exercises, courses, seminars, homeworks, projects, and various
forms of theses in Bachelor, Master, and PhD curricula.
Regarding PhD students one may even consider a research
paper as a teaching form trying to transport methods for
developing ideas and presentations from a teacher to a student.</p>
      <p>The teaching style may vary from a classical
teacher-infront option to group-work-oriented styles. Contrastive pairs
as traditional..gamified or research-oriented..trainee-oriented
styles are important. A research-oriented style views teaching
in the first place as representing research results. A
traineeoriented style looks at teaching from the perspective of the
trainee and tries to satisfy the trainee’s needs respecting and
taking into account the trainee’s abilities in the first place.</p>
      <p>Teaching modeling does not only involve the software
engineering realm, but many other Computer Science areas
teach modeling in some form, e.g. models are used in
teaching programming languages, information systems, networks,
theoretical computer science, or in artificial intelligence.</p>
      <p>Teaching always takes place in a certain environment in
which a curriculum performing institution is located. There
are always related curricula and related institutions at the
teaching institution and in the geographical neighborhood.
The present teaching colleagues and laws expressing curricula
frame requirements also take serious influence.</p>
    </sec>
    <sec id="sec-5">
      <title>IV. RELATIONSHIPS BETWEEN TEACHING MODELING</title>
      <p>FACTORS</p>
      <p>Figure 1 graphically places the discussed factors and
dimensions on a circle that allows to establish relationship
connections in the inner part of the circle being able to link a
single relationship with many factors.</p>
      <p>The figure shows prototypically two relationship
connections. There are much more similar relationships than the
shown ones. It is open future work to explore what the most
important relationships are.</p>
      <p>The two shown relationships are Teaching-Unit-Core and
Teaching-Unit-Neighborhood. Teaching-Unit-Core connects
content, medium, demonstrations, and form. It establishes
essentials of what makes up a traditional teaching unit.
TeachingUnit-Neighborhood connects actors, areas, and environment.
It brings together the neighborhood of a teaching unit, in
particular it puts emphasis on the fact that teaching actors
are connected to related Computer Science areas.</p>
    </sec>
    <sec id="sec-6">
      <title>A possible ‘know-how flow’ relationship (similar to the en</title>
      <p>ergy flow in a natural, biotic ecosystem) that could be added to
the figure is a reflexive relationship on actors because a student
can become a phd student who can become a researcher who
can become a lecturer teaching again to a student: a
‘knowhow flow’ in the teaching modeling ecosystem.</p>
    </sec>
    <sec id="sec-7">
      <title>V. FACTORS NEEDING ATTENTION AND IMPROVEMENT</title>
    </sec>
    <sec id="sec-8">
      <title>We here postulate a working thesis that there are currently six factors that need special attention and improvement: Content (in particular model qualities), demonstrations, actors, timing, areas, and environment.</title>
      <p>Fig. 2. Attempting to exemplify the process for finding abstractions.</p>
      <p>
        The first factor needing improvement is ‘Content’. Content
is about ‘Model qualities and characteristics’ concentrating on
notions like abstraction, classification, executability,
verifiability, and appropriateness. We think that modeling currently
underestimates the role of ‘traditional’ modeling languages
like flowcharts, automata, ER modeling, first order predicate
calculus, or graphs. The modeling community puts the
emphasis on ‘modern’ modeling languages (e.g. UML, OCL,
SysML, EMF, ATL, QVT). And the focus is on teaching
techniques, not on teaching model qualities like abstraction
or classification. It is much easier to teach techniques than
to teach qualities. A qualitiy is something that you cannot
take into your hands. Figure 2 is an attempt to explain what
teaching ‘abstraction’ basically looks like. The lower part
shows the system that needs to be handled and to be abstracted
from. The upper part shows different ways how this abstraction
can be done: by shape, by color, by coordinate. However in the
moment a teacher presents these abstracting solution options,
the teacher has done already the creative part of the abstraction
process, and the students could not look into the teachers head
to see how this process of finding the abstractions was done.
Finding abstractions is hard to teach! [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] Another point for
improvement concerns the teaching characteristics: models in
their representing medium should give feedback to students
with respect to verifiable or measurable qualities, in particular
in terms of executing and analysing models. Modeling tools
should give more feedback in terms of executing typical
modeling scenarios or analyzing essential model properties
like consistency.
      </p>
      <p>
        The second factor needing improvement is
‘Demonstrations’. Good demonstrations for abstract classes (in the
technical sense) covering structure (attributes and operations)
as well as behavior (e.g. operation contracts and protocol
state machines) could realize the demand for teaching the
principles of abstraction. Furthermore, demonstration cases at
different development stages and refinement levels should not
serve only for presentation of perfect, non-developing models.
The discusssion of development steps and their rationals by
presenting models at various levels of detail could benefit
teaching modeling. Also negative examples that show how
students should not model have to be taken into account [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
      </p>
      <p>The third factor needing improvement is ‘Actors’. There
is the typical teaching researcher that presents newest results
and tools. But for teaching models we would like to see
more professional teachers that present material from (neutral,
not self-authored) professional textbooks in a professional
way. Teaching is typically done from our research perspective
through teaching our own research results or at least by
considering material that leads to our results because as researchers
we are interested in advancing our research results. This
research-oriented teaching method should be complemented
by trainee-oriented teaching methods that help students in a
way they understand and that are inline with their abilities.</p>
      <p>The fourth factor needing improvement or at least discussion
is ‘Timing’. To bring up a very simple question: could
modeling be taught before programming is taught? Modeling comes
in curricula quite late, and thus students often use modeling
techniques as a way of ‘documenting the code’. So what would
happen if we ban programming from the first year of Computer
Science education and teach modeling instead?</p>
      <p>The fifth factor needing improvement is ‘Areas’. As
mentioned above, modeling is done in many, if not all areas of
Computer Science, and not only in software engineering. The
identification of confederate Computer Science areas who have
interest in modeling and their integration and establishing a
connection to our field is worthwhile. The modeling
community looks from the outside sometimes like to re-invent the
wheel. Identification of partners and confederates and relating
‘their’ modeling to our view on modeling would be a fruitful
task.</p>
      <p>The sixth factor needing improvement is ‘Environment’.
As part of the environment one can regard the MODELS
conference and its internal structuring. The MODELS
Educators Symposium and the MODELS Tutorials are separated,
non-communicating events at MODELS. There is no common
strategy or plan for these events. Tutorials could be a place
for MODEL education and teaching, with concepts being
developed hand in hand from both MODELS events. For
example, ‘bridge’ tutorials lying thematically between other
Computer Science areas and core modeling techniques could
establish connections. One could also discuss to systematically
offer basic modeling tutorials, not only specialized tutorials on
newest research directions and tools.</p>
      <p>Figure 3 displays the six factors that in our view need
improvement and surveys the items to be worked on.</p>
    </sec>
    <sec id="sec-9">
      <title>VI. CONCLUSION</title>
    </sec>
    <sec id="sec-10">
      <title>This contribution has identified the factors that make up a</title>
      <p>‘teaching modeling’ ecosystem. It has opened the option to
establish relationships between the constituing factors. Much
more workon identifying the relationships is needed. Lastly
we have discussed some of the factors that need further work
and improvement.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J. E.</given-names>
            <surname>Rumbaugh</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Jacobson</surname>
          </string-name>
          , and
          <string-name>
            <given-names>G.</given-names>
            <surname>Booch</surname>
          </string-name>
          ,
          <source>The Unified Modeling Language Reference Manuel - Covers UML 2</source>
          .0,
          <string-name>
            <given-names>Second</given-names>
            <surname>Edition</surname>
          </string-name>
          . AddisonWesley,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>J.</given-names>
            <surname>Warmer</surname>
          </string-name>
          and
          <string-name>
            <given-names>A.</given-names>
            <surname>Kleppe</surname>
          </string-name>
          ,
          <article-title>The Object Constraint Language: Getting Your Models Ready for MDA</article-title>
          . Reading/MA: Addison-Wesley,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>M.</given-names>
            <surname>Gogolla</surname>
          </string-name>
          ,
          <string-name>
            <surname>F.</surname>
          </string-name>
          <article-title>Bu¨ttner, and</article-title>
          <string-name>
            <given-names>M.</given-names>
            <surname>Richters</surname>
          </string-name>
          , “
          <article-title>USE: A UML-Based Specification Environment for Validating UML</article-title>
          and OCL,”
          <source>Science of Computer Programming</source>
          , vol.
          <volume>69</volume>
          , pp.
          <fpage>27</fpage>
          -
          <lpage>34</lpage>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M.</given-names>
            <surname>Gogolla</surname>
          </string-name>
          and
          <string-name>
            <given-names>F.</given-names>
            <surname>Hilken</surname>
          </string-name>
          , “
          <article-title>Model Validation and Verification Options in a Contemporary UML and OCL Analysis Tool,”</article-title>
          <source>in Proc. Modellierung</source>
          (MODELLIERUNG'
          <year>2016</year>
          ),
          <string-name>
            <given-names>A.</given-names>
            <surname>Oberweis</surname>
          </string-name>
          and
          <string-name>
            <given-names>R.</given-names>
            <surname>Reussner</surname>
          </string-name>
          , Eds. GI, LNI
          <volume>254</volume>
          ,
          <year>2016</year>
          , pp.
          <fpage>203</fpage>
          -
          <lpage>218</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>T. C.</given-names>
            <surname>Lethbridge</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Abdelzad</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. H.</given-names>
            <surname>Orabi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. H.</given-names>
            <surname>Orabi</surname>
          </string-name>
          , and
          <string-name>
            <given-names>O.</given-names>
            <surname>Adesina</surname>
          </string-name>
          , “
          <article-title>Merging Modeling and Programming Using Umple,” in Leveraging Applications of Formal Methods</article-title>
          ,
          <source>Verification and Validation: Proc. 7th Int. Symposium ISoLA</source>
          <year>2016</year>
          ,
          <article-title>ser</article-title>
          . LNCS 9953,
          <string-name>
            <given-names>T.</given-names>
            <surname>Margaria</surname>
          </string-name>
          and
          <string-name>
            <given-names>B.</given-names>
            <surname>Steffen</surname>
          </string-name>
          , Eds.,
          <year>2016</year>
          , pp.
          <fpage>187</fpage>
          -
          <lpage>197</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>C. A.</given-names>
            <surname>Gonza</surname>
          </string-name>
          ´lez, F. Bu¨ttner, R. Clariso´, and
          <string-name>
            <given-names>J.</given-names>
            <surname>Cabot</surname>
          </string-name>
          , “
          <article-title>EMFtoCSP: A Tool for the Lightweight Verification of EMF Models,”</article-title>
          <source>in Proc. 1st Int. Workshop Formal Methods in Software Engineering</source>
          ,
          <year>2012</year>
          , pp.
          <fpage>44</fpage>
          -
          <lpage>50</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>F.</given-names>
            <surname>Jouault</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Allilaire</surname>
          </string-name>
          , J. Be´zivin, and I. Kurtev, “ATL:
          <article-title>A model transformation tool,”</article-title>
          <source>Sci. Comput. Program.</source>
          , vol.
          <volume>72</volume>
          , no.
          <issue>1-2</issue>
          , pp.
          <fpage>31</fpage>
          -
          <lpage>39</lpage>
          ,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>D.</given-names>
            <surname>Ratiu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Pech</surname>
          </string-name>
          , and
          <string-name>
            <given-names>K.</given-names>
            <surname>Dummann</surname>
          </string-name>
          , “
          <article-title>Experiences with Teaching MPS in Industry - Towards Bringing Domain Specific Languages Closer to Practice,”</article-title>
          <source>in Proc. 20th Int. Conf. Model Driven Engineering Languages and Systems</source>
          (MoDELS'
          <year>2017</year>
          ). IEEE,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>M.</given-names>
            <surname>Simonot</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Homps</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Bonnot</surname>
          </string-name>
          , “
          <article-title>Teaching Abstraction in Mathematics and Computer Science - A Computer-supported Approach with Alloy,”</article-title>
          <source>in Proc. 4th Int</source>
          . Conference Computer Supported Education,
          <string-name>
            <given-names>M.</given-names>
            <surname>Helfert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. J.</given-names>
            <surname>Martins</surname>
          </string-name>
          , and J. Cordeiro, Eds.
          <source>SciTePress</source>
          ,
          <year>2012</year>
          , pp.
          <fpage>239</fpage>
          -
          <lpage>245</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>R. F.</given-names>
            <surname>Paige</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F. A. C.</given-names>
            <surname>Polack</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. S.</given-names>
            <surname>Kolovos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L. M.</given-names>
            <surname>Rose</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N. D.</given-names>
            <surname>Matragkas</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J. R.</given-names>
            <surname>Williams</surname>
          </string-name>
          , “Bad Modelling Teaching Practices,”
          <source>in Proc. ACM/IEEE MODELS 2017 Educators Symposium</source>
          , ser. CEUR Workshop Proceedings,
          <string-name>
            <given-names>B.</given-names>
            <surname>Demuth</surname>
          </string-name>
          and
          <string-name>
            <given-names>D. R.</given-names>
            <surname>Stikkolorum</surname>
          </string-name>
          , Eds., vol.
          <volume>1346</volume>
          . CEUR-WS.org,
          <year>2014</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>12</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>