Reusability Analysis for Shipbuilding Components Modeled in XML and Java

Transcription

1 Reusability Analysis for Shipbuilding Coponents Modeled in XML and Java Prof. Steven A. Deurjian, Sr., Jeffrey R. Ellis, Rodrigo Caballero, Hai Lin, and Xiaopei Wang Coputer Science & Engineering Departent The University of Connecticut Prof. Donald M. Needha Coputer Science Departent U.S. Naval Acadey (860) June2001.OOReuse-1 Overview Reusability Model, Layers, and Fraework (SD) q Can we Constrain Reusable Coponents? q Can we Define a Reuse Model with Layers? Reusability and XML (DN) q Ipact of XML Abstractions on Reuse q Linking Resources in XML Prototyping Progress in DRE and TCC (JE & SD) q Status of CSE367 Project q Work by JE on Parser and Other Capabilities q Planned Work for Upcoing Months Reusability and Genetic Algoriths (RC & SD) June2001.OOReuse-2 1

2 Reusability Model, Layers, and Fraework (SD) Application is Designed with Abstractions (Class, Interface, Package, Coponent) Apply the Reuse Fraework to the Classes, Interfaces, Packages, and Coponents q Assign Generality Levels q Deterine Related Classes, Coponents q Iterate Until Obtain Marking that is Consistent with the Goals/Objectives of Application Proble: Is it Possible to Organize or Copartentalize the Application s Classes, Interfaces, Packages, and Coponents Fro Different Perspectives Based on Requireents? q Copartents - Previously Called Layers q Represent Chunks of Functionality June2001.OOReuse-3 Reuse Model Issues fro Last Meeting Clarify/Redefine Related Characterization q Transitivity of Related q W R to A, B, and C vs. W R to A, B, or C Coon Definitions for Package/Coponent q How is Marking of Package/Coponent Deterined? Least General Class Sets Package/Coponent Generality q Packages/Coponents Must Obey All Generality Rules of the Model/Fraework Inclusion of Interfaces into Model/Fraework Design Patterns and Ipact on Reuse Layering and the Reuse Model (Our Focus) June2001.OOReuse-4 2

3 Proble Doain Layering Discussion fro October 2000 Meeting Notion of General/Specific Ipacted by Layering? Layer Coponent Coon Person Manufacturing Part Shipbuilding Not OK Piping-Part Part OK Copany-Specific Sub-Piping Piping-PartPart June2001.OOReuse-5 Recall the Different Abstractions Classes and Hierarchies q Building Blocks of Application q Independent Classes of All Types q Generalization and Specialization Interfaces q Specification of Behavior q Never Instantiated Note: We Must Reconcile Our and EB Abstraction Definitions Packages q Organize Classes and/or Hierarchies into Naed Conceptual Units Coponents q Application-Oriented q Logical and Physical Associations of Interfaces, Classes, Packages q Purpose: Represent a Meaningful Chunk of Functionality q This is a Design Tie Coponent (e.g., a Non-Instantiated Bean)! June2001.OOReuse-6 3

4 Relating the Different Abstractions Interface Class Coponent Package Contains - Type Level Uses - Instance Level June2001.OOReuse-7 Abstractions and Application INT_1 CL2 CL1 CL3 INT_2 INT_3 CL6 Package A CL9 CL4 CL5 Coponent X Package B INT_4 Coponent Y CL7 Package C INT_6 INT_5 CL8 June2001.OOReuse-8 4

5 Abstractions and Copartents Soe Saple Copartents? INT_1 CL2 CL1 CL3 INT_2 INT_3 CL6 Package A CL9 CL4 CL5 Coponent X Package B INT_4 Coponent Y CL7 Package C INT_6 INT_5 CL8 June2001.OOReuse-9 Proposed Proble Solution Define Reusability Node to Represent the Different Copartents of Application s Classes, Interfaces, Packages, and Coponents Specify the Rules for: q Coposition of a Reusability Node q Dependencies Aong Reusability Nodes With these Rules, Result is a Reusability Graph of Reusability Nodes with Reusability Dependencies Reusability Graph can be Layered Objectives: q Forally Define Reusability Node, Dependency, Graph, and Layer q Can we Autoate the Process When Given Source Code for Application? June2001.OOReuse-10 5

