A. Podgurski and L. Clarke, "A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance," IEEE Transactions of Software Engineering, vol. 16, no. 9 (1990), pp. 965-979.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....based upon the phase of the software life cycle to which the description applies and the type of system being developed. Early work in understanding system dependencies concentrated on programs that are comprised of a single procedure written in sequential, imperative programming languages [17, 41]; in this dissertation these types of programs are referred to as uni procedure programs. More recently, research has been directed at more complex types of languages used to describe programs with procedure calls [22, 27, 33, 37, 47] object oriented programs [31, 57] concurrent programs [14, ....

.... object oriented programs [57] software architectures [48, 55] and hardware architectures [15] Work in the area of identifying control dependencies in uni procedure programs produced two, very similar formal models, one by Ottenstein and Ottenstein [39] and the other by Podgurski and Clarke [41]. These formal models are based on combining control ow and forward dominance information to produce control dependence information. There have been several attempts to directly extend these models for application to programs with procedure calls [22, 27, 37, 47] which we refer to as ....

[Article contains additional citation context not shown here]

A. Podgurski and L.A. Clarke. A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance. IEEE Transactions on Software Engineering, 16(9):965-979, September 1990.

....not cope with the nondeterministic execution of statements. Thus, the development of techniques and tools to support analyzing concurrent Ada 95 software is urgently needed. Dependency analysis is an analysis technique to identify and determine various program dependencies in program source codes [5, 17]. It has been widely used in software engineering activities, such as program understanding, testing, debugging, and maintenance [1, 5, 8, 10, 11, 17, 18] It provides a solution for analyzing concurrent programs. This work was supported in part by the National Natural Science Foundation of ....

....Ada 95 software is urgently needed. Dependency analysis is an analysis technique to identify and determine various program dependencies in program source codes [5, 17] It has been widely used in software engineering activities, such as program understanding, testing, debugging, and maintenance [1, 5, 8, 10, 11, 17, 18]. It provides a solution for analyzing concurrent programs. This work was supported in part by the National Natural Science Foundation of China (NSFC) 60073012) National Science Foundation of Jiangsu, China (BK2001004) Opening Foundation of State Key Laboratory of Software Engineering in ....

Podgurski, A., Clarke, L.A.: Formal Model of Program Dependencies and its Implications for Software Testing, Debugging and Maintenance. IEEE Transactions on software Engineering, 1990, 16(9): 965-979

....has evolved from the related field of program visualisation. Visualisations of a program s source code are derived from dependencies that exist within and between program source documents. Since the late seventies, much work has gone into the analysis and extraction of program dependencies [9, 10, 17, 28, 31, 34, 39]. This work has paved the way for a wide variety of tools that provide visualisation of program dependencies. A predetermined set of software visualisations will not necessarily meet al..l of the user s comprehension needs. Jackendoff[18] tells us that Perception is the result of interaction ....

A. Podgurski and L. A. Clarke. A formal model of program dependencies and its implications for software testing, debugging and maintenance. IEEE Transactions on Software Engineering, 16(9):965--979, September 1990.

....relationships that exist in an architectural specification that, when collected together, produce a chain of dependencies that can be followed during analysis. The traditional view of dependence analysis is based on control and data flow relationships associated with functions and variables [1, 5, 8, 15, 19, 20]. This research takes a broader view of dependence relationships that is more appropriate to the concerns of architectures and their attention to component interactions. In particular, both the structural and the behavioral relationships among components expressed in current day formal ....

....of static concurrency analysis tools to architecture descriptions. ProDAG [21] is a program dependence analysis tool set that performs statement level dependence analysis. ProDAG allows one to create and access various predefined relationships originally identified by Podgurski and Clarke [20]. The technique of chaining, the dependence analysis technique proposed as a focus of this research, raises these ideas to the architectural level, as well as incorporating the notion of structural dependence. 1 Chaining is similar in nature to Weiser s concept of program slicing [24] Korel and ....

A. Podgurski and L.A. Clarke. A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance. IEEE Transactions on Software Engineering, 16(9):965-- 979, September 1990.

.... The development of e#cient and precise dependence analysis algorithms continues as an active area of research among compiler designers (e.g. 4, 9, 13] The application of dependence analysis techniques to aid program understanding and impact analysis has been widely studied (e.g. [19, 21, 23]) The creation of both static and dynamic program slices has been a focus for many researchers (e.g. 28, 30] Sloane and Holdsworth [25] suggest generalizing the concept of program slicing and suggest the potential for slicing non imperative programs. Our research takes a broader view of ....

A. Podgurski and L.A. Clarke. A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance. IEEE Transactions on Software Engineering, 16(9):965--979, September 1990.

