Serveur d'exploration sur la recherche en informatique en Lorraine

Attention, ce site est en cours de développement !
Attention, site généré par des moyens informatiques à partir de corpus bruts.
Les informations ne sont donc pas validées.

Maintaining Shared Workspaces Consistency during Software Development

Identifieur interne : 002475 ( Crin/Corpus ); précédent : 002474; suivant : 002476

Maintaining Shared Workspaces Consistency during Software Development

Auteurs : Hala Skaf ; François Charoy ; Claude Godart

Source :

RBID : CRIN:skaf99b

English descriptors

Abstract

The development of large software is always done by teams of people working together and struggling to produce quality software within their budget. Each person in these teams generally knows his job and wants to do it, without being bothered by other people. However, when people work towards a common goal they have to exchange data and create dependencies between each other regarding these data. If these people have to follow a process, cooperating and synchronizing with co-workers and trying to reach one's own goal becomes too difficult to manage. This may leads to frustration, lower productivity and reluctancy to follow the predefined process. This is why some support is needed to avoid common mistakes that occur when people exchange data. In this paper, a hybrid approach to support cooperation is presented. The originality of this approach is the ability to enforce general properties on cooperative interactions while using the semantic of applications to fit particular situations or requirements. This paper gives a brief idea about the general enforced properties on activity interactions. It describes in detail the semantic rules that control activity results, the impacts of the cooperation on these rules and how both of dimensions interact.

Links to Exploration step

CRIN:skaf99b

Le document en format XML

<record>
<TEI>
<teiHeader>
<fileDesc>
<titleStmt>
<title xml:lang="en" wicri:score="359">Maintaining Shared Workspaces Consistency during Software Development</title>
</titleStmt>
<publicationStmt>
<idno type="RBID">CRIN:skaf99b</idno>
<date when="1999" year="1999">1999</date>
<idno type="wicri:Area/Crin/Corpus">002475</idno>
</publicationStmt>
<sourceDesc>
<biblStruct>
<analytic>
<title xml:lang="en">Maintaining Shared Workspaces Consistency during Software Development</title>
<author>
<name sortKey="Skaf, Hala" sort="Skaf, Hala" uniqKey="Skaf H" first="Hala" last="Skaf">Hala Skaf</name>
</author>
<author>
<name sortKey="Charoy, Francois" sort="Charoy, Francois" uniqKey="Charoy F" first="François" last="Charoy">François Charoy</name>
</author>
<author>
<name sortKey="Godart, Claude" sort="Godart, Claude" uniqKey="Godart C" first="Claude" last="Godart">Claude Godart</name>
</author>
</analytic>
<series>
<title level="j">International Journal of Software Engineering and Knowledge Engineering</title>
<imprint>
<date when="1999" type="published">1999</date>
</imprint>
</series>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc>
<textClass>
<keywords scheme="KwdEn" xml:lang="en">
<term>consistency</term>
<term>constraints</term>
<term>cooperation</term>
<term>cooperative environment</term>
</keywords>
</textClass>
</profileDesc>
</teiHeader>
<front>
<div type="abstract" xml:lang="en" wicri:score="3942">The development of large software is always done by teams of people working together and struggling to produce quality software within their budget. Each person in these teams generally knows his job and wants to do it, without being bothered by other people. However, when people work towards a common goal they have to exchange data and create dependencies between each other regarding these data. If these people have to follow a process, cooperating and synchronizing with co-workers and trying to reach one's own goal becomes too difficult to manage. This may leads to frustration, lower productivity and reluctancy to follow the predefined process. This is why some support is needed to avoid common mistakes that occur when people exchange data. In this paper, a hybrid approach to support cooperation is presented. The originality of this approach is the ability to enforce general properties on cooperative interactions while using the semantic of applications to fit particular situations or requirements. This paper gives a brief idea about the general enforced properties on activity interactions. It describes in detail the semantic rules that control activity results, the impacts of the cooperation on these rules and how both of dimensions interact.</div>
</front>
</TEI>
<BibTex type="article">
<ref>skaf99b</ref>
<crinnumber>99-R-382</crinnumber>
<category>1</category>
<equipe>ECOO</equipe>
<author>
<e>Skaf, Hala</e>
<e>Charoy, François</e>
<e>Godart, Claude</e>
</author>
<title>Maintaining Shared Workspaces Consistency during Software Development</title>
<journal>International Journal of Software Engineering and Knowledge Engineering</journal>
<year>1999</year>
<volume>9</volume>
<number>5</number>
<pages>623-642</pages>
<month>Oct</month>
<keywords>
<e>cooperation</e>
<e>cooperative environment</e>
<e>constraints</e>
<e>consistency</e>
</keywords>
<abstract>The development of large software is always done by teams of people working together and struggling to produce quality software within their budget. Each person in these teams generally knows his job and wants to do it, without being bothered by other people. However, when people work towards a common goal they have to exchange data and create dependencies between each other regarding these data. If these people have to follow a process, cooperating and synchronizing with co-workers and trying to reach one's own goal becomes too difficult to manage. This may leads to frustration, lower productivity and reluctancy to follow the predefined process. This is why some support is needed to avoid common mistakes that occur when people exchange data. In this paper, a hybrid approach to support cooperation is presented. The originality of this approach is the ability to enforce general properties on cooperative interactions while using the semantic of applications to fit particular situations or requirements. This paper gives a brief idea about the general enforced properties on activity interactions. It describes in detail the semantic rules that control activity results, the impacts of the cooperation on these rules and how both of dimensions interact.</abstract>
</BibTex>
</record>

Pour manipuler ce document sous Unix (Dilib)

EXPLOR_STEP=$WICRI_ROOT/Wicri/Lorraine/explor/InforLorV4/Data/Crin/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 002475 | SxmlIndent | more

Ou

HfdSelect -h $EXPLOR_AREA/Data/Crin/Corpus/biblio.hfd -nk 002475 | SxmlIndent | more

Pour mettre un lien sur cette page dans le réseau Wicri

{{Explor lien
   |wiki=    Wicri/Lorraine
   |area=    InforLorV4
   |flux=    Crin
   |étape=   Corpus
   |type=    RBID
   |clé=     CRIN:skaf99b
   |texte=   Maintaining Shared Workspaces Consistency during Software Development
}}

Wicri

This area was generated with Dilib version V0.6.33.
Data generation: Mon Jun 10 21:56:28 2019. Site generation: Fri Feb 25 15:29:27 2022