<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     caa a22        4500</leader>
  <controlfield tag="001">477098029</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180405111533.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">170330e19960901xx      s     000 0 fre  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1007/BF02997707</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1007/BF02997707</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">Bézivin</subfield>
   <subfield code="D">Jean</subfield>
   <subfield code="u">Université de Nantes, 2, rue de la Houssinière, F-44072, Nantes Cedex 03, France</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="2">
   <subfield code="a">L'unification des méthodes dans le projet Osmosis</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[Jean Bézivin]</subfield>
  </datafield>
  <datafield tag="246" ind1="0" ind2=" ">
   <subfield code="a">The Osmosis path to method unification</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">The last years have seen the emergence of a number of so-called object-oriented analysis and design methods (ooadm) like class-relation, omt, Shlaer-Mellor, etc. In order to cope with the importance and diversity of these offerings, a strong trend toward unification has recently developed. For the time being, this unification movement has a scope mainly limited to notational aspects. In order to be really useful, it should also apply to the organizational aspects, i.e. not only to formalisms but also to processes. A general life cycle reference model called J3 is proposed here as a possible alternative to conventional schemes, giving rise to a regular organization of processes and products in the software development cycle. Since most of these products are expressed in an object-oriented formalism, their interoperation should be addressed in a general way. Instead of using a class-based meta-notation, we have defined, for that purpose, a minimal knowledge representation kernel called sNets, a specific kind of semantic networks. The J3 organization framework and the sNet core notation are the two main components of the Osmosis workbench. The synergy between these notational and organizational concepts gives rise to an original pilot software production scheme.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">Springer-Verlag, 1996</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Software engineering</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Object oriented method</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Reference model</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Software workshop</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Semantic network</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Knowledge representation</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Génie logiciel</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Méthode orientée objet</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Modèle référence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Atelier logiciel</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Réseau sémantique</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Représentation connaissances</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Annales Des Télécommunications</subfield>
   <subfield code="d">Springer-Verlag</subfield>
   <subfield code="g">51/9-10(1996-09-01), 451-458</subfield>
   <subfield code="x">0003-4347</subfield>
   <subfield code="q">51:9-10&lt;451</subfield>
   <subfield code="1">1996</subfield>
   <subfield code="2">51</subfield>
   <subfield code="o">12243</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1007/BF02997707</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="908" ind1=" " ind2=" ">
   <subfield code="D">1</subfield>
   <subfield code="a">research-article</subfield>
   <subfield code="2">jats</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">856</subfield>
   <subfield code="E">40</subfield>
   <subfield code="u">https://doi.org/10.1007/BF02997707</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">100</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Bézivin</subfield>
   <subfield code="D">Jean</subfield>
   <subfield code="u">Université de Nantes, 2, rue de la Houssinière, F-44072, Nantes Cedex 03, France</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">773</subfield>
   <subfield code="E">0-</subfield>
   <subfield code="t">Annales Des Télécommunications</subfield>
   <subfield code="d">Springer-Verlag</subfield>
   <subfield code="g">51/9-10(1996-09-01), 451-458</subfield>
   <subfield code="x">0003-4347</subfield>
   <subfield code="q">51:9-10&lt;451</subfield>
   <subfield code="1">1996</subfield>
   <subfield code="2">51</subfield>
   <subfield code="o">12243</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">Springer special CC-BY-NC licence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="898" ind1=" " ind2=" ">
   <subfield code="a">BK010053</subfield>
   <subfield code="b">XK010053</subfield>
   <subfield code="c">XK010000</subfield>
  </datafield>
  <datafield tag="949" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="F">NATIONALLICENCE</subfield>
   <subfield code="b">NL-springer</subfield>
  </datafield>
 </record>
</collection>
