I found this article by Stamen when searching for information about end user computing.
Stamen explicates the assumption I believe the PBD people have made in their research: “the two chief areas of business are on-line transaction processing and online analytical processing, the latter colloquially referred to as end user computing†(Stamen, 1993, p.55). This implies that Transaction Processing Systems and end-user computing are antonyms.
I believe that it’s this underlying assumption that has kept the Programming by Demonstration researchers from considering the option of end user development in transaction processing systems (see previous post).
In the table below, Stamen further posits that the user interface for transaction processing systems is unchanging.
| Characteristics | Application | |
| Transaction processing |
End-user computing |
|
| Data per transaction | Little | Lots |
| Orientation | Records | Attributes |
| Screens | Unchanging | User-defined |
| Typical operation | Update | Analyze |
| Data level | Detail | Aggregate |
| Age of data | Current | Historical, current and projected. |
Tha fact that most TPS have very static, simple user interfaces does not mean that they should have static, simple user interfaces. Or that they should be neglected by End User computing research in general. In fact TPS are possibly the applications most in need of end user development.
Naked objects s not a good user interface design methodology.