Difference between revisions of "Cloud4All Matchmaking Workflows"

From wiki.gpii
Jump to: navigation, search
(Created page with "== Generic, High-Level Matchmaker Workflow == <ol> <li>Fetch solutions from the Solutions Registry</li> <li>Filter the solutions based on: <ol style="list-style-type:...")
 
Line 23: Line 23:
 
== Statistic Matchmaker Workflow (today) ==
 
== Statistic Matchmaker Workflow (today) ==
  
1. Fetch solutions from the Solutions Registry 2. Filter the solutions based on:
+
<ol>
 +
  <li>Fetch solutions from the Solutions Registry</li>
 +
  <li>Filter the solutions based on:
 +
    <ol style="list-style-type: lower-alpha;">
 +
      <li>Platform</li>
 +
      <li>Platform version</li>
 +
      <li>Device</li>
 +
    </ol>
 +
  </li>
 +
  <li>Match
 +
    <ol style="list-style-type: lower-alpha;">
 +
      <li>Infer settings for the current platform/device/context</li>
 +
      <li>Don't modify the solutions list</li>
 +
      <li>Delegate to the Flat Matchmaker for 3c & 3d</li>
 +
    </ol>
 +
  </li>
 +
</ol>
  
    a. Platform
 
  b. Platform version
 
  c. Device
 
  
3. Match
+
== Statistic Matchmaker Workflow (future) ==
  
     a. Infer settings for the current platform/device/context
+
<ol>
  b. Don't modify the solutions list
+
  <li>Fetch solutions from the Solutions Registry</li>
  c. Delegate to the Flat Matchmaker for 3c & 3d
+
  <li>Filter the solutions based on:
 +
     <ol style="list-style-type: lower-alpha;">
 +
      <li>Platform</li>
 +
      <li>Platform version</li>
 +
      <li>Device</li>
 +
    </ol>
 +
  </li>
 +
  <li>Match
 +
    <ol style="list-style-type: lower-alpha;">
 +
      <li>Infer settings for the current platform/device/context</li>
 +
      <li>Implement custom workflow for 3b-d, resulting in the appropriate list of solutions and settings for the Lifecycle Manager</li>
 +
    </ol>
 +
  </li>
 +
</ol>
  
Statistic Matchmaker Workflow (future)
 
  
1. Fetch solutions from the Solutions Registry 2. Filter the solutions based on:
+
== Rule-Based Matchmaker Workflow ==
  
     a. Platform
+
<ol>
  b. Platform version
+
  <li>Fetch solutions from the Solutions Registry</li>
  c. Device
+
  <li>Filter the solutions based on:
 +
     <ol style="list-style-type: lower-alpha;">
 +
      <li>Platform</li>
 +
      <li>Platform version</li>
 +
      <li>Device</li>
 +
    </ol>
 +
  </li>
 +
  <li>Match
 +
    <ol style="list-style-type: lower-alpha;">
 +
      <li>Transform all preferences from application-specific to common terms (delegating to Transformer)</li>
 +
      <li>Invoke the RB MMM's conflict-resolution rules, which may produce a modified set of user preferences and list of solutions</li>
 +
      <li>Delegate to the Flat Matchmaker for 3c & 3d</li>
 +
    </ol>
 +
  </li>
 +
</ol>
  
3. Match
 
  
    a. Infer settings for the current platform/device/context
+
== Flat Matchmaker Workflow ==
  b. Implement custom workflow for 3b-d, resulting in the appropriate list of solutions and settings for the Lifecycle Manager
 
  
Rule-Based Matchmaker Workflow
+
<ol>
 
+
  <li>Fetch solutions from the Solutions Registry</li>
1. Fetch solutions from the Solutions Registry 2. Filter the solutions based on:
+
  <li>Filter the solutions based on:
 
+
    <ol style="list-style-type: lower-alpha;">
    a. Platform
+
      <li>Platform</li>
  b. Platform version
+
      <li>Platform version</li>
  c. Device
+
      <li>Device</li>
 
+
    </ol>
3. Match
+
  </li>
 
+
  <li>Match
     a. Transform all preferences from application-specific to common terms (delegating to Transformer)
+
     <ol style="list-style-type: lower-alpha;">
  b. Invoke the RB MMM's conflict-resolution rules, which may produce a modified set of user preferences and list of solutions
+
      <li>Use the Ontology Server to convert common preferences into ontologized format</li>
  c. Delegate to the Flat Matchmaker's workflow for 3c & 3d.
+
      <li>Don't modify the solutions list</li>
 
+
      <li>Match the user's preferences to the solution's capabilities</li>
Flat Matchmaker Workflow
+
      <li>Transform the common preferences into application specific, and produce appropriate output</li>
 
+
    </ol>
1. Fetch solutions from the Solutions Registry 2. Filter the solutions based on:
+
  </li>
 
+
</ol>
    a. Platform
 
  b. Platform version
 
  c. Device
 
 
 
3. Match
 
 
 
    a. Use Ontology Server to convert common preferences into ontologized format
 
  b. Don't modify the solutions list
 
  c. Match the user's preferences to the solution's capabilities blocks
 
  d. Transform the common preferences into application specific, and produce appropriate output
 

Revision as of 19:27, 2 April 2013

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