"... In PAGE 3: ... Table 1 reports for each system, the number of extracted snapshots, the range of analyzed releases, the number of non-commented lines of code (KNLOC), and the number of classes (excluding anonymous classes). Table2 reports for each design pattern the minimum and maximum num- ber of instances identified in all the analyzed software sys- tem releases. Abbreviations of Design Pattern column refers to the following: FM = Factory Method, P=Prototype, S=Singleton, AC=Adapter-Command, C=Composite, D= Decorator, O=Observer, SS=State-Strategy, TM= Template Method, V=Visitor.... ..."

"... In PAGE 4: ...ig. 1. Basic Design Pattern Template We can think of the set of all design patterns in terms of two orthogonal criteria, jurisdiction and characterization. Table1 organizes our current set of patterns according to these criteria. Jurisdiction is the domain over which a pattern applies.... ..."

"... In PAGE 4: ...ig. 1. Basic Design Pattern Template We can think of the set of all design patterns in terms of two orthogonal criteria, jurisdiction and characterization. Table1 organizes our current set of patterns according to these criteria. Jurisdiction is the domain over which a pattern applies.... ..."

"... In PAGE 6: ...3 Categorization of Pattern Evolutions We studied the types of pattern evolutions of the design patterns listed in [9]. The result is shown in Table3 . For each design pattern, all possible evolution types of the design pattern are listed in the Pattern- Level Evolutions column.... ..."

"... In PAGE 6: ...1 Primitive Design Patterns This layer contains the design patterns which are heav- ily used in the design patterns of higher level and in object- oriented systems in general. Table3 gives a list of these pat- terns in alphabetic order and their respective purpose. The Composite design pattern seems to be the most important one as it is used by eight other design patterns.... ..."

"... In PAGE 4: ...ig. 1. Basic Design Pattern Template We can think of the set of all design patterns in terms of two orthogonal criteria, jurisdiction and characterization. Table1 organizes our current set of patterns according to these criteria. Jurisdiction is the domain over which a pattern applies.... ..."

"... In PAGE 4: ...ig. 1. Basic Design Pattern Template We can think of the set of all design patterns in terms of two orthogonal criteria, jurisdiction and characterization. Table1 organizes our current set of patterns according to these criteria. Jurisdiction is the domain over which a pattern applies.... ..."

"... In PAGE 3: ... Based on these and the general rules of software ergonomics (see in [5]) our pattern should accept the following criteria-groups. Table1 . shows the detailed criteria.... In PAGE 6: ... Unfortunately the design pattern does not solve all safety-related problems, but at least supports them, and allowing the verification of the rule by external checker pro- grams. Naturally the design pattern should be converted into the particular system, and this operator can modify the properties shown in the Table1 . Unfortunately the design patterns have no methods to protect the model.... ..."

"... In PAGE 15: ...1 Analysis Task Description The flrst step is to express the detection of the Blob as a sequence of actions to accomplish, as described by the Analysis Task Model (see Section 3). The speciflcation for the Blob detection task is presented in Table4 . This description is based on software metrics and general data analysis techniques.... In PAGE 15: ... This description is based on software metrics and general data analysis techniques. Method to accomplish Goal: Blob Detection 1: Find Extremum(wholeSystem, WMC, WMC = HIGH) 2: Filter Attributes(extremeClasses, LCOM5, LCOM5 = HIGH) 3: FOR EACH(c 2 fllteredClasses) REPEAT(Step 4 to Step 6) 4: IF(Verify Value(c, DIT, DIT = LOW)) GOTO(Step 5) ELSE(continue) 5: Inspect(c, class name, method signatures) 6: IF(Verify Property(c, type, controller class)) GOTO(Step 7) ELSE(CONTINUE) 7: Save(c, controller class) 8: FOR EACH (m 2 controllerClasses) REPEAT(Step 9) 9: Accomplish Sub-Goal: Data Class Veriflcation(m) Method to accomplish Goal: Data Class Veriflcation(class) 1: Filter Relationship(wholeSystem, Association Relationship, class) 2: Filter Attributes(associatedClasses,WMC = LOW, LCOM5 = LOW, DIT = LOW) 3: IF(Verify Property(filteredClasses, type, data class)) 4: Save(class, Blob) Table4 . Blob detection expressed using the AT model.... In PAGE 23: ... Reusability. Table4 presents the evaluations by re- spondents of the impact of design patterns on reusabil- ity. Overall, as shown in Table 8, reusability is felt as being slightly more negatively impacted by design pat- terns, with 12 negative patterns and 11 positive pat- terns.... ..."