WHAT-IF : A Function to Estimate the Impacts of Potential Changes in a Software
Identifieur interne : 001436 ( Crin/Corpus ); précédent : 001435; suivant : 001437WHAT-IF : A Function to Estimate the Impacts of Potential Changes in a Software
Auteurs : S. Ajila ; H. Basson ; J.-C. DerniameSource :
English descriptors
- KwdEn :
Abstract
Software maintenance is generally known to be time consuming and expensive. One of the main reasons for this is that it is difficult for software engineers and analysts to understand fully a software system that they did not design or implement. Even when they develop their own system, it is easy to forget the details of the design or code developed at earlier stages. Some of the questions a software engineer may want to ask when making a change are : {\it what other parts of the software must I change if I carry out this modification? who in the developing team must be informed of this modification? what other versions or configurations of the software system must I change?} The effect of changing a part of a software system depends on the item of change, type of change and environment of change. Therefore, when making a change it is necessary to analyze its impacts and keep track of the details of implementing the change. In this paper we present a model that will allow {\it a priori}, the impact analysis and propagation of objects change in a software system. Our work is primarily aimed at large software systems. WHAT-IF is a knowledge-based system. It uses an attributed multi-graph to represent the structure of a software system from different points of view. The inference engine for impact analysis and change propagation is written in Prolog. Thus, the inference engine can be fired each time there is a need to evaluate the impact of a particular change.
Links to Exploration step
CRIN:ajila94aLe document en format XML
<record><TEI><teiHeader><fileDesc><titleStmt><title xml:lang="en" wicri:score="467">WHAT-IF : A Function to Estimate the Impacts of Potential Changes in a Software</title></titleStmt><publicationStmt><idno type="RBID">CRIN:ajila94a</idno><date when="1994" year="1994">1994</date><idno type="wicri:Area/Crin/Corpus">001436</idno></publicationStmt><sourceDesc><biblStruct><analytic><title xml:lang="en">WHAT-IF : A Function to Estimate the Impacts of Potential Changes in a Software</title><author><name sortKey="Ajila, S" sort="Ajila, S" uniqKey="Ajila S" first="S." last="Ajila">S. Ajila</name></author><author><name sortKey="Basson, H" sort="Basson, H" uniqKey="Basson H" first="H." last="Basson">H. Basson</name></author><author><name sortKey="Derniame, J C" sort="Derniame, J C" uniqKey="Derniame J" first="J.-C." last="Derniame">J.-C. Derniame</name></author></analytic></biblStruct></sourceDesc></fileDesc><profileDesc><textClass><keywords scheme="KwdEn" xml:lang="en"><term>change propagation</term><term>impact analysis</term><term>knowledge base</term><term>relationships</term><term>software components</term><term>software maintenance</term></keywords></textClass></profileDesc></teiHeader><front><div type="abstract" xml:lang="en" wicri:score="4806">Software maintenance is generally known to be time consuming and expensive. One of the main reasons for this is that it is difficult for software engineers and analysts to understand fully a software system that they did not design or implement. Even when they develop their own system, it is easy to forget the details of the design or code developed at earlier stages. Some of the questions a software engineer may want to ask when making a change are : {\it what other parts of the software must I change if I carry out this modification? who in the developing team must be informed of this modification? what other versions or configurations of the software system must I change?} The effect of changing a part of a software system depends on the item of change, type of change and environment of change. Therefore, when making a change it is necessary to analyze its impacts and keep track of the details of implementing the change. In this paper we present a model that will allow {\it a priori}, the impact analysis and propagation of objects change in a software system. Our work is primarily aimed at large software systems. WHAT-IF is a knowledge-based system. It uses an attributed multi-graph to represent the structure of a software system from different points of view. The inference engine for impact analysis and change propagation is written in Prolog. Thus, the inference engine can be fired each time there is a need to evaluate the impact of a particular change.</div></front></TEI><BibTex type="inproceedings"><ref>ajila94a</ref><crinnumber>94-R-044</crinnumber><category>3</category><equipe>GENIE LOGICIEL</equipe><author><e>Ajila, S.</e><e>Basson, H.</e><e>Derniame, J.-C.</e></author><title>WHAT-IF : A Function to Estimate the Impacts of Potential Changes in a Software</title><booktitle>{Proceedings Software Quality Management, Edinburgh (Scotland)}</booktitle><year>1994</year><month>jul</month><publisher>Computational Mechanics Publications</publisher><keywords><e>software maintenance</e><e>software components</e><e>impact analysis</e><e>change propagation</e><e>relationships</e><e>knowledge base</e></keywords><abstract>Software maintenance is generally known to be time consuming and expensive. One of the main reasons for this is that it is difficult for software engineers and analysts to understand fully a software system that they did not design or implement. Even when they develop their own system, it is easy to forget the details of the design or code developed at earlier stages. Some of the questions a software engineer may want to ask when making a change are : {\it what other parts of the software must I change if I carry out this modification? who in the developing team must be informed of this modification? what other versions or configurations of the software system must I change?} The effect of changing a part of a software system depends on the item of change, type of change and environment of change. Therefore, when making a change it is necessary to analyze its impacts and keep track of the details of implementing the change. In this paper we present a model that will allow {\it a priori}, the impact analysis and propagation of objects change in a software system. Our work is primarily aimed at large software systems. WHAT-IF is a knowledge-based system. It uses an attributed multi-graph to represent the structure of a software system from different points of view. The inference engine for impact analysis and change propagation is written in Prolog. Thus, the inference engine can be fired each time there is a need to evaluate the impact of a particular change.</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 001436 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Crin/Corpus/biblio.hfd -nk 001436 | 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:ajila94a
|texte= WHAT-IF : A Function to Estimate the Impacts of Potential Changes in a Software
}}
| This area was generated with Dilib version V0.6.33. |  |