System development methodology using LOGOS

ABSTRACT

The development of applications written in APL has traditionally both benefited by and suffered from the freedom offered by the environment. A consequence of this freedom is that few applications are designed from the perspectives of consistency, modularity, and structure. This paper describes how LOGOS, a programming environment for APL, helps improve the development and maintenance of APL applications. Through the use of basic support facilities and integrated tools, LOGOS encourages a modular design within applications and a greater consistency among them. The support facilities provide such functionality as the paging of large applications, or the parallel testing of multiple versions of software, with minimal effort. Specific examples of system design and development are given in the paper. Programming methodologies in widespread practice are examined, and their application to APL with LOGOS is described. The use of LOGOS in top-down design and in application prototyping is also discussed.

REFERENCES

• Alle86: David B. Allen , Leslie H. Goldsmith , Mark R. Dempsey , Kevin L. Harrell, LOGOS: An APL programming environment, ACM SIGAPL APL Quote Quad, v.16 n.4, p.314-325, 1986
• Bern86: Robert Bernecky, APL: A prototyping language, ACM SIGAPL APL Quote Quad, v.16 n.4, p.221-228, 1986
• Boeh62: Boehm, Corrado and G. Jacopini. "Nuove Techniche di Programmazione Semplificantila Sintesi di Macchine Universali di Turing." Rend, Act. Naz. 1 incei . , 8:32 (June 19621, pp. 913-922.
• Demp79: Mark R. Dempsey, Using an APL macroprocessor to implement generalized software systems, Proceedings of the international conference on APL: part 1, p.286-293, May 30-June 01, 1979, New York, New York, United States
• Demp81: Mark R. Dempsey , Leslie H. Goldsmith, A regular expression pattern matching processor for APL, Proceedings of the international conference on APL, p.94-100, October 21-23, 1981, San Francisco, California, United States
• Dijk65: Dijkstra, Edsger W. "Programming Considered as a Human Activity. " Proceedings of /F/P Congress 65, Spartan Books, Washington, D.C., 1965.
• Dijk68: Edsger W. Dijkstra, Letters to the editor: go to statement considered harmful, Communications of the ACM, v.11 n.3, p.147-148, March 1968 [doi>10.1145/362929.362947]
• Falk73: Falkoff, Adin D. and K.E. Iverson. "The Design of APL." IBM Journal of Research and Development, 1714 (July 1973), 324-334.
• Guim83: Tor Guimaraes, Managing application program maintenance expenditures, Communications of the ACM, v.26 n.10, p.739-746, Oct. 1983 [doi>10.1145/358413.358421]
• Hopk72: Martin E. Hopkins, A case for the GOTO, Proceedings of the ACM annual conference, p.787-790, August 01-01, 1972, Boston, Massachusetts, United States [doi>10.1145/800194.805860]
• I PSA84: WSDOC: SHARP APL Workspace Documentation Facility User's Guide. I. P. Sharp Associates Limited, Toronto, Canada, August 1984.
• IS085: Second Draft Proposal for Programming Language APL. International Standards Organisation, Document No. IS0 TC97/SC5 N811 DP-8485, March 1985.
• lver79: Kenneth E. Iverson, The role of operators in APL, Proceedings of the international conference on APL: part 1, p.128-133, May 30-June 01, 1979, New York, New York, United States
• Jack75: M. A. Jackson, Principles of Program Design, Academic Press, Inc., Orlando, FL, 1975
• Kern81: Kernighan, Brian W. and J.R. Mashey. "The UNIX Programming Environment." Computer, 14:4 (April 19811, 12-24.
• Knut74: Donald E. Knuth, Structured Programming with go to Statements, ACM Computing Surveys (CSUR), v.6 n.4, p.261-301, Dec. 1974 [doi>10.1145/356635.356640]
• Lien83: Bennet P. Lientz, Issues in Software Maintenance, ACM Computing Surveys (CSUR), v.15 n.3, p.271-278, Sept. 1983 [doi>10.1145/356914.356919]
• Mill72: Mills, Harlan D. "Chief Programmer Teams: Principles and Procedures." ISM Technical Report FSC 71-5108, IBM Corporation, Gaithersburg, MD., June 1972.
• Oste81: Osterweil, Leon. "Software Environment Research: Directions for the Next Five Years." Computer, 14:4 (April 1981), 35-43.
• PEG81: A Quick Reference Guide to the Sharp APL lmplementatlon of the APL Workshop. The Planning Economics Group, Boston, Mass., November 1981.
• Pesc82: Roland Pesch, Large arrays and files, Proceedings of the international conference on APL, p.249-253, July 26-30, 1982, Heidelberg, Germany
• Rama: C. V. Ramamoorthy , Atul Prakash , Wei-Tek Tsai , Yutaka Usuda, Software engineering: problems and perspectives, Computer, v.17 n.10, p.191-207, Oct. 1984 [doi>10.1109/MC.1984.1658970]
• Syke82: Sykes, Roy A., Jr. "Managing APL Projects. " Proceedings of the 1982 APL Users Meeting, volume 2, I .P. Sharp Associates Limited, Toronto, Canada, October 1982, pp. 387-394.
• Taus77: Robert C. Tausworthe, Standardized Development of Computer Software, Prentice Hall PTR, Upper Saddle River, NJ, 1977
• Vess83: Iris Vessey , Ron Weber, Some factors affecting program repair maintenance: an empirical study, Communications of the ACM, v.26 n.2, p.128-134, Feb. 1983 [doi>10.1145/358024.358057]
• Warn76: Warnier, Jean D. Logical Construction of Programs. 0. Flanagan, trans., 3rd cd., Van Nostrand Reinhotd, New York, N.Y., 1976.
• Wass84: Wasserman, Anthony I. "Software Toois in the User Software Engineering Environment." Interactive Programming Envlronments. David R. Barstow, H.E. Shrobe, and E. Sandewall, eds., McGraw-Hill, Inc., New York, N.Y., 1984, pp. 370-386.
• Wirt74: Niklaus Wirth, On the Composition of Well-Structured Programs, ACM Computing Surveys (CSUR), v.6 n.4, p.247-259, Dec. 1974 [doi>10.1145/356635.356639]
• Your79: Yourdon, Edward and L.L. Constantine. Structured Design. Prentice-Hall, Inc., Englewood Cliffs, N.J., 1979.
• Zelk79: Marvin V. Zelkowitz , Alan C. Shaw , John D. Gannon, Principles of Software Engineering and Design, Prentice Hall Professional Technical Reference, 1979

INDEX TERMS

Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
  D.3 PROGRAMMING LANGUAGES
      D.3.2 Language Classifications

          Nouns: APL

General Terms:
Design, Languages, Management