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

TL;DR: A survey of 400 recent research articles suggests that computer scientists publish relatively few papers with experimentally validated results, which appears to be a serious weakness in computer science research.

TL;DR: A case study designed to investigate two alternatives for reducing the cost of mutation, randomly selected x% mutation and constrained abs/ror mutation, which provide experimental data indicating that both alternatives lead to test sets that distinguish a significant number of nonequivalent mutants and provide high all-uses coverage.

TL;DR: The role of metrics in an integrated approach to system and software engineering is described, the basic components of complete metric definitions are introduced, and the use of metrics is discussed in comprehensively assessing objective aspects of the requirements engineering process and its products.

TL;DR: Exceptional engineers are more likely than nonexceptional engineers to maintain a “big picture,” have a bias for action, be driven by a sense of mission, exhibit and articulate strong convictions, play a proactive role with management, and help other engineers.

TL;DR: The utility of neural networks in isolating high-risk modules where class determination is based on multiple quality metrics is demonstrated, and the absence of the data assumptions typical of statistical techniques is demonstrated.

TL;DR: This article proposes candidature criteria founded on the dominance relation between the nodes of a call-directed graph that has been adopted in a real-life reuse reengineering process on PASCAL software.

TL;DR: In reply to the long-standing question as to whether overruns are more attributable to inaccurate estimating or ineffectual project management, the data in this study raise concerns about the latter.

TL;DR: A typical result of the calculations obtained by applying the C & C formulas to two different implementations of an algorithm shows that the formulas are sensitive enough to distinguish between the two implementations, and the obtained quantitative values agree with the qualitative assessment of the implementations.

TL;DR: The REBOOT approach to software reuse is presented, covering both organizational and technical aspects and the experiences so far from the applications.

TL;DR: This article reviews two early attempts at software maintainability assessment and describes five recently developed models that are applied to industrial software systems and shown to be effective in evaluatingindustrial software systems at the component, subsystem, and system levels.

TL;DR: An application domain perspective is applied to software reuse by selecting those features required in a target system and then tailoring the domain model, subject to the appropriate feature/object dependency constraints, to generate the target system specification.

TL;DR: This article attempts to bring order to disorder by identifying and classifying different notions of program slicing and their applications, including a new notion of execution slice and a method for interprocedural dynamic slicing are introduced.

TL;DR: It was found that neither code size nor subjective factors describing the problem, schedule, personnel, process, product, and development environment provided enough information with which to predict the total number of faults in highly fault-prone modules.

TL;DR: This paper examines a number of successful requirements engineering efforts carried out by the author and determines that a critical element in the success of these efforts was the author's ignorance of the client's domain.

TL;DR: ROSA, a software reuse system based on the processing of the natural language descriptions of software artifacts to automatically extract both verbal and nominal phrases from descriptions and to use this information to create frame-based indexing units for software components.

TL;DR: IBM's experiences with a corporate RSL, reuse incentive programs, and the results of an enterprise-wide initiative to develop reusable software for the RSL are presented.

TL;DR: The two major reasons for estimate alterations studied here are the project manager's experience and time constraints and the confidence of the projectmanager in the estimation model.

TL;DR: Two different alternative approaches to the design choice of how to provide access to remote data referenced by the transaction in a distributed RTDBS environment are described and analyzed.

TL;DR: This article defines ordinal measures of the complexity factors based on discrete mathematical structures of programs and the information content or entropy, transforms the different domains of software complexity in linear metric spaces in order to represent a program by a set of vectors whose magnitudes and distances represent metrics of the program components.

TL;DR: What a metrics plan is and an approach that combines a goal-questionmetric analysis with process maturity assessment and process modeling is described, which allows an organization to tailor metrics collection and analysis to the needs and characteristics of the project and organization that will use the metrics.

TL;DR: It is concluded that successful software reuse requires the selection of appropriate domains, systematic development of reusable modules based on domain analysis, and the commitment of senior management.

TL;DR: An approach to the design of tools to help software designers build repositories of software components and locate potentially reusable software in those repositories is described, named CodeFinder, which supports the process of retrieving software components when information needs are ill-defined and users are not familiar with vocabulary used in the repository.

TL;DR: It is demonstrated that formal methods for software development and safety analysis are being increasingly adopted in the safety-critical systems sector by describing several industrial-scale applications of formal methods.

TL;DR: It is claimed that all three types of reengineering are needed: reengineering at the levels of product, process, and systems management, and an approach at one level only may not be satisfactory.

TL;DR: The approach uses a Poisson analysis to model fault locality and a categorical multivariate regression analysis based on an ordered response model to model effort to estimate the fault correction effort at the project level.

TL;DR: This work describes the design and use of a fast, programmable tool that can perform syntactically oriented text-processing tasks for use in program understanding and transformation and takes a “traditional” compiler approach to the problem.

TL;DR: The purpose of this article is to analyze the incredible differences between object- oriented requirements and object-oriented design, explain why the transition between them is not and should not be easy, and provide guidance concerning how the transition should be made.

TL;DR: It is evident from the published literature that reasonable progress has been made in the purely technical areas of software reuse, however, there has not been as much progress in the other related areas necessitated by the diverse ramifications and implications ofSoftware reuse practice.

TL;DR: A two-phase encryption algorithm for data base systems that allows the encryption and decryption of fields within a record by means of writing and reading subkeys of fields and two algorithms for cryptographic relational algebra in data base system are developed.