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

TL;DR: This paper describes several types of interesting cognitive events that were gathered from professional programmers as they were engaged in a program-understanding task and used to derive a computational model of the programmers' mental processes.

TL;DR: Vidoetaped protocols of experienced programmers as they enhanced a personnel data base program are analyzed and it is suggested that there are two strategies for program understanding, the systematic strategy and the as-needed strategy.

TL;DR: An improved technique for reviewing designs is described, based on the following ideas, drawn from the application of active design reviews to the Naval Research Laboratory's Software Cost Reduction Project.

TL;DR: Algorithms used for determining whether or not a set of tasks is schedulable in a system having r resources are studied, and if so, determining a schedule for it.

TL;DR: This paper proposes a method of measuring the "macrocomplexity", i.e., how difficult the overall structure of the software is to deal with, as well as the microcomplexity, using data obtained during the development of a compiler/environment project.

TL;DR: This study reexamined one basic relationship proposed by the theory of software science: that between estimated and actual program length, and showed that the apparent agreement between these quantities is a mathematic artifact.

TL;DR: The productivity model developed was able to explain over 70% of the productivity variation found in Cobol, Pick/Basic, and Focus implementation environments and could be used as a basis for project planning and control for different organizations, hardware environments, operating systems, or development methodologies.

TL;DR: The Cleanroom software development process which has been developed by the IBM Federal Systems Division combines both ideas into an effective development tool and results in software with fewer errors which are both easier to find and to fix.

TL;DR: This paper takes the view that information pertaining to the configurations of a system constitute a basic source of knowledge about the system's design and how its component modules fit together, and uses a special language called NuMIL, which captures the interdependencies between the interfaces of components within a system.

TL;DR: ADA/SDP is identified as a program design language with many of the right features and some of the necessary tools; however, more are needed, and proposals for these are given.

TL;DR: An architecture for a sizing model for applications systems is presented, its major components are identified, and their general functions described.

TL;DR: This paper investigated the effects of computer programming skills on the writing of ordinary instructions and found that advanced programmers used more looping and programming action statements than Naïve or Beginner users, even when writing to another person.

TL;DR: SoftCost-R as discussed by the authors is a work-breakdown structure-oriented IBM PC-based estimating package used to forecast costs and schedules for software projects, which employs parametric and statistical relationships to provide its users with what-if analysis capabilities that allow them to look at different cost and schedule options.

TL;DR: A modular implementation, whose structure follows that of the formal definition, is developed by a combination of hand coding and semiformal transformations that bring the definition down to the level of a program in a Pascal-like language.

TL;DR: The conditions necessary for a prepaging policy to possess the memory inclusion property are examined and cost analysis techniques are developed that are fairer and more detailed than those that have been used to report the performances of prepaging policies in the past.

TL;DR: A method for detecting the presence of a computer virus and removing it from a computer system is presented, which would be applicable even if the virus had caused the system to crash.

TL;DR: A high-level conceptual framework—a taxonomy—for programming languages with language constructs for specification of cosequential and concurrent processes is described, concerning different patterns in which control can be transferred between the processes.

TL;DR: A model that characterizes one particular dialogue for menu-based interaction is presented, actually a sequence of models, hierarchically structured, where each successive model builds on its predecessor by introducing additional characterization elements.

TL;DR: A method for selecting test data that uses reasoning to derive test cases that show incongruence between assertions, i.e., what the programmer thinks the program does and what the program actually does is presented.

TL;DR: A Sum-of-Products checksum can be used to discretely identify data files in a manner that is similar to the way fingerprints are used for the identification of people, providing a higher confidence of accuracy than physical security of media and data alone.

TL;DR: Several marketing considerations that are especially appropriate for software products are discussed, including the importance of focusing on customer needs, market segmentation, developing a marketing strategy, the software product life cycle, strategies for positioning a software product, selecting an effective brand name, and the use of direct marketing.

TL;DR: This paper discusses the analysis, verification, and design of programs containing executable assertions, a common way to validate programs.

TL;DR: This paper classifies authorization requirements and presents a language for their specification, and presents an algorithm to derive a conceptual model where conditional and dynamic authorization upon database resources is represented.

TL;DR: In this paper, a study of computer science literature and psychology research was made to identify the types of conceptual units which should be captured within encapsulation units, and guidelines were developed to aid in the architectural design and implementation of software systems.

TL;DR: A formatting discipline for Pascal programs is proposed, formalized using an Extended Backus-Naur Form (EBNF) description, to provide a better view of the syntactic structure of the programs and to ease the reading of other people's programs.

TL;DR: This architecture is one of the first attempts to develop an effective decomposition of computer systems into integrated systems of specialized subsystems and concentrates on creating the image of a single system despite being composed of multiple heterogeneous subsystems.

TL;DR: It is argued that the hierarchical scope rules of Pascal violate accepted criteria for large program design and FORTRAN is shown to obey these criteria in its global data rules only.

TL;DR: This paper compares two algorithm development strategies suitable for carrying out the specialization phase of program development based on the following underlying idea: to increase software reliability the same level of attention must be devoted to the code and the specification synthesis.

TL;DR: The impact of tuning issues on attempts to validate the model against actual data is reviewed and aspects of CICS performance that are not represented by analytic models based on traditional SMF and RMF data are discussed.

TL;DR: The DRAT virtual printer module hides details of a wide variety of printing engines, allowing flexibility for the user while minimizing the effort of specifying options.