Robert L. Glass
Skip Abstract Section
Abstract
Tools and toolsets for the software builder are receiving increased attention. Research into new-concept tools is progressing. However, the use of tools in the software workplace is not. This paper asserts that what is needed is a Minimum Standard Software Toolset which is available to all professional programmers in all workplaces. The functional content of such a toolset is proposed, based heavily on the work of the U.S. Department of Defense in its Ada Programming Support Environment.
- (ADA78) "Proceedings of the Irvine Workshop on Alternatives for the Environment, Certification and Control of the DoD High Order Language," June 1978, University of California at Irvine. A collection of session transcripts and position papers regarding APSE requirements.Google Scholar
- (ADA79) "Ada Environment Workshop," Nov. 1979, San Diego. A collection of papers on software toolsets and environments presented to influence the DoD APSE definition.Google Scholar
- (AUTO80) "Automated Tools for Software Engineering," 1980. A directory of software tools prepared by Software Research Associates, P.O. Box 2432, San Francisco CA 94126.Google Scholar
- (BELL78) "Unix Time-Sharing System," The Bell System Technical Journal, July-Aug. 1978. An issue of an in-house journal devoted to descriptions of the Unix system.Google Scholar
- (BITS80) "Boeing Intelligent Terminal System (BITS)," 1980. User manual for a Pascal based microcomputer toolset.Google Scholar
- (BUXT80) "An Informal Bibliography on Programming Support Environments," SIGPLAN Notices, Dec. 1980; J.M. Buxton. A bibliography of papers describing toolsets.Google Scholar
- (CAIN77) "PDL - Program Design Language Reference Guide," Caine, Farber and Gordon, 1977. User manual for a commercially-available PDL checker.Google Scholar
- (COMP81) Two special issues of Computer (IEEE) deal with programming environments (April 1981) and Ada and its environment (June 1981).Google Scholar
- (DANA80) "The Use of Software Tools in California Computer Science Programs," TRCS80--04, University of California at Santa Barbara, C. Dana and A. Pyster, 1980. A survey of California college computer science programs which shows that tools are little used in their curricula.Google Scholar
- (FELD79) "MAKE - A Program for Maintaining Computer Programs," Software Practice and Experience, April 1979; Feldman. Describes a version control tool which runs on the UNIX operating system.Google Scholar
- (GILL77) "On the Evolution of an Adaptive Support Software System," Computers in Aerospace Conf., Oct., 1977. Describes the Boeing Support Software System and its use.Google Scholar
- (GLAS79) "From Pascal to Pebbleman..and Beyond," Datamation, July 1979; R. L. Glass. A look at the history and status of the Ada language.Google Scholar
- (GLAS81)
Software Maintenance Guidebook , Prentice-Hall, 1981; R. L. Glass and R. A. Noiseux. A summary of the problems of software maintenance, and the tools and techniques for addressing them.Google Scholar - (HART79) "The Advanced Interactive Debugging System (AIDS)," SIGPLAN Notices, Dec., 1979; Hart. An implementation of interactive, source language debug capabilities tied to a multi-lingual compiler is described. Google ScholarDigital Library
- (HOWD82) "Contemporary Software Development Environments," Communications of the ACM, May 1982; Howden. Proposes four classes of software development environment, where the content of each is related to project size. Google ScholarDigital Library
- (IBM) "OS PL/1 Checkout Compiler Programmer's Guide" (for the IBM 370), SC330007. Describes the use of the PL/1 checkout compiler, including its source language debug capabilities.Google Scholar
- (JUG80) "JUG Support Tools Committee Minutes/Newsnotes," JOVIAL Users Group, Jan., 1980. Presentation material from a user group overview of toolsets.Google Scholar
- (KERN76)
Software Tools , Addison-Wesley, 1976; B. W. Kernighan and P. J. Plauger. A description of a toolset based on the RATFOR (structured Fortran) language and the UNIX operating system. Google ScholarDigital Library - (NAVY79) "Support Software Tool Survey," U.S. Navy, Nov. 1979. A survey of software tools prepared by the Software Quality Control Branch, Code 9133, Naval Ocean Systems Center, San Diego CA 92152.Google Scholar
- (NAVY81) "Software Engineering Environments," U.S. Navy, 1981. A survey of tools environments similar to that for tools above, prepared by the Software Engineering Technology Branch, Code 8322.Google Scholar
- (NBS81) "Software Development Tools: A Reference Guide to a Taxomony of Tools Features," National Bureau of Standards, 1981. A proposed standard tools taxonomy.Google Scholar
- (NBS82) "Software Development Tools," NBS Special Publication 500--88, Raymond C. Houghton, Jr. A categorized and indexed list of software tools.Google Scholar
- (NG78) "A 1900 Fortran Post Mortem Dump System," Software - Practice and Experience, July 1978; Ng and Young. Describes a source language debug tool which produces formatted Fortran language dumps.Google Scholar
- (REIF77) "A Glossary of Software Tools and Techniques," Computer (IEEE), July 1977; D. Reifer and Trattner. Lists, defines, and categorizes 70 types of tools.Google Scholar
- (REIF81) "Software Tools Directory," 1981. A directory of software tools prepared by Reifer Consultants, 2733 Pacific Coast Highway, Suite 203, Torrance CA 90505.Google Scholar
- (SITE78) "Programming Tools: Statement Counts and Procedure Timings," SIGPLAN Notices, Dec. 1978; Sites. Advocates the use of analysis tools to obtain visibility for making programs more efficient. Google ScholarDigital Library
- (SOFT80) "Softool 80," 1980. Brochure describing a toolset available from Softool Corp., 3701 S. Kellogg Ave., Goleta CA 93017.Google Scholar
- (SRA82) "Software Engineering Automated Tools Index," 1982. A directory of software tools prepared by Software Research Associates, P.O. Box 2432, San Francisco CA 94126.Google Scholar
- (STON80) "Requirements for Ada Programming Support Environments, Stoneman," U.S. Department of Defense, 1980. The definition of the requirements for APSE and MAPSE.Google Scholar
- (WEGN80a) "The Ada Language and Environment," Software Engineering Notes, April 1980; P. Wegner. A description of the history, status, and capabilities of Ada and APSE. Google ScholarDigital Library
- (WEGN80b)
Programming with Ada - An Introduction by Means of Graduated Examples , Prentice-Hall, 1980; P. Wegner. A tutorial on the Ada Language. Google ScholarDigital Library
Recommendations
Recommended Skills and Knowledge for Software Engineers
CSEET '99: Proceedings of the 12th Conference on Software Engineering Education and TrainingOne goal of this paper is to put forward a proposition that computer science and software engineering are distinct but related subjects and to clearly define how they are related. Another goal is to offer a recommendation on a set of skills and ...
CASE tools: understanding the reasons for non-use
Computer-Aided Software Engineering (CASE) technologies are tools that provide automated assistance for software development [3]. The goal of introducing CASE tools is the reduction of the time and cost of software development and the enhancement of the ...
CASE: Analysis and Design Tools
Computer-aided software engineering (CASE) tools are defined, and ten CASE tools are briefly overviewed. Individual presentations on the various tools follow. The focus is on structured analysis, design, and programming. Two of the tools (Cradle and JSP ...
Comments