Good
points! Does anybody have references/papers/names for the "Testing" topic? Or
would you say there are none?
Sebastian
-----Urspr�ngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Ruven E Brooks
Gesendet: Donnerstag, 10. M�rz 2005 17:20
An: [email protected]
Betreff: Re: PPIG discuss: Commercial reality (was: Competence (was: About natural naming))
The "programming" in Psychology of Programming seems to have gotten associated with behavior having to do with the syntax/semantics of programming languages and the coding activity.
A few of the open questions that I'd include in PoSE that fall outside the programming language issues are:
Testing - How do people decide what to test? How do people construct tests? How do people actually use test tools (as versus the way the authors of those tools envisioned their use)?
There are also some issue here that are on the PoP/PoSe border. How do novice programmers learn to do testing? How does programming language syntax/semantics affect test strategy and behavior?
Requirements and specifications. This is a huge area. Is there a psychological separation between a requirement and a specification or is it all context dependent? What sorts of requirement representations are hard/easy to code from? Why? How do requirements errors happen? Can we come up with a taxonomy of requirements errors? What does it take to teach novice software developers to write requirements?
There are also some areas that I have more trouble translating directly to psychological issues. Whether a product installs successfully is actually far more important than whether it has bugs after
it is installed. Why do installs fail? What kinds of human errors lead to install failures? What are the psychological characteristics of systems for creating install scripts? Are they just like conventional programming languages or are they fundamentally different in some way?
Ruven
