By Topic

Software Engineering Journal

Issue 1 • Date January 1986

Filter Results

Displaying Results 1 - 10 of 10
  • Editorial: controlling software projects

    Save to Project icon | PDF file iconPDF (97 KB)  
    Freely Available from IEEE
  • The problems of managing software projects

    Page(s): 3 - 6
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (526 KB)  

    Experience suggests that projects involving a significant software content run a considerable risk of being completed late and over budget, while the resulting software does not always meet the original design specifications. This is in spite of the fact that the general principles of project management are well understood. This paper discusses the particular difficulties often cited by managers of software projects. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Controlling software projects

    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (1588 KB)  

    In recent years the software industry has seen the increasing imposition of structure and discipline on technical development activities in an attempt to improve the efficiency of software development and the reliability of the software produced. The clear emphasis in the modern approach to software engineering is to focus attention on the overall development process and the co-ordination all aspects of software development. This paper examines the principles of managing and successfully controlling software development from a software engineering basis. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Quantitative models for managing software development processes

    Page(s): 17 - 23
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (1481 KB)  

    This paper presents a quantitative modelling technique which the authors have developed and are using to manage medium-scale software development projects. Separate models are defined for separate project phases; each model captures the salient features of the process which underlies the corresponding phase. The models support all project management activities: planning, estimating, tracking and decision making. Furthermore, they provide a means of recording project data and experience in order to share that information with other projects. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Controlling software quality

    Page(s): 24 - 28
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (837 KB)  

    In this paper a number of methods for controlling quality are introduced and discussed. Chief among these is a model called the quality cycle. The model is used to illustrate requirements selection and specification, reviewing procedures, life cycle development and change control. It is also a basis for balancing quality with budget and time scale constraints on a project. The paper concludes with a discussion of quality management and of quality support activities: standards, training and staff motivation. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Quality management - procedures and practices

    Page(s): 29 - 38
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (1574 KB)  

    This paper presents a discussion of the need for better quality management, followed by descriptions of what the authors currently consider to be the two most effective instruments of its achievement; these are the project (or product) quality plan and its associated test plans. Finally, there is a discussion of the use of the quality plan and test plans beyond their initiating projects, followed by a summary and some thoughts on future work. A brief set of references is appended, mainly as an indication of the starting point for the concepts and procedures described in the rest of this paper. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The eclipse object management system

    Page(s): 39 - 42
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (595 KB)  

    Configuration management is a vital element in successful software development. Automation to assist configuration management will be of great benefit in improving productivity and quality in software production. Eclipse is an integrated project support environment being developed as part of the Alvey Programme. The Eclipse Object Management System provides automated assistance for configuration management. This paper describes the approach taken in Eclipse and gives details of the concepts embodied in the Eclipse Object Management System. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Field monitoring of software maintenance

    Page(s): 43 - 49
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (1153 KB)  

    Life cycle maintenance cost must be predicted for any new product. Correct management practice then requires the prediction to be checked by measurement, so that planning and budgets can be adjusted. This requires knowledge of the nature of the market, quality of the product and activities of the service organisation, and how they mutually interact. This paper describes this interaction, and the problems of data collection peculiar to each of the three areas. A relational database structure is defined to enforce consistency on the data. Particular attention is paid to the problems of having different copies of the software in different states of repair, having several versions of several products in use simultaneously, and recording running time in order to be able to measure reliability. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • SPMMS - information structures in software management

    Page(s): 50 - 57
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (1350 KB)  

    SPMMS is an ESPRIT project which aims to develop a system to support the management of software production and maintenance. In this paper we list some of the reasons why such a system is required, and then outline the characteristics which it needs to have in order to meet those requirements. The remainder of the paper addresses two of the central problems which must be solved before an adequate SPMMS can be built: how to make SPMMS flexible enough to adapt to a useful range of organisational types and working practices, and what information structure to choose to deliver the required degree of control. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Software metrics and integrated project support environments

    Page(s): 58 - 64
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (1171 KB)  

    This paper considers how the information needs of managers may be helped by the development of integrated project support environments (IPSEs). In particular the paper concentrates on the issue of obtaining quantitative information about a software product and its development process using software metrics. The nature and use of software metrics and the problems of metrics data collection are discussed in terms of the authors' experience of an already existing metrics data collection system. The paper then considers the way in which metrics collection and analysis can be incorporated into IPSEs and the requirements that metrics systems place on the design of IPSEs. View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.