Presentation is loading. Please wait.

Presentation is loading. Please wait.

Configuration Ingegneria della Conoscenza e Sistemi Esperti Paolo Mereghetti.

Similar presentations


Presentation on theme: "Configuration Ingegneria della Conoscenza e Sistemi Esperti Paolo Mereghetti."— Presentation transcript:

1 Configuration Ingegneria della Conoscenza e Sistemi Esperti Paolo Mereghetti

2 Problem-Solving Types ClassificationConstruction Configuration Configuration Assignment Assignment Planning PlanningSimulation

3 Problem Solving Methods Heuristic construction Skeletal construction Skeletal construction Propose-revise strategy Propose-revise strategy Propose-exchange strategy Propose-exchange strategy Least-commitment strategy Least-commitment strategy Model based construction Case based construction

4 Business Service Components: a Knowledge Based Approach S. Bandini, S. Manzoni and P. Mereghetti Department of Computer Science, Systems and Communication University of Milano-Bicocca

5 Project Goal Development of a KB support system that helps Telcordia Tecnologies consultants in the activity of design and develop architectures for Business Services Namely Bellcore Morristown, NJ (USA)

6 Consultants activities formulate high-level business goals and a strategy to achieve these goals (business service design) identify suitable functionalities to provide a business service identify a suitable configuration of products to realize a technological solution

7 Component Definition I. A component is a self-contained software construct that has a defined use, has a run-time interface, can be autonomously deployed, and is built with foreknowledge of a specific component socket II. A component socket is software that provides a well- defined and well-known interface to a supporting infrastructure into which the component will fit III. A component is built for composition and collaboration with other components (Business Component Factory: A Comprehensive Overview of Component-Based Development for the Enterprise by Peter Herzum, Oliver Sims John Wiley & Sons, 2000 ISBN: )

8 Component Types BC - Business Component Realization of a defined functionality Realization of a defined functionality BC maps to definition I BC maps to definition I MSC - Middleware Service Component Realization of a defined middleware service Realization of a defined middleware service MSCs define the supporting infrastructure of BCs MSCs define the supporting infrastructure of BCs MSC maps to definition II MSC maps to definition II

9 BCs support the relationships: collaboration collaboration Requires Requires MSCs support the relationships: compatibility compatibility Supplies Supplies MSCs comply standards Relationships allow to build components for composition and collaboration with other components (maps to definition III) BC collaboration requires Relationships compatibility supplies standard MSC

10 BC collaboration relationship collaboration relationship is defined between BCs only A BC may support many collaboration relationships collaboration relationship can be classified in: By dependency (well-known relationship) By dependency (well-known relationship) By design (deduced by configuration requirements) By design (deduced by configuration requirements) collaboration by dependency collaboration by design

11 requires relationship is defined between BCs and MSCs A BC may have many requires relationships requires relationship can only be: By dependency (well-known relationship) By dependency (well-known relationship) BC BC requires relation Vignette catalog manager Vignette transaction manager

12 Middleware Service Component compatibility relationship is defined between MSCs only A MSC may have many compatibility relationships compatibility relation can be classified in: By dependency (well-known relationship) By dependency (well-known relationship) By design (deduced by configuration requirements) By design (deduced by configuration requirements) compatibility by dependency compatibility by design

13 MSC Middleware Service Component supplies relation is defined between MSCs and BCs A MSC may have many supplies relations supplies relation can only be: By dependency (well-known relation) By dependency (well-known relation) Vignette catalog manager Vignette transaction manager

14 Adapter Is a MSC without supplies relationships It helps two different MSCs to be compatible MSC Adapter MSC

15 Legacy Systems A Software Bundle composed by a set of BCs and MSCs No information on a single BC or MSC (internal structure) MSC BC MSC BC Software Bundle

16 Legacy Systems Possibility to buy or build Adapters MSC2 BC1BC2 MSC1 BC3 Software Bundle Adapter Using Adapters MSC3

17 Legacy Systems Possibility to know the standards that comply to MSC2 BC1BC2 MSC1 BC3 Software Bundle “Exporting” Standards MSC3

18 The Supporting Tool Based on “Generate and Test” approach with an Adapter module A solution hypothesis is generated The solution is tested If the Test phase failed, the tool is able to adapt the solution

