Showing papers in "Journal of Systems and Software in 1996"

TL;DR: This article discusses various types of code changes of classes in an object-oriented program and presents a method for identifying these changes and the affected classes and an algorithm for generating a desirable order to test the affectedclasses.

TL;DR: An empirical comparison of several modeling techniques for predicting the quality of software components early in the software life cycle is described, finding that no model was able to effectively discriminate between components with faults and components without faults.

TL;DR: A shift of focus for IS planning research is proposed by suggesting a smodel that combines the above concepts, considering the inter-dependence between organizational structure and culture.

TL;DR: A safety checklist for use during the analysis of software requirements for spacecraft and other safety-critical, embedded systems is provided to reduce the number of safety-related software errors.

TL;DR: This work studied of how experts perform this design recovery activity by analyzing the cognitive processes of six experienced system developers engaged in the program comprehension phase of software reengineering.

TL;DR: This paper forms dynamic property specification and detection as instances of the language recognition problem, and gives examples for the case of properties that can be specified as regular grammars through finite automata.

TL;DR: The amount of effort devoted to the ASP acquisition and implementation process has a positive and significant correlation with the perceived quality of an acquired ASP, and such a relationship is stronger when the level of structuredness of the task to be automated is low.

TL;DR: A framework for maintaining control of and analyzing object-oriented system specifications of real-time systems by using a set of metrics covering technical, cognitive, and process-oriented views is presented.

TL;DR: The article divides the languages into four major categories based on the way the language specifies the external behavior of the system and on the ability of the language to specify concurrent systems.

TL;DR: A new technique for determining at design time, the utilization bound for a specific set of hard real-time periodic tasks with known periods, when scheduled by any arbitrary fixed priority algorithm is developed.

TL;DR: The article presents models for each system view, describes methods for linking the views with a top-down flow of system objectives, and applies the method to a simplified radar warning receiver.

TL;DR: An extensive study involving three test groups over a period of three different years was performed to determine differences between comprehension of recursive and iterative code constructs, suggesting a tendency toward an interaction effect between task and construct in terms of comprehension time.

TL;DR: A new, meaningful lower bound on the number of test cases needed to achieve branch coverage is introduced as the maximum number of unconstrained arcs in a ddgraph that are mutually weakly incomparable and fits into the testability model of Bache and Mullerburg (1990).

TL;DR: An experiment to evaluate the relative effectiveness of functional-decomposition and object-orientation as paradigms for client/developer communication in the early stages of the system development process suggests that functional- decomposition is the more effective of the two paradigm as a vehicle for early client/ developer communication.

TL;DR: A data reduction method is presented that makes multivariate data analysis involved in intrusion detection more efficient and extracts, from the original data set, discriminating components that best characterize user behavior.

TL;DR: In this article, the authors advocate a conical-spiral type life cycle, arranged in two dimensions (the spiral) for the development of software engineering systems and three dimensions ( the conical)-spiral for the knowledge engineering life cycle.

TL;DR: A model-oriented approach for safety analysis using fault trees is described, which advocates that a safety analysis of a system should start with a systematic study of the physical model of the system and, as a result, construct a system safety model based on thephysical model.

TL;DR: This work describes an alternative escrow system that uses public-key cryptography and nonclassified algorithms, implementable in hardware or software, and should give users (and perhaps governments) more confidence, be more exportable, and permit a fully automated escrow/retrieval system.

TL;DR: This work presents a model that is an extension of a servicebased reference model for development environments that can be used to formally define terms such as open systems, features for open systems such as interoperability, and integration.

TL;DR: It is argued that an inconsistent use of fundamental concepts prohibits their effective application and leads to a decrease of the quality of the resulting software.

TL;DR: An independent assessment of the effectiveness of using Z on CICS based on the set of public domain documents is provided and how future similar case studies could be improved so that the results are more rigorous and conclusive is described.

TL;DR: A model has been developed, dealing with the matching between prevailing contingency factors and the preconditions of already existing situated approaches, and a generic process model for systems development, including the information systems operations stage, is proposed.

TL;DR: The proposed methodology combines the ODP (Open Distributed Processing) concepts and structuring rules with the systematic development process advocated by a second generation object-oriented software engineering method called fusion to propose a seamless thread from problem definition to the realization of the distributed telecommunications system.

TL;DR: An ME-technique is provided for the construction, analysis, and refinement of an O/A-matrix and illustrated by examples taken from the ME of the SPITS methodology.

TL;DR: An analysis approach designed to generate program documentation that satisfies a set of criteria for facilitating the rigorous understanding of code components via documentation is presented and existing notations and approaches with respect to these criteria are evaluated.

TL;DR: This article addresses the problem of how to select event sequences from an abstract program to test its concrete implementation, and describes a constraint notation called CSPE and formally define C SPE constraints in the propositional modal μ-calculus.

TL;DR: An integrated approach to test tracking and analysis in a commercial software development environment that includes measurement gathering, graphical test activity and defect tracking, overall quality assessment using various reliability growth models, and identification of problematic areas and risk management using tree-based modeling is presented.

TL;DR: This work argues that all that an object-oriented model needs to support for behavioral specifications are purely functional behaviors, with no side-effects on the objects implementing them; and purely side-effectal behaviors, whose effects are restricted to the implementer and its components.

TL;DR: Criteria for measuring efficiency of database access as applications expressed in different normal forms is illustrated and it is found that in almost all studied cases where there are multivalued dependencies, the fourth normal form is more efficient.

TL;DR: A design methodology of real-time systems to be implemented on multiprocessor machines which can decompose the life cycle into six stages, according to five views of systems and propose how to transform the results from one stage to another.