Cloud4All Matchmaking Workflows

From wiki.gpii
Revision as of 19:27, 2 April 2013 by Colinbdclark (talk | contribs)
Jump to: navigation, search

Generic, High-Level Matchmaker Workflow

  1. Fetch solutions from the Solutions Registry
  2. Filter the solutions based on:
    1. Platform
    2. Platform version
    3. Device
  3. Match
    1. Modify, synthesize, or infer user preferences
    2. Modify solutions list
    3. Run custom matchmaking strategy (using preferences set and solutions list)
    4. Produce and return the appropriate list of solutions and settings for the Lifecycle Manager


Statistic Matchmaker Workflow (today)

  1. Fetch solutions from the Solutions Registry
  2. Filter the solutions based on:
    1. Platform
    2. Platform version
    3. Device
  3. Match
    1. Infer settings for the current platform/device/context
    2. Don't modify the solutions list
    3. Delegate to the Flat Matchmaker for 3c & 3d


Statistic Matchmaker Workflow (future)

  1. Fetch solutions from the Solutions Registry
  2. Filter the solutions based on:
    1. Platform
    2. Platform version
    3. Device
  3. Match
    1. Infer settings for the current platform/device/context
    2. Implement custom workflow for 3b-d, resulting in the appropriate list of solutions and settings for the Lifecycle Manager


Rule-Based Matchmaker Workflow

  1. Fetch solutions from the Solutions Registry
  2. Filter the solutions based on:
    1. Platform
    2. Platform version
    3. Device
  3. Match
    1. Transform all preferences from application-specific to common terms (delegating to Transformer)
    2. Invoke the RB MMM's conflict-resolution rules, which may produce a modified set of user preferences and list of solutions
    3. Delegate to the Flat Matchmaker for 3c & 3d


Flat Matchmaker Workflow

  1. Fetch solutions from the Solutions Registry
  2. Filter the solutions based on:
    1. Platform
    2. Platform version
    3. Device
  3. Match
    1. Use the Ontology Server to convert common preferences into ontologized format
    2. Don't modify the solutions list
    3. Match the user's preferences to the solution's capabilities
    4. Transform the common preferences into application specific, and produce appropriate output