Thomas,
>1) Nomenclature: are we going to refer to 'plans' or 'schemas' ? The
>plan-word regularly causes confusion. Shall we switch?
The concept of patterns has taken off in the software world.
Would using 'pattern' carry too many incorrect overtones to be used
by ppigers?
Schemas are used by the database people (a very underresearched
area, I have not even found any papers on metrics for SQL) and
might be confused by them.
Of course we are also assuming that the software world will embrace
the research being carried out by you all one day (which I hope it does).
> > I am beginning to think that program understanding does not exist.
> > A program is a knowledge base that people learn. Complex ones are harder
> > to learn about than simpler ones, hence my interest in reducing complexity.
>
>I like the switch from understanding to learning. It de-emphasizes the idea
>of grasping the whole 'meaning' of a program, all at one go, and brings out
>a picture of incremental growth, with islands of understood parts and dark
>areas where the program is doing something that is still mysterious.
I think the problem is on the word program. This is generally used to refer to
all of the software that makes up the whole. Programs tend to be large and
people usually work on parts of it.
'parts of program' understanding
module understanding
procedure understanding
software understanding
software comprehension
code understanding
code comprehension
derek
--
Derek M Jones tel: +44 (0) 1252
520 667
Knowledge Software Ltd mailto:[EMAIL PROTECTED]
Applications Standards Conformance Testing http://www.knosof.co.uk
- Automatic footer for [EMAIL PROTECTED] ----------------------------------
To unsubscribe from this list, mail [EMAIL PROTECTED] unsubscribe discuss
To join the announcements list, mail [EMAIL PROTECTED] subscribe announce
To receive a help file, mail [EMAIL PROTECTED] help
This list is archived at http://www.mail-archive.com/discuss%40ppig.org/
If you have any problems or questions, please mail [EMAIL PROTECTED]
