The entity-relationship model—toward a unified view of data
ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
Characteristics of application software maintenance
Communications of the ACM
The system for business automation (SBA): programming language
Communications of the ACM
The ROBOT System: Natural language processing applied to data base query
ACM '78 Proceedings of the 1978 annual conference
MAPP: a DSS for financial planning
ACM SIGMIS Database - Proceedings of a conference on Decision Support Systems, Santa Clara, California, January 24-26, 1977
IEEE Transactions on Software Engineering
The entity-relationship model: a basis for the enterprise view of data
AFIPS '77 Proceedings of the June 13-16, 1977, national computer conference
AFIPS '75 Proceedings of the May 19-22, 1975, national computer conference and exposition
HIPO and integrated program design
IBM Systems Journal
IBM Systems Journal
Query-by-example: a data base language
IBM Systems Journal
Information Resource Management And The End User: Some Implications For Education
Information Resources Management Journal
Information Resources Management Journal
Assessment of End-User Computing from an Organizational Perspective
Information Resources Management Journal
Exploring a "Gap" Model of Information Services Quality
Information Resources Management Journal
Hi-index | 0.00 |
The demand for new or expanded computer-based information systems far exceeds the capacity of present DP organizations to meet this demand. Assuming that a massive expansion of DP personnel is not feasible, one solution is to make existing computer professionals more productive; and efforts in this direction have met with a fair measure of success. Another approach is to allow end users to function as their own developers. In this way, the programmer "middle man" is eliminated and users can create and modify their own applications as the need arises. Not only does this help relieve the DP department's development workload, but it also helps lessen the maintenance load. However, to accomplish this transfer of application development from DP professional to DP user, certain key variables must be understood. This article discusses these variables, including the nature of the development process, a user classification scheme, the scope and orientation of systems, and the respective roles of design and maintenance in the applications development life cycle. In particular, the misunderstood mature of "maintenance" is explored, as well as the potential value of the use of application prototypes. Finally, there is a discussion of specific tools and techniques that may aid the end user in acting as application developer.