QuoteRef: howdWE1_1990

references g-h
testing by program mutation
source-rich system
flavor analysis and typestates for supplementary type checking
dynamic type checking
plan-based task scheduling


Howden, W.E., "Comments analysis and programming errors", IEEE Transactions on Software Engineering, 16 , 1, pp. 72-81, January 1990. Google

72 ;;Quote: mutation and perturbation testing are good for catching errors of commission but poor for errors of omission
72 ;;Quote: the error-based approach to testing develops tests for each possible class of errors
72+;;Quote: a decomposition error occurs when a programmer makes a false assumption about some other part of the program
72 ;;Quote: software errors often occur when information is lost because it is not part of the program
73 ;;Quote: a flavor is a property of an object that changes during program execution; e.g., 'total' may be initialized, partial sum, total sum
73 ;;Quote: handle infeasible paths by assigning flavors to a special 'path condition'; stop path exploration when the flavor assumption fails
73 ;;Quote: the flavor analyzer does not interpret data objects; so A(T) and A(R) are treated separately
74 ;;Quote: flavor analysis treats task invocation and return the same as subroutine invocation and return
75 ;;Quote: flavor and scheduling analysis by comment analysis on data state and operator state expressions; give assumptions and assertions
75+;;Quote: a data state expression in flavor analysis is the set of data properties that objects can have at a program location
75+;;Quote: an operator state expression in scheduling analysis is the valid operator sequences that can reach a program location
76 ;;Quote: use assumption and assertion comments to state that x has a single property or some property with other properties
76 ;;Quote: input flavor statements specify data assumptions at function invocation; output statements specify data assertions at end
76+;;Quote: an always flavor statement specifies data assumptions at every program location
77 ;;Quote: operator state expressions--an assumption denotes the programmer's expectation that all paths imply some operator state; an assertion becomes part of the operator state
80 ;;Quote: used flavor analysis on an existing 70K assembly language program; effective for tracking registers and temporary variables
80+;;Quote: flavor analysis comments on an existing program were similar to the original comments

Related Topics up

ThesaHelp: references g-h (299 items)
Topic: testing by program mutation (18 items)
Group: testing   (18 topics, 551 quotes)
Topic: bugs (65 items)
Topic: source-rich system (27 items)
Topic: flavor analysis and typestates for supplementary type checking (68 items)
Topic: dynamic type checking (43 items)
Topic: aliasing (28 items)
Topic: plan-based task scheduling (13 items)
Topic: comments (23 items)

Collected barberCB 9/90
Copyright © 2002-2008 by C. Bradford Barber. All rights reserved.
Thesa is a trademark of C. Bradford Barber.