Showing papers in "Journal of Systems and Software in 1997"
••
TL;DR: A research study comparing three estimation techniques using function points as an estimate of system size based on regression analysis, artificial neural networks and case-based reasoning finds that case- based reasoning appears to have value for software development effort estimation models.
269 citations
••
TL;DR: The effectiveness of the mutation testing and all-uses test data adequacy criteria at various coverage levels, for randomly generated test sets, was mixed: at the highest coverage levels considered, mutation was more effective than all-use for five of the nine subjects, all- uses was moreeffective than mutation for two subjects, and there was no clear winner for two Subjects.
235 citations
••
TL;DR: This paper provides a motivation for reading as a quality improvement technology, based upon experiences in the Software Engineering Laboratory at NASA Goddard Space Flight Center and shows the evolution of the study of reading via a series of experiments.
144 citations
••
TL;DR: A unified framework for expressing techniques of classifying subsystems of a software system is presented, comprised of a consistent set of terminology, notation, and symbols that may be used to describe the input, output, and processing performed by these techniques.
103 citations
••
TL;DR: The SEPS model is designed to be a planning tool to examine trade-offs of cost, schedule, and functionality, and to test the implications of different managerial policies on a project's outcome.
71 citations
••
TL;DR: This article built descriptive models of the software process, defects, and cost and developed evaluative models that clarify the relationship between the basic metrics, the analysis method, and the goals of the analysis.
64 citations
••
TL;DR: The result of an evaluation of the guidelines on over two dozen government pilot studies is presented, showing that although the guidelines may be too rigorous, they form at least a foundation from which a useful set of steps for a particular pilot project might be tailored.
44 citations
••
TL;DR: This work introduces a modular logical and timing analysis methodology for a kind of high level Petri net named G-Nets that can be applied for complex software systems.
44 citations
••
TL;DR: A fault-classification scheme and a fault-seeding method that are based on the manifestation of faults in the program dependence graph (PDG) are presented and the operation of the fault seeder is used to perform a study of the effectiveness of dataflow testing and mutation testing.
44 citations
••
TL;DR: A dynamic resource allocation strategy for software module testing that takes into account the variations of the number of detected faults during testing, re-estimates the model parameters using all the available fault detection data and dynamically allocates the testing resources to the software modules is studied.
38 citations
••
TL;DR: The efforts being made to promote the reuse of requirements for engine control systems at Rolls-Smith Engine Controls Limited (RoSEC) are described, based on existing domain analysis techniques, and a forms-based tool that is prototyped which supports the reused of requirements during the development of new systems is presented.
••
TL;DR: A new electronic voting protocol with IC cards is proposed, so secure that it can meet all security requirements and only a legitimate voter can cast a valid ballot and only once.
••
TL;DR: Results indicate that the overall complexity of the studied distributed systems overwhelmed the ease-of-use and simplicity of their components — thus increasing the overall difficulty of software maintenance.
••
TL;DR: For software projects developed through multiple builds, it is shown that a Poisson model that incorporates a measure of testing effort is applicable and that software development environment volatility is a strong determinant of subprogram defects.
••
TL;DR: This research examines the relationship between programming productivity and program structure measures in a COBOL programming environment and indicates that program development time is significantly associated with span of control and levels of control used in the program.
••
TL;DR: The results of a study comparing Function Point measures are stated, and they are compared against effort and LOC, and the relationships among the variables are examined.
••
TL;DR: This survey shows the greatest use of prototyping in the design phase and least in the implementation phase; its use in the analysis phase is comparatively low; and there are some significant differences in respondents' perceptions of the two approaches.
••
TL;DR: In this article, the authors study the effects of reuse across seven projects in a narrow domain from a single development organization and find significant differences between errors associated with new and various types of reused components in terms of the types of errors committed.
••
TL;DR: The development of a method to identify objects in legacy systems, specifically those coded in the imperative language, FORTRAN-77, is discussed, using a modification of the program slicing concept introduced by Weiser in 1984.
••
TL;DR: The paper shows how QFD focused its effort to produce a product for customers with diverse needs and also how to tailor the technique for use with modern Object-Oriented Design software technology.
••
TL;DR: The results of the analysis show that physical stress could generate faults at a higher rate than mental stress even when it appeared for a short period, independent of design methodology.
••
TL;DR: A case study for the empirical validation of the usefulness of two recent research results aimed at improving the branch testing process, which confirmed the validity of the path generation method and provided evidence that this method can reduce the test effort, especially for non-expert testers.
••
TL;DR: This paper proposes new Petri net based model, which is called CTPN (Cryptographic Timed Petri Net), and it is found to have executable, formal, graphical textual, and consistent characteristics suitable for the specification and analysis of cryptographic protocols.
••
TL;DR: A model for estimating software size based on the program design and other documents, then evaluated by looking at some application examples, providing a measure of the accuracy of estimates.
••
TL;DR: An experimental tool to help software maintainers to disabbreviate existing source programs, which is implemented using Prolog, is an interactive and intelligent system which can suggest name replacements to its users.
••
TL;DR: A model that estimates small-scale software development effort in 4GL and end-user computing environments is developed and two of the most popular models currently used to estimate software development efforts, lines of code (LOC), and function points (FP) are evaluated.
••
TL;DR: This paper presents the strategy, implementation, and experience with tool support for software measurement, analysis, and quality improvement in a commercial software development environment and employed existing internal tools, commercial off-the-shelf tools, and new tools that were developed to gather and analyze data.
•
TL;DR: In this paper, the authors report the results of a study focused on experienced COBOL programmers and their transition to the C language, which was conducted at a major financial services firm that is in the process of transforming its application development practice from a primarily mainframe, CoBOL-based environment to a client-server, C-based one.
••
TL;DR: The results suggest that life cycle development stages critically impact the overall perception of system effectiveness and the nature of the interactions within the expert system development process.
••
TL;DR: Results validate the general perception that COBOL programmers do not have very positive attitudes towards C and point to the contingent effects of job insecurity and organizational tenure on training outcomes.