6 Definition 1: Reusability Node A Reusability Node (RN) is a Set of Classes (Cl( Cl), Packages (P), Interfaces (I), and Coponents (Co) Marked With Varying Levels of Generality Entities in RN Must Satisfy Current Reuse Analysis w.r.t. General/Specific/Related, Coupling Counts, etc. CL1 RN x as Shown on Right INT_1 Classes, Packages, CL2 CL3 INT_2 INT_3 Interfaces, Coponents CL4 are Labeled as follows: CL5 Coponent X Package B q G xi for i = 1 n x are n x Generality levels June2001.OOReuse-11 Assuptions: Reusability Node Is the Makeup and Content of a RN Constrained? What are Possible Constraints on RN x? Levels of Generality q At Most 3 Different Generality Levels Replication q Classes in Exactly One RN q Can Packages/Coponents CL1 INT_1 be in Multiple RNs? q Interfaces Can be in One CL2 CL3 INT_2 or More Different RNs CL4 q Do Coponents/Packages CL5 Package B have Generality Level? INT_3 Coponent X June2001.OOReuse-12 6

7 Objective: Reusability Node Given Source Code (Classes, Interfaces, Packages, and Coponents) for Application, is it Possible to Dynaically/Autoatically Deterine all RNs? What is Needed for this to Occur? q Each Class, Interface, Package, Coponent CL1 INT_1 Must be Marked with Generality Level CL2 CL3 INT_2 INT_3 q Related Dependencies CL4 for Reuse are Defined CL5 Coponent X Package B q Parser that Synthesizes All of the Source Code Dependencies Is this Proble NP Hard? Coplete? June2001.OOReuse-13 Aside: Marking Coponents/Packages A Coponent/Package can Contain Coponents, Classes, and Interfaces q Reeber, Class CL1 can be Defined in Package B and Used in Coponent X q Or, Coponent X can be Used in Package B Coponents/Packages Must Run Through Reuse Metrics/Analysis to Eliinate Bad Dependencies Package not Marked Since Utilize Portions of the Package and Not Package Itself Coponents not Marked or Assued Most General Package B Coponent X June2001.OOReuse-14 7

8 Definition 2: Reusability Dependency A Reusability Dependency (RD) is a directed arrow between two Reusability Nodes, RN x and RN y, which satisfies the following: G xi G y j q for i = 1 n x < for j = 1 n y q RN x is Most General, RN y is Least General q Arrow fro RN y to Rn x Issues: q Should it be <= Rather than <? < is Preferable, Since it Allows for a Cleaner Ordering Aong Different RNs Eliinates Abiguity in Ordering June2001.OOReuse-15 Definition 2: Reusability Dependency Issues: q Should Interfaces be Excluded fro Ordering? If Interfaces Replicated, Sae Generality Level? If Interfaces Non-Replicated, Include in Ordering? Must Support Replicated Interfaces since Different Classes can Ipleent Sae Interface Differently q Proposal regarding Interfaces Interfaces are Not Marked When Class Ipleents Interface, the Marking of the Interface is the Sae as the Marking of Class Hence, Interface Can have Different Markings in Different Classes June2001.OOReuse-16 8

9 Definition 2: Reusability Dependency Issues: q Should the Dependencies Between Gx i and be Liited Such That G x1 Can Only be Dependent on G yn j? Yes, this Constrains the Constructive Requireents of the Reusability Graph (See Defn. 3) This Constraint with Assuptions of RN (Slide 5) May Assist in Autoated Deterination of RDs If Both RNs and RDs can be Autoated, fro Source Code, Create Reusability Graph (Defn. 3) q That is, Highest Level of Generality in RN y Can only Dependent on Lowest Level in RN x G y j June2001.OOReuse-17 Quantifying a Reusability Dependency Suppose RN x has Generality Levels of: G 0 G 1 G 2 Suppose RN y has Generality Levels of : G 3 G 4 Should Dependencies (Class, Method, Attr,, etc.) be Liited to fro G 3 in RN y to G 2 in RN x? Or, are Liits Unnecessary? CL1 INT_1 CL6 INT_1 CL2 CL3 INT_2 INT_3 CL4 Package B CL5 Coponent X CL7 CL8 Package B Package C INT_4 Coponent Y June2001.OOReuse-18 9

10 Definition 3: Reusability Graph A Reusability Graph (RG) is a Directed Graph with Reusability Nodes (Defn( Defn.. 1) as Vertices which are Connected by Reusability Dependencies (Defn.. 2) Issue: Are Cycles Allowed? June2001.OOReuse-19 Issues: Reusability Graph Cycles: q A Cycle Indicates Co-Dependency Aong Multiple Reusability Nodes - D, E, and H q Does this Iply All Must be Reused Together? Autoation q Assue that Reusability Nodes can be Autoatically (Algorithically) Deterined When Given Application s Source Code q Can Reusability Graph be Autoatically Derived? Is this NP Hard? Coplete? q Can we Use Genetic Algoriths for Proble? June2001.OOReuse-20 10

11 Definition 4: Reusability Layer A Reusability Layer (RL) is a Subset of the RG that Represents a Grouping of RNs to Satisfy a Particular Doain or Organization Requireent # $ % " &! ( ' June2001.OOReuse-21 Issue: What is Scope of a Layer? Since RN A Depends on RN D which Depends on RN E which Depends on RN H which Depends on RN B, Should all For the Layer? ) *+ ) * / ) * 0 ) * 1 ) *. ) *, ) * 2 ) * - ) * 4 ) * 3 June2001.OOReuse-22 11

12 Issues: Reusability Layer Cycles: q Recall a Cycle Means Co-Dependency Aong Multiple Reusability Nodes - D, E, and H q If All Must be Reused Together then Will this Ipact Layering - Must Layer Always Contain all Nodes in Cycle? Can Layer Contain only Part of Cycle? Autoation q Intuitively, Autoating Layers Doesn t Make Sense q Layer is Doain Specific and Dictated by Designer June2001.OOReuse-23 Future Work Issues for Layering and Reusability What are Liitations Across Layers? None??? How are Dependencies Tracked? q Defn. of RN and RD Can There be Different Layered Perspectives for Sae Design? Can All Layerings Coexist Together? Are Layerings Application Specific? q Yes to all Three - As shown on Previous Slide? What are Issues to Develop a Reuse Model for Levels and Layers? q Foral Model and Analysis q Inter-Layer vs. Intra-Layer Reuse q Inter-Level vs. Intra-Level Reuse Is there an EB Exaple to Deonstrate Ideas? June2001.OOReuse-24 12

13 Reusability and XML (DN) June 2001 IEEE Coputer(p.66): XML Leaves Unresolved How to Best Specify Intersyste Mappings q Analysts need Tools to record Intersyste Relationships and Mappings to Counity Standard DTDs or Scheas and to ake the Available for Reuse XML Abstractions Ipacting Reuse q SOAP, Extending XML Datatypes q Linking Resources in XML as applied to Reuse Extended Links Traversal Rules June2001.OOReuse-25 XML, OO, and Reuse Our Approach to Analyzing Reuse Exaines Counication Between OO Classes Siple Object Access Protocol (SOAP)( Messages use XML Docuents to Allow Internet Counication Between Applications q q Can SOAP Messages For the Basis of our Reuse-Focused Counication Analysis, or Does Another Aspect of XML Meet our Counication Analysis Interests? June2001.OOReuse-26 13

14 The Nature of XML Data Types Currently, An XML Coplex Type May be Extended Only Through Appending Will Eerging XSDL Support Seantic Inheritance? q Negative Overriding/Partial Inheritance Allows Designer to Inherit soe Properties, and Suppress Other Properties q Is Seantic Inheritance Critical to our Reuse Interests? June2001.OOReuse-27 Linking Resources in XML Creation/Description of Links Between Resources q Associate Metadata With a Link q Express Links that Reside in a Location Separate fro the Linked Resources q Runtie Traversal via Link Base Doc1 Virtual Relationship? (Ipact on Reuse?) Link Base DocA DocC DocB June2001.OOReuse-28 14

15 What is an XML Link? An XML Link is an Explicit Relationship Between Resources or Portions of Resources Made Explicit by an XLink Linking Eleent Asserting the Existence of a Link When a Link Associates a Set of Resources, Those Resources Are Said to Participate in the Link q Such Links are Able to Associate All Kinds of Resources, Not Just XML-Encoded Ones June2001.OOReuse-29 Extended Links Offer 3rd-Party Arcs and Links With Arbitrary Nu of Participating Resources. Can Include Eleents for: q Pointing to Reote Resources, q Containing Local Resources, q Specifying Arc Traversal Rules XLink Provides Seantics for Finding Linkbases q Docuents Containing Collections of Inbound and Third-party Links Are Called Link Databases, or Linkbases. June2001.OOReuse-30 15

16 Extended Links: Associate Resources and Provide Traversal Rules Local to Reote ResourceA Local to Reote ResourceB Extended Link Associates 3 Resources Provides 2 Traversal Rules Local to Reote ResourceC June2001.OOReuse-31 XLink Eleent Type The Type Attribute Indicates the Eleent Type: q q Dictates the XLink-Iposed Constraints That Such an Eleent Must Follow, and The Behavior of the XLink Application upon Encountering the Eleent Does such Behavior play a Role siilar to Method Invocation in ters of Evaluating Reuse? June2001.OOReuse-32 16

17 Future Work XML Reuse Considerations Do Arcs,Type, Seantic or Behavior Attributes provide Static Typing Info Usable in Aiding Reuse Evaluation of XML Designs? q q Spice (Extended Java-Script) has been used to Specify XML Docuent Behavior. Does Spice Play a Role in our Reuse Focus? How Does Dynaic Behavior of XML Linkbases Ipact XML Reuse? What Other XML Abstractions/Dependencies Exist that Ipact Reuse? June2001.OOReuse-33 Prototyping Progress in DRE and TCC (SD & JE) Suary of Prototyping Milestones Results and Status of CSE367 Project q Work by H. Lin on DRE q Work by X. Wang on TCC DRE Status q GUI Finalized q Siulator Copleted q Parser Integrated q Help Subsyste Copleted Togethersoft Control Center Status q Developed Extensive Set of Plug-ins q UML Design Level Reusability Definition June2001.OOReuse-34 17

18 Schedule (Spring 2001) Data Structures q JE & Tea q Septeber-October 2000 q January-February 2001 Java Parser q Tea q October-Noveber 2000 q February-May 2001 Metrics Schee & Calculator q JE q Noveber-Deceber 2000 q March 2001 GUI q Tea q October-Deceber 2000 q February-May 2001 June2001.OOReuse-35 Schedule (Spring 2001) Help Syste q Tea & JE q Deceber 2000 q March-April 2001 Siulation Tool q JE q February-May 2001 Together Control Center Application q Tea & JE q Septeber-Deceber 2000 q February-May 2001 Characterization File q JE q January 2001 q March 2001 June2001.OOReuse-36 18

19 Main Application Window June2001.OOReuse-37 Main Window Setting Generality June2001.OOReuse-38 19

20 Main Window Setting Relations June2001.OOReuse-39 Main Window Choosing Siulation Options June2001.OOReuse-40 20

21 Help Subsyste HTML-based Docuents Describe Tool & Theory June2001.OOReuse-41 Reuse in Togethersoft Control Center Integrates Visual Modeling via IDE q Ipleents UML/Supports Java and C++ q Source Code Editing q Model/Code Synchronization q Open API and Plugin Support (Written in Java) Single Integrated Design/Developent Environent with Reusability Assessent Leverage TCC to Support Reusability at Design Level q Incorporate G/S and Related at UML Level q Users can Execute Plug Ins for Each q Actual Properties for UML Classes Modified June2001.OOReuse-42 21

22 Reusability in Together CC June2001.OOReuse-43 Reusability in Together CC June2001.OOReuse-44 22

23 Reusability in Together CC June2001.OOReuse-45 Reusability in Together CC June2001.OOReuse-46 23

24 Future Work Prototyping, Together CC, and XML Version Releases q v2.00 Deceber 2000 (Unreleased) q v2.01 April 9, 2001 q v2.02 June 12, 2001 Future Work q Continue TCC Research q Ipleent Recoendations Usability Requests Feedback q q C++? DRE Research Displaying Coupling Counts Masters Thesis XML and Reuse? June2001.OOReuse-47 Reusability and Genetic Algoriths Objectives (RC & SD) Design and Ipleent a New DRE Parser Using Java Copiler Copiler Parser Generator Tool q Use of the Java Graar Specification Allows Easier Maintenance of DRE Parser q Iproveent of Current Parser: Isolation of Parser and Data Structures Use a Genetic Algorith to Find a Near Optial Class Generality Marking q Can Genetic Algorith be Utilized to Autoate Deterining Marking? q Class Marking That Miniizes a Function of the Coupling Counts q User Presented Actual Generality Level of Classes Based on Cross-References in Code June2001.OOReuse-48 24

25 Parser Generation Java Copiler Copiler Javacc is a Parser Generator Tool q Copiles a Graar Specification into Java q Augent Graar Specification with Seantic Actions - Java Code q Resulting Progra Recognizes Java Source Code and Generates Java Code That Creates DRE Data_Structures Objects Java Graar.jj JavaCC DRE Parser.java DRE Tool Runtie Java File.java DRE Parser DRE.data_structures Objects June2001.OOReuse-49 Genetic Algorith Stochastic Search Method Inspired in Natural Evolution Population-based Rando Variation/Selection Applied to Data Structures with Goal/Initialization Characteristics: q Genetic Operators (Selection, Crossover, Mutation) q Population of Chroosoes (Bit Strings) Encode Candidate Solutions in Search Space q Selection Based on the Fitness of Each Chroosoe Proble: Current GA with Liited Assuptions Tends to Yield all General Classes! June2001.OOReuse-50 25

26 Near Optial Class Generality Marking Coupling Counts Class Marking G CC1 G G CC3 S CC5 CC7 S S June2001.OOReuse-51 Genetic Algorith and Reuse Towards Guided Software Reusability Assessent Multi-Step Iterative Process: q Deterine Set of Assuptions Regarding Generality Levels of Generality that are Required Related Iplied by Dependencies or Set by User q Key Issue is to Define Constraints that Will Underlie the GA Fitness Function q Run the Genetic Algorith on Code for Fixed Population and Nuber of Generations q Evaluation of Results - Potential to Rerun with Changed Assuptions, Population, Generations q Converge Towards Reasonable Marking June2001.OOReuse-52 26

27 Future Work Genetic Algorith and RNs, RDs,, RG Current Independent Study - Rodrigo Caballero Investigating GA Work and Ph.D. Research q Exaining Related Research in Refactoring, Reuse Metrics, etc. q Conducting Experients using GA Algorith regarding Assuptions, Fitness Functions,etc. q Considering Role of RNs and RDs in Arriving at Realistic and Meaningful Marking q Towards Guided Reusability Assessent Allow SWE Input re. Assuptions, Generality, Related, etc. Apply GA Algoriths Based on SWE Input Provide Integrated Environent to Guide SWE June2001.OOReuse-53 Future Work - Reusability - Suary Short Ter (By 9/2001) q Prototype (DRE /TCC) - JE and XW q GA Work - RC q Initial Foral Reuse Model -SD q XML/Reuse - DN/JE q Journal Paper (All) Long Ter (By 5/2002) q Copleted Prototypes q Progress on GA Work q Foral Reuse Model q MS Thesis on XML and Reuse q Conference and 2nd Journal Articles Research - Through 2004 q Focus on Coprehensive Reuse Fraework q Guided Reusability Assessent/GA Analysis q Coponent Repository with Seantic Search Capabilities q Leverage Doain/Organization Specificity q UML, XML, and Java Coponents June2001.OOReuse-54 27