BibSonomy :: publication ::

tag user group author concept BibTeX key search:all search:phbaer

The blue social bookmark and publication sharing system.

(0)

This publication has not been reviewed yet.

rating distribution

average user rating

The average rating is computed over all reviews. However, some of them may be invisible to you due to the visibility setting chosen by the reviewers.

(0.0 of 5.0 based on 0 reviews)

The Drawbacks of Model-Driven Software Evolution

by: Harry Sneed

In: Workshop on Model-Driven Software Evolution at CSMR Amsterdam: (March 2007) .

Resources (URL, PDF, PS...)

URL:	http://www.sciences.univ-nantes.fr/MoDSE2007/p9.pdf

This short paper is an essay on the drawbacks of model driven software evolution which apply equally well to model driven software development. The idea of automatically generating code changes from a UML type model is equally enticing as that of automatically generating whole components from such a model. The drawback is that there is then nothing to test against, since there is only one description of the system, the model. This violates the principles of software verification and validation, according to which correctness can only be demonstrated by comparing two independent descriptions of the same solution. For this reason, the author proposes another interpretation of model driven evolution, one in which the requirements model serves as a basis for propagating changes to both the code and the test, along two independent paths. The UML type system design could then be generated from the code and not vice versa

BibTeX record

@inproceedings{sneed07modse,
  abstract = {This short paper is an essay on the drawbacks of model
driven software evolution which apply equally well to
model driven software development. The idea of
automatically generating code changes from a UML
type model is equally enticing as that of automatically
generating whole components from such a model. The
drawback is that there is then nothing to test against,
since there is only one description of the system, the
model. This violates the principles of software
verification and validation, according to which
correctness can only be demonstrated by comparing
two independent descriptions of the same solution. For
this reason, the author proposes another interpretation
of model driven evolution, one in which the
requirements model serves as a basis for propagating
changes to both the code and the test, along two
independent paths. The UML type system design could
then be generated from the code and not [vice] versa},
  added-at = {2008-07-01T11:20:58.000+0200},
  address = {Amsterdam},
  author = {Sneed, Harry},
  biburl = {http://www.bibsonomy.org/bibtex/20194bcfa92f21ac8ea1a6eae482d5cb2/phbaer},
  booktitle = {Workshop on Model-Driven Software Evolution at CSMR},
  interhash = {207867f184bd6af02fa9059b0401ea37},
  intrahash = {0194bcfa92f21ac8ea1a6eae482d5cb2},
  keywords = {drawback driven evolution harmfull model software},
  month = {March},
  timestamp = {2008-07-01T11:20:58.000+0200},
  title = {The Drawbacks of Model-Driven Software Evolution},
  url = {http://www.sciences.univ-nantes.fr/MoDSE2007/p9.pdf},
  year = 2007
}

Endnote record

%0 Conference Paper
%1 sneed07modse
%A Sneed, Harry
%B Workshop on Model-Driven Software Evolution at CSMR
%C Amsterdam
%D 2007
%K 
%T The Drawbacks of Model-Driven Software Evolution
%U http://www.sciences.univ-nantes.fr/MoDSE2007/p9.pdf
%X This short paper is an essay on the drawbacks of model
driven software evolution which apply equally well to
model driven software development. The idea of
automatically generating code changes from a UML
type model is equally enticing as that of automatically
generating whole components from such a model. The
drawback is that there is then nothing to test against,
since there is only one description of the system, the
model. This violates the principles of software
verification and validation, according to which
correctness can only be demonstrated by comparing
two independent descriptions of the same solution. For
this reason, the author proposes another interpretation
of model driven evolution, one in which the
requirements model serves as a basis for propagating
changes to both the code and the test, along two
independent paths. The UML type system design could
then be generated from the code and not [vice] versa

BibSonomy :: publication ::

The Drawbacks of Model-Driven Software Evolution

Resources (URL, PDF, PS...)

Abstract

BibTeX record

Endnote record