By Topic

Software Engineering Journal

Issue 2 • Date Mar 1994

Filter Results

Displaying Results 1 - 4 of 4
  • Toward measuring potential coupling

    Page(s): 83 - 90
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (728 KB)  

    Coupling (W.P. Stevens et al., 1974) measures the strength of connection between two modules and is defined for modules that share data or control connections. Other types of connections are possible. Among these are sharing of types, sharing of coding standards and sharing an environment. The work presented deals with the potential coupling between a program and other modules in the environment. The importance of this type of coupling stems from its prevalence in software reuse. Potential coupling is not defined directly like the original coupling types. Instead, this work develops bounds for the sum of all coupling in the program and uses it to define the measure of design density and define potential coupling analytically View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Implementation of static semantic analysis of LOTOS specifications

    Page(s): 55 - 66
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (656 KB)  

    The implementation of syntax-driven static semantic analysis of languages presenting recursive forward references in their definition, requires the handling of a syntax tree. When dealing with languages for which the syntax tree approach is very heavy to implement, a source code reorganisation operation may solve the problem more conveniently. This applies to the ISO specification language LOTOS which is taken as the main concern in the article. The implementation of a static semantic analyser for LOTOS based on the above approach is described by means of a C program, and all the main issues are addressed. It is shown that the source code reorganisation operation applied to LOTOS specifications does not alter the semantics of the original source specification. Examples and measures of performance collected by testing the tool on some significant case studies in the literature are also given View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Treating interactions systematically: a theme to cope with an aspect of the complexity of managing life-cycle software production

    Page(s): 67 - 82
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (1164 KB)  

    The paper presents a method for simplifying the complex managerial phenomena in the life-cycle software production by means of systems analysis. The reason for this is that software products are becoming increasingly complex and that project teams are, and will continue to be, the dominant way of organising software development. There is a fundamental principle; the complexity of the field in question is an interpretation of `reality' according to a coarse systematisation. The interpretation is about how we think, what we do and how we cope. Based on this philosophical framework, the method consists of the following: describing the complex phenomena in terms of interactions; the interactions between a team and the tasks (e.g. modelling), the interactions between the teams (e.g. co-operating) and the interactions between tasks (e.g. configuring); defining a pattern to categorise the events of the interactions and interpreting the pattern to rationalise the concepts; system context and model contexts, communication and information context. The benefits of the practical use of the method are to provide unified objectives for supplying management with technical measures, and thus to enhance the efficiency and quality of the operational processes View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Critical review of quantitative assessment

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

    The paper discusses several empirical studies reported in the literature aimed at evaluating the benefits of using software engineering methods and tools. The discussion highlights a number of problems associated with the methodology of the studies. The main problems concerned the difficulty of formulating the hypothesis to be tested, using surrogate measures, defining a control and minimising the effect of personalities. Most of these problems are found in many experimental situations, but the problem associated with the proper definition of a control group seems to be a particular issue for software experiments. The paper concludes with some guidelines for improving the organisation of empirical studies View full abstract»

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