A Cooperative Petri Net Editor
Identifieur interne : 002D30 ( Istex/Curation ); précédent : 002D29; suivant : 002D31A Cooperative Petri Net Editor
Auteurs : R. Bastide ; C. Lakos [Australie] ; P. Palanque [France]Source :
- Lecture Notes in Computer Science [ 0302-9743 ] ; 2001.
Descripteurs français
- Wicri :
- topic : étude de cas, Logiciel.
English descriptors
- KwdEn :
- Agha, Appropriate command, Australia introduction, Basic requirements, Bastide, Berlin heidelberg, Case study, Concurrency, Control interactions, Cooperative editing, Cooperative petri, Cooperative work, Cscw, Current members, Deletion, Editing, Editing privileges, Editing session, Editing sessions, Editing software, Encapsulation, Example system, Formal approaches, Formal model, Formalism, Graphical elements, Groupware, Hardware logic designs, Hierarchical, Hierarchical diagrams, Lakos, Lncs, Necessary network communications, Objectoriented, Objectoriented design methodology, Other forms, Other ownership, Other users, Palanque, Particular user, Particular workstation, Petri, Petri nets, Precise aspect, Real time, Reasonable size, Requirements engineering, Several users, Simple coordination protocol, Software, Software architecture, Standard example, Subcomponents, Synchronous groupware, Technical details, User, Various users, Work products, Workstation, Wysiwis.
- Teeft :
- Agha, Appropriate command, Australia introduction, Basic requirements, Bastide, Berlin heidelberg, Case study, Concurrency, Control interactions, Cooperative editing, Cooperative petri, Cooperative work, Cscw, Current members, Deletion, Editing, Editing privileges, Editing session, Editing sessions, Editing software, Encapsulation, Example system, Formal approaches, Formal model, Formalism, Graphical elements, Groupware, Hardware logic designs, Hierarchical, Hierarchical diagrams, Lakos, Lncs, Necessary network communications, Objectoriented, Objectoriented design methodology, Other forms, Other ownership, Other users, Palanque, Particular user, Particular workstation, Petri, Petri nets, Precise aspect, Real time, Reasonable size, Requirements engineering, Several users, Simple coordination protocol, Software, Software architecture, Standard example, Subcomponents, Synchronous groupware, Technical details, User, Various users, Work products, Workstation, Wysiwis.
Abstract
Abstract: This case study presents a standard example for evaluating formal specification approaches that combine a formal model of concurrency (such as Petri nets) with the object-oriented approach. You are expected to exercise your formalism of choice on this problem in order to demonstrate how well it deals with a system of reasonable size. We describe how the structure of a problem can be modeled in a formalism and how component reuse can be incorporated. It is desirable to highlight or emphasize the way that the structure of the problem can be modeled in your formalism, and the way that reuse of components can be incorporated.
Url:
DOI: 10.1007/3-540-45397-0_23
Links toward previous steps (curation, corpus...)
- to stream Istex, to step Corpus: Pour aller vers cette notice dans l'étape Curation :002D30
Links to Exploration step
ISTEX:F06DB32940DAF3AED43BAF8369CA7FCFAF03628BLe document en format XML
<record><TEI wicri:istexFullTextTei="biblStruct"><teiHeader><fileDesc><titleStmt><title xml:lang="en">A Cooperative Petri Net Editor</title>
<author><name sortKey="Bastide, R" sort="Bastide, R" uniqKey="Bastide R" first="R." last="Bastide">R. Bastide</name>
</author>
<author><name sortKey="Lakos, C" sort="Lakos, C" uniqKey="Lakos C" first="C." last="Lakos">C. Lakos</name>
<affiliation wicri:level="1"><mods:affiliation>University of Tasmania, Australia</mods:affiliation>
<country xml:lang="fr">Australie</country>
<wicri:regionArea>University of Tasmania</wicri:regionArea>
</affiliation>
</author>
<author><name sortKey="Palanque, P" sort="Palanque, P" uniqKey="Palanque P" first="P." last="Palanque">P. Palanque</name>
<affiliation wicri:level="1"><mods:affiliation>University of Toulouse I, France</mods:affiliation>
<country xml:lang="fr">France</country>
<wicri:regionArea>University of Toulouse I</wicri:regionArea>
</affiliation>
</author>
</titleStmt>
<publicationStmt><idno type="wicri:source">ISTEX</idno>
<idno type="RBID">ISTEX:F06DB32940DAF3AED43BAF8369CA7FCFAF03628B</idno>
<date when="2001" year="2001">2001</date>
<idno type="doi">10.1007/3-540-45397-0_23</idno>
<idno type="url">https://api.istex.fr/document/F06DB32940DAF3AED43BAF8369CA7FCFAF03628B/fulltext/pdf</idno>
<idno type="wicri:Area/Istex/Corpus">002D30</idno>
<idno type="wicri:explorRef" wicri:stream="Istex" wicri:step="Corpus" wicri:corpus="ISTEX">002D30</idno>
<idno type="wicri:Area/Istex/Curation">002D30</idno>
</publicationStmt>
<sourceDesc><biblStruct><analytic><title level="a" type="main" xml:lang="en">A Cooperative Petri Net Editor</title>
<author><name sortKey="Bastide, R" sort="Bastide, R" uniqKey="Bastide R" first="R." last="Bastide">R. Bastide</name>
</author>
<author><name sortKey="Lakos, C" sort="Lakos, C" uniqKey="Lakos C" first="C." last="Lakos">C. Lakos</name>
<affiliation wicri:level="1"><mods:affiliation>University of Tasmania, Australia</mods:affiliation>
<country xml:lang="fr">Australie</country>
<wicri:regionArea>University of Tasmania</wicri:regionArea>
</affiliation>
</author>
<author><name sortKey="Palanque, P" sort="Palanque, P" uniqKey="Palanque P" first="P." last="Palanque">P. Palanque</name>
<affiliation wicri:level="1"><mods:affiliation>University of Toulouse I, France</mods:affiliation>
<country xml:lang="fr">France</country>
<wicri:regionArea>University of Toulouse I</wicri:regionArea>
</affiliation>
</author>
</analytic>
<monogr></monogr>
<series><title level="s">Lecture Notes in Computer Science</title>
<imprint><date>2001</date>
</imprint>
<idno type="ISSN">0302-9743</idno>
<idno type="ISSN">0302-9743</idno>
</series>
</biblStruct>
</sourceDesc>
<seriesStmt><idno type="ISSN">0302-9743</idno>
</seriesStmt>
</fileDesc>
<profileDesc><textClass><keywords scheme="KwdEn" xml:lang="en"><term>Agha</term>
<term>Appropriate command</term>
<term>Australia introduction</term>
<term>Basic requirements</term>
<term>Bastide</term>
<term>Berlin heidelberg</term>
<term>Case study</term>
<term>Concurrency</term>
<term>Control interactions</term>
<term>Cooperative editing</term>
<term>Cooperative petri</term>
<term>Cooperative work</term>
<term>Cscw</term>
<term>Current members</term>
<term>Deletion</term>
<term>Editing</term>
<term>Editing privileges</term>
<term>Editing session</term>
<term>Editing sessions</term>
<term>Editing software</term>
<term>Encapsulation</term>
<term>Example system</term>
<term>Formal approaches</term>
<term>Formal model</term>
<term>Formalism</term>
<term>Graphical elements</term>
<term>Groupware</term>
<term>Hardware logic designs</term>
<term>Hierarchical</term>
<term>Hierarchical diagrams</term>
<term>Lakos</term>
<term>Lncs</term>
<term>Necessary network communications</term>
<term>Objectoriented</term>
<term>Objectoriented design methodology</term>
<term>Other forms</term>
<term>Other ownership</term>
<term>Other users</term>
<term>Palanque</term>
<term>Particular user</term>
<term>Particular workstation</term>
<term>Petri</term>
<term>Petri nets</term>
<term>Precise aspect</term>
<term>Real time</term>
<term>Reasonable size</term>
<term>Requirements engineering</term>
<term>Several users</term>
<term>Simple coordination protocol</term>
<term>Software</term>
<term>Software architecture</term>
<term>Standard example</term>
<term>Subcomponents</term>
<term>Synchronous groupware</term>
<term>Technical details</term>
<term>User</term>
<term>Various users</term>
<term>Work products</term>
<term>Workstation</term>
<term>Wysiwis</term>
</keywords>
<keywords scheme="Teeft" xml:lang="en"><term>Agha</term>
<term>Appropriate command</term>
<term>Australia introduction</term>
<term>Basic requirements</term>
<term>Bastide</term>
<term>Berlin heidelberg</term>
<term>Case study</term>
<term>Concurrency</term>
<term>Control interactions</term>
<term>Cooperative editing</term>
<term>Cooperative petri</term>
<term>Cooperative work</term>
<term>Cscw</term>
<term>Current members</term>
<term>Deletion</term>
<term>Editing</term>
<term>Editing privileges</term>
<term>Editing session</term>
<term>Editing sessions</term>
<term>Editing software</term>
<term>Encapsulation</term>
<term>Example system</term>
<term>Formal approaches</term>
<term>Formal model</term>
<term>Formalism</term>
<term>Graphical elements</term>
<term>Groupware</term>
<term>Hardware logic designs</term>
<term>Hierarchical</term>
<term>Hierarchical diagrams</term>
<term>Lakos</term>
<term>Lncs</term>
<term>Necessary network communications</term>
<term>Objectoriented</term>
<term>Objectoriented design methodology</term>
<term>Other forms</term>
<term>Other ownership</term>
<term>Other users</term>
<term>Palanque</term>
<term>Particular user</term>
<term>Particular workstation</term>
<term>Petri</term>
<term>Petri nets</term>
<term>Precise aspect</term>
<term>Real time</term>
<term>Reasonable size</term>
<term>Requirements engineering</term>
<term>Several users</term>
<term>Simple coordination protocol</term>
<term>Software</term>
<term>Software architecture</term>
<term>Standard example</term>
<term>Subcomponents</term>
<term>Synchronous groupware</term>
<term>Technical details</term>
<term>User</term>
<term>Various users</term>
<term>Work products</term>
<term>Workstation</term>
<term>Wysiwis</term>
</keywords>
<keywords scheme="Wicri" type="topic" xml:lang="fr"><term>étude de cas</term>
<term>Logiciel</term>
</keywords>
</textClass>
<langUsage><language ident="en">en</language>
</langUsage>
</profileDesc>
</teiHeader>
<front><div type="abstract" xml:lang="en">Abstract: This case study presents a standard example for evaluating formal specification approaches that combine a formal model of concurrency (such as Petri nets) with the object-oriented approach. You are expected to exercise your formalism of choice on this problem in order to demonstrate how well it deals with a system of reasonable size. We describe how the structure of a problem can be modeled in a formalism and how component reuse can be incorporated. It is desirable to highlight or emphasize the way that the structure of the problem can be modeled in your formalism, and the way that reuse of components can be incorporated.</div>
</front>
</TEI>
</record>
Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Wicri/Asie/explor/AustralieFrV1/Data/Istex/Curation
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 002D30 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Istex/Curation/biblio.hfd -nk 002D30 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien |wiki= Wicri/Asie |area= AustralieFrV1 |flux= Istex |étape= Curation |type= RBID |clé= ISTEX:F06DB32940DAF3AED43BAF8369CA7FCFAF03628B |texte= A Cooperative Petri Net Editor }}
![]() | This area was generated with Dilib version V0.6.33. | ![]() |