....indicate in what context a function is called. We see two mechanisms for providing this information: one, enhance the instrumentation of the executable so that the call stacks are output rather than function entries in isolation, and, two, synthesize these relationships using program dependence [31, 69] 137 information. The second body of additional information that could be added relates to the program s data structures. These data structures are manipulated within the context of the functions that make up the information, and they represent additional constraints and relationships not captured ....

A. Podgurski and L.A. Clarke. A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance. IEEE Transactions on Software Engineering, 16(9):965--979, September 1990.

....based on relationships between control structures, such as data flow criteria (e.g. all def and all use coverage) Clarke et al. 5] compare several families of data flow criteria; each family forms a hierarchy reflecting the relative comprehensive coverage of the criteria. Podgurski and Clarke [13] consider more general dependence relationships between components. This idea of developing a family of structural criteria based on relative coverage has also been extended to define test criteria for concurrency [16] Another structural approach is fault based test criteria, which prescribe test ....

A. Podgurski and L.A. Clarke. A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance. IEEE Transactions on Software Engineering, 16(9):965--979, September 1990.

.... The development of e#cient and precise dependence analysis algorithms continues as an active area of research among compiler designers (e.g. 4, 9] The application of dependence analysis techniques to aid program understanding and impact analysis has also been widely studied (e.g. [19, 22, 24]) Our research takes a broader view of dependence relationships that is more appropriate to the concerns of architectures and their attention to component interactions. In particular, both the structural and the behavioral relationships among components expressed in current day formal ADLs, such ....

A. Podgurski and L.A. Clarke. A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance. IEEE Transactions on Software Engineering, 16(9):965-- 979, September 1990.

....parallelizing Fortran compilers use PDGs to analyze dependencies among iterations of a loop in order to schedule the loop iterations for correct parallel execution. CDGs, both by themselves and as part of PDGs, have also been used in a variety of ways in testing and analysis [Harrold et al. 1993; Podgurski and Clarke 1990]. Constructing CDGs for arbitrary programs is a complex task; implementations of CDG tools can run into several thousand lines of code. Traditionally, a CDG is constructed by first deriving a control flow graph (CFG) from an AST or ASG and then performing various transitive closure and ....

PODGURSKI, A. AND CLARKE, L. 1990. A formal model of program dependencies and its implications for software testing, debugging, and maintenance. IEEE Trans. Softw. Eng. 16, 9 (Sept.), 965--979.

....specification. Links connect elements of the specification that are directly related, producing a chain of dependencies that can be followed during analysis. The traditional view of dependence analysis is based on control and data flow relationships associated with functions and variables [1, 4, 5, 12, 15, 16]. We take a broader view of dependence relationships that is more appropriate to the concerns of architectures and their attention to component interactions. In particular, we look at both the structural and the behavioral relationships among components expressed in current day formal architecture ....

....languages and combines the information with behavioral dependencies. ProDAG [18] is a program dependence analysis toolset that performs statement level dependence analysis. ProDAG allows one to create and access various predefined relationships originally identified by Podgurski and Clarke [16]. The technique of chaining raises these ideas to the architectural level, as well as incorporating the notion of structural dependence. Sloane and Holdsworth [19] suggest advanced applications for Weiser s concept of program slicing [22] in which the basis for analysis includes aspects other ....

A. Podgurski and L.A. Clarke. A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance. IEEE Transactions on Software Engineering, 16(9):965-- 979, September 1990.

....compilers use PDGs to analyze dependencies among iterations of a loop in order to schedule the loop iterations for correct parallel execution. CDGs, both by themselves and as part of PDGs, have also been used in a variety of ways in testing and analysis. For examples, see Podgurski and Clarke [8], Harrold et al. 7] and the citations contained therein. Constructing CDGs for arbitrary programs is a complex task; implementations of CDG tools can run 3 The other main component of a PDG is the data dependence graph. into several thousand lines of code. Traditionally, a CDG is constructed ....

A. Podgurski and L.A. Clarke. A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance. IEEE Transactions on Software Engineering, 16(9):965--979, September 1990.

....the queries made by a user. Architecturally, Aladdin is similar to ProDAG [22] an implementation level dependence analysis tool for Ada and C programs. ProDAG uses a the former approach to identifying dependencies based on the program dependence relationships defined by Podgurski and Clarke [20]. Dependence analysis is performed by both ProDAG and Aladdin in a two step process. First, a language specific intermediate representation is created, and then language independent analysis is performed over this representation. In Aladdin, the representation consists of a set of cells, where ....

A. Podgurski and L.A. Clarke. A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance. IEEE Transactions on Software Engineering, 16(9):965--979, September 1990.

No context found.

A. Podgurski and L. Clarke, "A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance," IEEE Transactions of Software Engineering, vol. 16, no. 9 (1990), pp. 965-979.

No context found.

A. Podgurski and L.A. Clarke. A Formal Model of Program Dependencies and its Implications for Software Testing, Debugging, and Maintenance. IEEE Transactions on Software Engineering, 16(9):965-979, September 1990.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC