Printer friendly

What does TROOP stand for?

TROOP stands for Transformation of Object-Oriented design using design Patterns


This definition appears very rarely

Other Resources: Acronym Finder has 3 verified definitions for TROOP

Samples in periodicals archive:

CiteSeerX - Document Details (Isaac Councill, Lee Giles, Pradeep Teregowda): In re-engineering object-oriented legacy code, it is frequently useful to introduce a design pattern in order to improve specific non-functional requirements (e.g., maintainability enhancement). This paper presents a methodology for the development of a quality-driven re-engineering framework for object-oriented systems. First, a catalogue of design motifs (primitive design pattern transformations) is presented. Then, the transformations for the design patterns in the GoF book are defined as a composition of these primitive transformations. Non-functional requirements for the migrant system can be encoded using soft-goal interdependency graphs and can be associated with design pattern transformations that are applied for the migration of an object-oriented legacy system. 1
CiteSeerX - Document Details (Isaac Councill, Lee Giles, Pradeep Teregowda): Developing code free of defects is a major concern for the object-oriented software community. In this paper, we classify design defects as those within classes ( intra-class), those among classes ( interclasses) , and those of semantic nature ( behavioral). Then, we introduce guidelines to automate the detection and correction of inter-class design defects: We assume that design patterns embody good architectural solutions and that a group of entities with organization similar, but not equal, to a design pattern represents an inter-class design defect. Thus, the transformation of such a group of entities, such that its organization complies exactly with a design pattern, corresponds to the correction of an inter-class design defect. We use a meta-model to describe design patterns and we exploit the descriptions to infer sets of detection and transformation rules. A constraints solver with explanations uses the descriptions and rules to recognize groups of entities with organizations similar to the described design patterns. A transformation engine modifies the source code to comply with the recognized distorted design patterns. We apply these guidelines on the Composite pattern using Ptidej, our prototype tool that integrates the complete guidelines.