Design principles for software manufacturing tools

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

Design principles for software manufacturing tools

Full text

Pdf (806 KB)

Source

ACM Annual Conference/Annual Meeting archive
Proceedings of the 1984 annual conference of the ACM on The fifth generation challenge table of contents

Pages: 85 - 93

Year of Publication: 1984

ISBN:0-89791-144-X

Author

Paul Bassett

Sponsor

ACM: Association for Computing Machinery

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 4, Downloads (12 Months): 10, Citation Count: 0

Additional Information:

abstract references index terms collaborative colleagues

Tools and Actions:	Request Permissions Review this Article Save this Article to a Binder Display Formats: BibTeX EndNote ACM Ref

DOI Bookmark:	Use this link to bookmark this Article: http://doi.acm.org/10.1145/800171.809608 What is a DOI?

ABSTRACT

A good solution to the reusable code problem turns out to provide a solid technical basis from which to understand and deal with the production, quality, and maintenance issues currently besieging the software industry. To this end, a software manufacturing methodology has been developed called Computer Aided Programming tm. CAP is based on a functional programming concept called a frame, motivated in turn by the reusable code problem. The introduction explains the necessary background ideas about frames. Section two analyzes the subtle but important distinction between problem solving and programming. CAP design principles are then developed which show how to build software tools that support problem solving through open—ended, structured, program manufacturing techniques. The principles are organized around the flow of program specifications from 'under' to 'optimally', to 'over' specified, machine executable instructions. The components of an existing CAP system are described in section three, and section four discusses the usage of CAP as a manufacturing technique. Statistics from a case study are presented which indicate that: (a) production quality commercial software can be manufactured at rates exceeding 2000 lines of debugged COBOL per man-day (including systems design time), and (b) less than 10% of this code needs to be hand written /-maintained.

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	John Backus, Can programming be liberated from the von Neumann style?: a functional style and its algebra of programs, Communications of the ACM, v.21 n.8, p.613-641, Aug. 1978 [doi>10.1145/359576.359579]
	2	BALZER, R. An alternative approach to software automation. In Research Directions in Software Technology, P. Wegner (Ed.), MIT Press, Cambridge, Mass., 1979, pp. 851-856.
	3	Paul Bassett, Computer Aided Programming, Proceedings of the 20th conference on Design automation, p.527-529, June 27-29, 1983, Miami Beach, Florida, United States
	4	BASSETT, P.B. and RANKINE, S. The Maintenance Challenge. Computerworld In Depth, May 16, 1983.
	5	BIANCHI, M.H., MASHEY, J.R. Rapid Prototyping on UNIXtm. Presented at the Software Engineering Symposium: Rapid Prototyping, Columbia Maryland, April 19-21 1982.
	6	BLATTNER, M., FROBOSE, R. Prototyping and the Life Cycle of Software. Presented at the Software Engineering Symposium: Rapid Prototyping, Columbia Maryland, April 19-21 1982.
	7	CHEATHAM, T.E. The Harvard PDS Project: an Overview. Presented at the Software Engineering Symposium: Rapid Prototyping, Columbia Maryland, April 19-21 1982.
	8	Michael Evans, Software engineering for the Cobol environment, Communications of the ACM, v.25 n.12, p.874-882, Dec 1982 [doi>10.1145/358728.358732]
	9	GOGUEN, J.A., THATCHER, J.W., and WAGNER, E.G. An Initial Algebra Approach to the specification, correctness and implementation of abstract data types. In Current Trends In Programming Methodology, vol 4, R. Yeh (Ed.). Prentice-Hall, 1979 pp. 80-149.
	10	HAMMER, M., RUTH, G. Automating the Software Development Process. In Research Directions in Software Technology, P. Wegner (Ed.), MIT Press, Cambridge, Mass., 1979, pp. 767-790.
	11	HOUGHTON, R.C. jr. Rapid Prototyping Tools: What can we Learn From the MIS World ? Presented at the Software Engineering Symposium: Rapid Prototyping, Columbia Maryland, April 19-21 1982.
	12	R. E. A. Mason , T. T. Carey, Prototyping interactive information systems, Communications of the ACM, v.26 n.5, p.347-354, May 1983 [doi>10.1145/69586.358137]
	13	MINSKY, M. A Framework for Representing Knowledge. In The Psychology of Computer Vision, P. Winston (Ed.), McGraw-Hill Inc., U.S.A., 1975, pp. 211-277.
	14	Charles Rich, Inspection Methods in Programming: Cliches and Plans, Massachusetts Institute of Technology, Cambridge, MA, 1987
	15	TAYLOR, T., STANDISH, T.A. Initial Thoughts on Rapid Prototyping Techniques. Presented at the Software Engineering Symposium: Rapid Prototyping, Columbia Maryland, April 19-21 1982.
	16	Anthony I. Wasserman , Steven Gutz, The future of programming, Communications of the ACM, v.25 n.3, p.196-206, March 1982 [doi>10.1145/358453.358459]
	17	WULF, W.A. Some Thoughts on the Next Generation of Programming Languages. In Perspectives on Computer Science, Academic Press, New York, New York, 1977, pp. 217-234.