softwareengineering has become a de rigueur part of all self-respecting conferences on computer subjects, and has complete masters degree curricula devoted to itself in some universities. Special templates for drawi...
softwareengineering has become a de rigueur part of all self-respecting conferences on computer subjects, and has complete masters degree curricula devoted to itself in some universities. Special templates for drawing “softwareengineering symbols” are being issued to employees of programming divisions of large companies, and uncounted audiences attend softwareengineering courses, schools, symposia and workshops. All this indicates that as a fad softwareengineering is enormously *** paper attempts to bring into focus some issues that in the nearest future are very likely to enter the field that we today consider as “softwareengineering.”
While there is currently a proliferation of software development tools and development support systems, they do not appear to be having an impact consonant withthe expectations which led to their preparation. A recen...
While there is currently a proliferation of software development tools and development support systems, they do not appear to be having an impact consonant withthe expectations which led to their preparation. A recent workshop-style conference had the intent of assessing the current state-of-the-art in the area of software development tools, identifying the reasons underlying their diminished impact, and establishing directions for further advancement within the area of software development tools. the intent of this panel is to initiate discussion of these issues within the softwareengineering community at large by using a report upon the workshop-style conference as a focus of an open discussion.
three key factors often determine the success or failure of a software project: the management of the project, the selection of personnel, and the development methodology that is used. this paper discusses the importa...
three key factors often determine the success or failure of a software project: the management of the project, the selection of personnel, and the development methodology that is used. this paper discusses the important considerations that should be addressed in each of these areas and examines the results of a typical project that paid attention to these factors. In particular, it was concluded that a good development methodology can help ensure the reliability, maintainability and timeliness of any software project.
this paper explains how to use APL to build assemblers, PASCAL-like dialects, or special purpose languages. Our technique is to use APL not as a programming language but as an interactive softwareengineering environm...
this paper explains how to use APL to build assemblers, PASCAL-like dialects, or special purpose languages. Our technique is to use APL not as a programming language but as an interactive softwareengineering environment Our experience is that modern programming techniques like extendibility, program and data structuring can be made available to mini and microcomputer programmers at a minimum expense and very quickly.
the production of software can be viewed as an economic, as well as an engineering, process. Since the prime factor of production is the labor inputs of programmers and systems analysts, the personnel characteristics ...
the production of software can be viewed as an economic, as well as an engineering, process. Since the prime factor of production is the labor inputs of programmers and systems analysts, the personnel characteristics and employment trends of these occupations in the United States are reviewed. these labor factors are then related to prior and expected trends in the installation and utilization of computer equipment. A discussion of programming labor productivity is followed by a digression on the diffusion rates of technology. A brief outlook of plausible software developments suggests two areas perhaps deserving more softwareengineering research and development attention.
Does the adherence to softwareengineering concepts allow effective management in planning, organizing, staffing, monitoring, and controlling the development of quality software with-in time and resources budgets? Our...
Does the adherence to softwareengineering concepts allow effective management in planning, organizing, staffing, monitoring, and controlling the development of quality software with-in time and resources budgets? Our panel of experts will provide realistic analysis of current management problems withsoftware development and proven successful approaches and techniques for solving these problems in the production and subsequent maintenance of software. Issues to be discussed include:Inadequate planning for changes and management of change controlOvercoming continuous project redefinition of goals, schedules and responsibilitiesProgress measurement of actual technical accomplishmentsImproving communications between users, analysts, designers, and programmersValidity of software development estimating techniques in planningProgrammer productivity improvement utilizing structured design and programming techniquesTop down implementationConfiguration management
the Microprocessor softwareengineering Facility (MSEF) is an integrated set of software tools to support the development and maintenance of microcomputer software. the MSEF is hosted on a PDP-11 computer under the UN...
the Microprocessor softwareengineering Facility (MSEF) is an integrated set of software tools to support the development and maintenance of microcomputer software. the MSEF is hosted on a PDP-11 computer under the UNIX operating system but could support the production of software for many different microcomputers. the MSEF Change Control Library promotes defining, updating, and integrating parts of a software configuration, isolation of user work environments, and version control. the MSEF supports the organized testing of software components by associating test scenarios and test results withthe components to be tested. the MSEF also provides automatic change logging with a configuration audit trail. A macro assembler supporting structured langauge constructs is included in the tool complement.
A study has been carried out to relate the maintenance performance of a collection of PL/I programs to measures that characterize control flow, data usage, and software science attributes of the programs. the programs...
A study has been carried out to relate the maintenance performance of a collection of PL/I programs to measures that characterize control flow, data usage, and software science attributes of the programs. the programs are from two subsystems of a business data processing application. Interesting relationships were found not only between the maintenance data and the measures but also among the measures themselves. this paper discusses some of the stronger of these relationships.
this paper illustrates four experiences in cross software development for microprocessors. After a comparison among some programming techniques (high-level languages, macroprocessors, meta-assemblers and special purpo...
this paper illustrates four experiences in cross software development for microprocessors. After a comparison among some programming techniques (high-level languages, macroprocessors, meta-assemblers and special purpose systems) a translator writing system has been used to implement a cross-assembler, a simulator, a microassembler and a cross compiler for a microprocessor, showing its great flexibility at a low cost. Each of the four applications is briefly described and compared with similar programs written using other techniques.
the main aim of this paper is to indicate how various losses may be reduced or avoided when the development of software does not proceed according to its schedule; i.e., if what we call “bankruptcy” occurs. Data wer...
the main aim of this paper is to indicate how various losses may be reduced or avoided when the development of software does not proceed according to its schedule; i.e., if what we call “bankruptcy” occurs. Data were collected from twenty three projects in various types of applications, the projects together containing a million lines of code. the causes of failure in developing software were obtained by interviewing the managers of the projects under observation. Having analysed these two aspects, this paper points out under what circumstances managers are likely to fail and proposes a method of detecting failures in the software development.
暂无评论