....is done by providing a custom class loader. Other non portable load time instrumentation alternatives were comprehensively explored by Duncan and Hlzle [DH99] Consens et al. CHM94, CMR92] use the Hy visualization system to find errors using post mortem event traces. De Pauw et al. [DLVW98] and Walker et al. WM 98] use program event traces to visualize program execution patterns and event based object relationships, such as method invocations and object creation. Similarly, Bruegge and Hibbard [BH83] use generalized path expressions that refer to program events and variables to ....
de Pauw, W.; Lorenz, D.; Vlissides, J.; Wegman, M. Execution Patterns in Object-Oriented Visualization. Proceedings of the Fourth USENIX Conference on Object-Oriented Technologies and Systems, Sante Fe, NM, USA, 27-30 April 1998, USENIX Association, 1998. pp. 219-34.
....on industrial case studies showed that tools are missing which aid in understanding the dynamic behaviour of object oriented applications. Most tools for understanding behaviour display a large volume of low level information and rely on visual techniques and cues for navigating this information [8, 12]. We therefore looked for ways in which to recover more succinct models of behaviour. In [23] we investigated the use of dynamic information for obtaining high level models of object oriented applications. In contrast, the work described here is aimed at recovering fine grained models which ....
....control flow information required for deriving collaborations and with information about the context in which methods of specific instances are invoked. Program tracing, however, results in a great volume of low level information from which we must sift the details relevant for our investigation [8, 12, 27]. Here, the problems of focus, granularity and scalability must be addressed: Focus and Granularity. In order to be manageable, it is necessary to break the program trace up into chunks representing collaborations. Also, we are not interested in all collaborations, nor in all the details of a ....
[Article contains additional citation context not shown here]
W. DePauw, D. Lorenz, J. Vlissides, and M. Wegman. Execution patterns in object-oriented visualization. In Proceedings Conference on Object-Oriented Technologies and Systems (COOTS '98). USENIX, 1998. 9
....understand the impact tracing had on a system s performance, which they found to be minimal. Similar work has been done by E. S. Cho et al. 6] that showed an approach to clustering CORBA objects from information in a CORBA trace. Trace approaches can be divided into macroscopic and microscopic [9]. Macroscopic approaches collect cumulative information while microscopic approaches concentrate on sequences of messages. No one approach is better than the other. Both can be used for comprehension, although they focus on different aspects. As an example, we often find macroscopic tools ....
....Therefore, we present information summary statistics by time period (per hour, etc. This is in order to build detailed operational profiles [18] One uses microscopic approaches to learn how something is accomplished or to get more detail. Examples of this are Karam [14] and De Pauw, et al. [9]. Karam shows execution traces on a timeline where it possible to zoom in and out. His system provides a state machine based interpreter for events. This, in turn, is used to construct timelines using an oscilloscope metaphor. The metaphor is further enhanced with annotation symbols that overlay ....
[Article contains additional citation context not shown here]
De Pauw, W., Lorenz, D., Vlissides, J., Wegman, M. (1998) Execution patterns in object-oriented visualisation, Proceedings of the Fourth USENIX Conference on Object-Oriented Technologies and Systems, Santa Fe, NM, April 27-30, 219--234.
....the Behavior of Java Programs Tarja Syst a Software Systems Laboratory Tampere University of Technology P.O. Box 553, FIN 33101 Tampere, Finland tsysta cs.tut.fi Abstract To fully understand the underlying architecture of an object oriented software system, both static and dynamic analyses are needed. Dynamic reverse engineering techniques are especially important for understanding the run time behavior of objects in ....
....Scenario diagrams and state diagrams are variations of UML sequence diagrams and statechart diagrams, respectively. Many dynamic reverse engineering tools use variations of Message Sequence Charts (MSCs) to visualize the run time behavior of the target object oriented software system [2, 3, 6, 7, 10] In Shimba, the visualization of the run time behavior of object oriented software has been taken one step further: not only scenario diagrams but also the final specification of the dynamic behavior, i.e. the state diagram, is composed automatically as a result of the execution of a target ....
[Article contains additional citation context not shown here]
W. D. Pauw, D. Lorenz, J. Vlissides, and M. Wegman. Execution patterns in object-oriented visualization. In Proc. of the COOTS, 1998.
....can point to mistakes in the model. Taking it one step further, one can even imagine the estimated values (for example the number of elements in a list) in the model being automatically updated based on the measurement results. Some more information on visualising system dynamics may be found in [PAU98] and [WAL98] 9.2.4 Unknown Resource Usage Even when performance is considered from the very start of the development process, problems may still arise. Determining which resources to consider is a likely source of problems. If a certain resource is used by software components but it is not ....
W. De Pauw, D. Lorenz, J. Vlissides, M. Wegman, Execution Patterns in Object-Oriented Visualization, Conference on Object-Oriented Technologies and Systems, pp. 219-234, USENIX Association, 1998.
....the target system typically results in many SCED scenarios during the dynamic reverse engineering process. Hence, means to raise the level of abstraction of the scenarios are needed. A commonly used approach is to search for behavioral patterns. This approach is used in Jinsight [12] and Ovation [11] In some cases it is meaningful to build abstractions for the scenarios based on static criteria. The original scenarios show the interaction between objects or classes. From those scenarios it is difficult to get a flavor of the overall communication, e.g. the interaction between packages or ....
....Vertical abstraction decreases the number of horizontal arcs in a scenario. They can be built, e.g. by omitting internal events that are sent and received by the same participant or by collapsing method call chains into a single call event. Such approaches are used in Scene [7] and Ovation [11] in which events can be hidden and expanded by a simple mouse click. The approach to be introduced next can be used to build both horizontal and vertical abstractions. The static abstractions formed in Rigi define the vertical lines that will be grouped together. When using a reverse ....
W. D. Pauw, D. Lorenz, J. Vlissides, and M. Wegman. Execution patterns in object-oriented visualization. In Proc. of the USENIX Conference on Object-Oriented Technologies and Systems (COOTS), Sante Fe, New Mexico, April 1998.
....patterns in a system. The visualizations they produce are also at a fine grained level. Vlissides et al. use a different notion of pattern, which they refer to as execution patterns, to help developers investigate the large amount of fine grained execution information available about a system [3]. Specifically, they allow a developer to query an on line animation for patterns appearing in a dynamic execution stream. In both the Program Explorer and execution pattern approaches, the developer must apply detailed knowledge about a system to formulate appropriate queries. Jerding et al. have ....
W. De Pauw, D. Lorenz, J. Vlissides, and M. Wegman. Execution patterns in object-oriented visualization. In Proceedings of the 4th USENIX Conference on ObjectOriented Technologies and Systems, pp. 219--234, 1998.
....[Laf97] discusses visual debugging in Java using source code instrumentation or JVM changes. We opted for the third method class file instrumentation at load time. Consens et al. CHM94, CMR92] use the Hy visualization system to find errors using post mortem event traces. De Pauw et al. [DLVW98] and Walker et al. WM 98] use program event traces to visualize program execution patterns and event based object relationships, such as method invocations and object creation. This work is complementary to ours because it focuses on querying and visualizing run time events while we query object ....
de Pauw, W.; Lorenz, D.; Vlissides, J.; Wegman, M. Execution Patterns in Object-Oriented Visualization. Proceedings of the Fourth USENIX Conference on Object-Oriented Technologies and Systems, Sante Fe, NM, USA, 27-30 April 1998, USENIX Association, 1998. pp. 219-34.
....possible to map class diagrams to code and vice versa. For object interaction diagrams, however, there is a key difficulty. There is not enough information in the interaction diagram to do the job. One can try to overcome this difficulty and construct code by abstracting over execution patterns [DLWV98] in object interaction diagrams. But this would require a working program to begin with. In this paper, we show an incremental direct technique for moving from an interaction diagram to code. Class Diagram Component Diagram Deployment Diagram Object Diagram Static Aspects Use Case Diagram Activity ....
Wim De Pauw, David Lorenz, Mark Wegman, and John Vlissides. Execution Patterns in Object -Oriented Visualization. In Proceedings of The Fourth Conference on Object-Oriented Technologies and Systems, pages 219-234, Santa Fe, New Mexico, April 27-30, 1998. USENIX.