G. Murphy. Lightweight Structural Summarization as an Aid to Software Evolution. PhD thesis, University of Washington, 1996.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....the same time, this exploration continues the evaluation of HASTI and CoSTH. It establishes that they are can be applied to analyze important tools issues within this research domain. Not only that, but it also shows that they have interesting things to say about them. 8. 1 RMTool Example RMTool [428 430] is a prototype tool that was designed for reverse engineering and software comprehension. Although nothing really precludes it from being applied to other tasks and problem domains (e.g. as Rigi has been [643] the original intent for RMTool was to understand software systems. Consequently that ....

....required that some understanding is needed of how the system is structured. Use Scenario One of the best ways to understand RMTool is through a scenario of use. A scenario of a software engineer understanding a Unix kernel is used here. This is the same scenario used in the RMTool literature [428] (although the narrative is modified slightly for presentation purposes) so the reader may refer to that literature for more details. An illustration of the general process of using the technique is shown in Figure 8.1. It goes as follows: 1. EXTRACT LLM. The engineer selects and configures ....

[Article contains additional citation context not shown here]

Murphy, G. C. Lightweight Structural Summarization as an Aid to Software Evolution. PhD thesis, Department of Computer Science and Engineering, University of Washington, 1996.

....space. In Section 3 we will explain why they can easily be constructed using declarative meta programming. Architectural drift or architectural erosion arises when changes that break the constraints of the original architecture, are made to the implementation. Conformance checking tools [11,18,9,10] try to verify whether an implementation (still) matches the architecture. When different architectural views on the same implementation are provided, we also need support for maintaining consistency between these different views. Tool support can vary according to the level of synchronization one ....

G. C. Murphy. Lightweight Structural Summarization as an Aid to Software Evolution. Ph.D. dissertation, University of Washington, 1996.

....architecture[6] In this paper, we refine the relationships in order to deal with evolution of CORBA based federated database systems, using the standard services of the Object Management Group[11] 13] 6] and without to rewrite the federation architecture. In comparison with other models [1] 12][20][22] the major advantage of our approach concerns the deal with multilanguage programs source codes and the federated databases, in both centralized and distributed environment. Our approach consider both the program source codes and database schemas, in an homogeneous representation. This allows ....

G. Murphy. Lightweight Structural Summarization as an Aid to Software Evolution. PhD thesis, University of Washington, July, 1996.

....rules, for centralized applications and database schemas evolution. In this paper, we propose an extension of this model to deal with the distributed components. With this extension, we analyze the change impact on distributed and heterogeneous databases. In comparison with other models [1] 14][21][23] the major advantage of our approach concerns the deal with multilanguage programs source codes and the heterogeneous databases, in both centralized and distributed environment. Most of the models proposed in the literature do not integrate multilanguage programs, manipulating data stored in ....

G. Murphy. Lightweight Structural Summarization as an Aid to Software Evolution. PhD thesis, University of Washington, July, 1996.

....models that are separate from a system s source (documentation, mental models , etc. can be useful for reasoning about many aspects of the system. However, dealing with these models is also risky because they may not be an accurate representation of the system s actual implementation [Mur96b] Conformance checking tools, such as RMTool[MNS95] and Pattern Lint [SSC96b] reduce these risks by showing whether and how an architectural model di ers from the source code evidence. Basically, the user provides a conformance checking tool with a set of components and relationships that are ....

Gail C. Murphy. Lightweight Structural Summarization as an Aid to Software Evolution. PhD thesis, University of Washington, July 1996.

....the high level entities and designation of the mapping by the software, for instance, are also characteristic of the software reflexion model approach from which this visualization technique is derived. Users of the software reflexion model approach have not had difficulties performing these steps [10, 11]. Our preliminary studies, then, focus on investigating the usefulness of the visualization. We report on two case studies. The first case study (Section 4.1) discusses the use of the visualization technique by one of the authors to determine why a Smalltalk implementation of a reverse engineering ....

....an engineer to apply it to a new system. We have been able to easily apply our technique to different systems because of the separation in our process between data gathering and visualization. Our visualization technique buildson the software reflexion model technique developed by Murphy et al. [12, 10]. The reflexion model technique helps an engineer access both static and dynamic information about a system by enabling a comparison between a posited high level model and a model representing informationextracted from either the static source or from a system s execution. Similar to our ....

[Article contains additional citation context not shown here]

G. C. Murphy. Lightweight Structural Summarization as an Aid to Software Evolution. Ph.D. Dissertation, Department of Computer Science and Engineering, University of Washington, 1996.

....Informal naming and file conventions were used to flag the columnar properties, but these are by no means constructive or highly visible. Indeed, an analysis of the architecture with a reflexion modeling tool was helpful in understanding some of the detailed relationships [Murphy et al. 95, Murphy 96] However, once this latent architecture was recognized and analytically codified, it nonetheless proved to be a valuable guide in resolving low level design issues as direct update was introduced into the tool [Griswold Notkin 95] 4 Conclusion Software architecture has been conceptualized ....

G. C. Murphy. Lightweight Structural Summarization as an Aid to Software Evolution. PhD dissertation, University of Washington, Department of Computer Science & Engineering, July 1996.

....they are lazy, but rather because it is time consuming and difficult to maintain logical but implicit relationships among documents. The software reflexion model technique was developed to help people perform various software engineering tasks by exploiting rather than removing this drift [Mur96][MNS95] More specifically, the technique helps an engineer compare artifacts by summarizing where one artifact (such as a design) is consistent with and inconsistent with another artifact (such as source) The technique helps an engineer detect, assess, and manage inconsistencies from a ....

....and inconsistent with another artifact (such as source) The technique helps an engineer detect, assess, and manage inconsistencies from a task specific viewpoint. The initial uses of reflexion models included design conformance tasks, assessing software structure prior to an implementation change [Mur96], and an experimental reengineering of the Excel code base by a Microsoft engineer [MN97] The users for these tasks identified a set of shortcomings of the basic tools and techniques. In this paper, we present a set of improvements to the reflexion model technique, each of which is aimed at ....

[Article contains additional citation context not shown here]

Murphy, G.C. Lightweight structural summarization as an aid to software evolution. Ph.D. dissertation, University of Washington, Seattle WA, 1996.

No context found.

G. Murphy. Lightweight Structural Summarization as an Aid to Software Evolution. PhD thesis, University of Washington, 1996.

No context found.

G. C. Murphy, Lightweight structural summarization as an aid to software evolution, Ph.D. thesis, Univeristy of Washington (1996).

No context found.

G. Murphy. Lightweight Structural Summarization as an Aid to Software Evolution. PhD thesis, University of Washington, 1996.

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