19 The Supporting Tool (logical steps) Input acquisition (set of BCs, functionalities and collaboration by design relations) Input verification and completion Using the component selection criteria Using the component selection criteria Using knowledge on collaboration by dependency Using knowledge on collaboration by dependency Identification of the set of MSCs that satisfies all the services required by BCs

20 The Supporting Tool (logical steps) Relationships projection Each compatibility by design is tested MSC BC MSC

21 MSCs Compatibility Two MSCs are considered compatible if: A compatibility by dependency is defined A compatibility by dependency is defined Exist an MSC with compatibility by dependency relationship with them Exist an MSC with compatibility by dependency relationship with them There is at least one common standard they comply to There is at least one common standard they comply to

22 MSCs Compatibility

23 Solution example Wireless Gateway Voice Gateway Cocoon JMS Router User Interface Delivery System Prof.-Cont. Manag. Credit-Card System E-ShopCall Center Delivery System Legacy System EJB Container JMS-XML RMI Compatibility by dependency Compatibility by standards RMI Tomcat HTTP

24 Component selection criteria A tree-structured hierarchy of quality features (Quality Tree) has been defined A quality value (i.e. in [1..10]) and a weight are assigned to each node Different tree branches represent different quality features (i.e. Technical quality features, Marketing quality features, etc.) Each tree level correspond to a specific level of granularity for that feature

25 Quality Tree quality technical marketing management friendliness product engineering market position investment risk cost configurationoperation

26 Handling the Quality Tree The Tool can handle Quality Trees whose values are not completely assigned The Tool can handle Quality Trees whose values are not completely assigned Some nodes have no quality value assigned to them Some nodes have no quality value assigned to them The Tool uses Upwards and Downwards Completion functions to complete the tree The Tool uses Upwards and Downwards Completion functions to complete the tree

27 Product Tree completion Node values calculated with the upwards function Node values calculated with the downwards function Node values defined by the Product Steward

28 Product and Query Quality Tree Product Quality Tree Associated to a product (component) Associated to a product (component) Weights are defined and configured tool-wide, but not for each product Weights are defined and configured tool-wide, but not for each product Query Quality Tree Isomorphic to the Product Quality Tree Isomorphic to the Product Quality Tree A relational operator is defined for each node and is used in the quality indicators computation A relational operator is defined for each node and is used in the quality indicators computation

29 The Query Quality Features List Users are presented with simple, high-level questions in order to assess: Users are presented with simple, high-level questions in order to assess: Their propension to risk Their propension to risk Their technology and SW budget Their technology and SW budget Their expected levels of traffic (customer targets) Their expected levels of traffic (customer targets) Using this simple data, the Tool infers values for some of the remaining features that are collected in a list (Quality Features List): Using this simple data, the Tool infers values for some of the remaining features that are collected in a list (Quality Features List): Investment Risk Investment Risk Cost Cost Scalability Scalability

30 Using the Quality Features List A new Query Tree is constructed using the values in the Query Quality Features List A new Query Tree is constructed using the values in the Query Quality Features List Quality Features ListQuery Quality Tree created Nodes without an associated value Input values

31 Quality indicators It is now is possible to compute the Quality Indicators values It is now is possible to compute the Quality Indicators values Query Quality TreeProduct Quality Tree Only thevalues are used to compute the indexes

32 Indicators Distance Quality Indicator Constraint Violation Indicator

33 Bibliogrphy Rolston, D.W., Principles of Artificial Intelligence and Expert systems Development, McGraw Hill International Edition, Rolston D.W., Sistemi esperti: teoria e sviluppo-, MacGraw Hill Libri Italia, Milano, Guida, G., G. Berini, Ingegneria della Conoscenza: Strumenti per Innovare e per Competere, E.G.E.A., Forgy, C.: On the efficient implementation of production systems, Ph.D. Thesis, Carnagy Mellon University, Forgy, C.: Rete: A Fast Algorithm for the Many Pattern Many Object Pattern Match Problem, Artificial Inelligence, 19(1) 1982.


Download ppt "Configuration Ingegneria della Conoscenza e Sistemi Esperti Paolo Mereghetti."

Similar presentations


Ads by Google