On Wed, 06 Oct 1999 16:44:38 +0100, "Peter Hornsby" <[EMAIL PROTECTED]>
wrote:
> My work is very much concerned with using contextual knowledge in software
> engineering. I am currently developing a system which uses design
> information as a source of 'meaning' for code - identifying higher level
> information about what the code is being used for rather than using formal
> approaches to (fairly ridigly) specify what a given code fragment /
> component can be used for.
You might also consider applying the same treatment to code changes as well as
fixed pieces of code. That is, you could identify higher information about
what the changes to code are for.
I know of at least one prototype programming environment which tried to
capture networks of abstractions down to both code and changes to code: ESDE-P
from my own thesis [1]. :-j
Perhaps code changes could be called "delta code"? At the design level one
might imagine "delta UML" which diagrammatically describes changes to a
design. I wonder if such a thing has been formulated yet or if it has any
worth?
Hmmm. I wonder also if the 2nd etc derivative of code WRT time is worth
describing? (:-j)
__Jason
[1] J. Trenouth (1990) "A Framework for Exploratory Software Development:
integrating software version control and undo support", PhD Thesis, University
of Exeter.
