Experimentation Platform for Architectural Integration Rose Gamble University of Tusa System Overview Netscape Browser input architectural system characteristics output table of solutions and integration strategies Java server at Univ of Tulsa Site Intelligent agent system using KQML with embedded KBS Formal Models abstracting agent abstracting agent facilitator abstracting agent Architectural Integration Objectives To help in reusing software components by identifying problems that arise during integration of complex systems n To recommend solutions to resolve integration problems n To provide formal underpinnings for interoperability that improve reliability of recommended integration strategy n Purpose of Approach to Analysis Effective reuse of software components is largely needed in development n An architectural view of a system exposes critical properties of the system n Properties can be expressed formally for more extensive and reliable analysis n Overall Objectives Catalog and formally model system characteristics at the architectural level that contribute to interoperability problems n Recommend solutions and appropriate integration strategies to resolve problems n Implement an experimentation platform n Value Added Developers can obtain knowledge of potential module integration problems prior to implementation n Developers see what problems occur along with available solutions n Developers can choose to reuse components that have less interoperability problems n Advantages of Software Architecture Recognizes common paradigms in systems n Assists in the analysis and description of high level properties of a system n Aids in making principled choices among design alternatives n Helps in communicating new system designs n General Characteristics Characteristic Meaning Components The type of components involved in the style Naming of Components Naming issues related to components Identity of Components Knowledge of other components in the system Connectors The types of connectors involved Production of output The nature of how the output is produced Control Structure The structure that governs the execution Data Storage Method The details about how the data is stored Data Representation The format of data representation Integration Problems n Characteristic conflicts are used to recognize the integration problems Example Different restrictions the type of data that can reside on a pipe Characteristic System 1 System 2 Specialization in Pipes Bounded Typed Solutions and Strategies n Example Pipes can make different assumptions about the data transmitted through Wrapping one format to another Broker to mediate and handle the difference Characteristic System 1 System 2 Solution Specialization in Pipes Bounded Typed Strategy Handle Broker conflicts in the Wrapper nature of data in pipes Formal Underpinnings n Hierarchy of architectural style information contributes to characteristic descriptions characteristic conflicts n Formal models of integration strategies contribute to solution descriptions strategy recommendations Continued Research Some problems with Java interface and KQML n Stronger association between formal models and agent system is needed n Additional architectural styles including heterogenous styles need incorporation n