Showing papers on "Software as a service published in 1978"

Software Configuration Management

Abstract: This paper is about discipline. It is about discipline that managers should apply to software development. Why is such discipline needed? Quite simply because the software industry has traditionally behaved in an undisciplined manner—doing its own thing. The products that the industry has turned out have typicallyContained other than what was expected (usually less, rather than more);Been delivered much later than scheduled;Cost more than anticipated;Been poorly documented; andIf you have been involved in any of the situations quoted above, then this paper may be of some help. In short, if you are now, or intend to be, a software seller or buyer, then you should benefit from an understanding of Software Configuration Management. Lest you think that you are not now, or ever will be, a software seller or buyer—keep in mind that the recent technology explosion in electronic component miniaturization has placed the era of personalized computing at hand. In that context, nearly everyone may be considered a potential seller or buyer of software.This paper is about the discipline called Software Configuration Management (SCM). The objective of SCM is to assist the software seller in achieving product integrity and to assist the software buyer in obtaining a product that has integrity.

The use of software reliability measures in project management

Abstract: The execution time theory of software reliability developed by the author provides measures that offer promise as valuable tools in managing a software project. The measures furnish excellent current status indicators and permit schedule forecasts to be developed. The relationships among reliability, project completion date, project cost, and various resource parameters can be examined through simulation as an aid in making management decisions. Managers have indicated that the conceptual framework provided is valuable in understanding the testing process. Experience has been gained in the use of the theory on a number of projects. A program has been developed to handle most of the calculations.

Corporate Level Software Management

Abstract: Software management is considered from the corporate headquarters viewpoint. This perspective encompasses all facets of management, but specifically dealt with are those that are brought to bear on software management obstacles and ways to cope with them are presented. Standardization is presented as the most effective management device available at the corporate level for enhancing the overall software posture. Corporate management actions available for favorably influencing the quality of software over its life cycle and research initiatives are described.

Managing Software Development in Microprocessor Projects

Abstract: Careful management of firmware development effort and selection of appropriate design tools can improve programmer productivity.

Management planning for large software projects

Abstract: This paper stresses the crucial role of planning in managing, developing, integrating, and documenting a large software effort. Section 1 details the necessary components of a software plan. Section 2 then outlines the planning aspects of incremental development (i.e. successive builds) and Section 3 discusses "software first" integration planning. Finally Section 4 suggests that prior planning can provide for the straightforward. and accurate recording of project status and problems.

Guest Editorial Software Management: We Must Find a Way

Abstract: SOFTWARE management is a term which inspires many different reactions from the broad range of practitioners in the field of data processing. The term has many dimensions ranging from the first and second line manager of a software development activity who plies his trade with little to fall back on other than his prior experience, and native skills and intuition. Contrast this with a senior executive who, because of lack of understanding of software management, is frustrated in trying to determine if his company can produce a software program on schedule and within budget. The data processing landscape is littered with examples of major software developments which faltered and then expired. That this situation should exist, after almost a quarter-century of experience with implementing these systems, is one of the enigmas of the rapidly expanding data processing industry.

Software/courseware exchange for UCSD pascal

Abstract: As a result of rapidly increasing interest in the UCSD PASCAL Software System, the Institute for Information Systems will establish an exchange service for software developed by users of the system. In addition to handling contributed programs, the exchange will function as a marketplace wherein authors of applications software packages, or computer based course materials, may sell their products to customers in return for royalty payments. The exchange will recover its operating costs through customer payments of small distribution charges, and will operate as a non profit public service.

A programmable system for software configuration management

Abstract: This paper describes the design and implementation of a flexible, programmable set of software tools which provide capabilities for the automatic storage and retrieval of information concerning the components of a software product, with facilities to use this information to control all processing in a software development and maintenance environment. The system implements a hierarchically structured, relational database in which the user may specify both the logical organization and the types of data to be stored. It also provides a structured, high Ievel user language. The system may be used in batch or interactive modes. It has been implemented on a 16-bit minicomputer where it is in use to support development and configuration management activities, and is being transported to larger mainframe equipment.