recommender gui requirements for one portal technical meeting san gallen february 2009

16
Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Upload: marilynn-lee

Post on 02-Jan-2016

216 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Recommender GUIRequirements for ONE Portal

Technical Meeting San GallenFebruary 2009

Page 2: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Resume

• Rec-1: Partner Invitation• Rec-2: Join Negotiation• Rec-3: Create Offer• Rec-4: Offer Evaluation

Recommendations supported in the ONE Portal

Page 3: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

GUI

• Invocation Recommender Advice(where to place the ‘button’)

• Display Recommender Advice(how to visualize results)

For each of the 4 recommendation we defined both of them

Page 4: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

REC-1 - Invocation[Partner Invitation Recommender]

AdviceAdvice

Invoke the PARTNER INVITATION

recommender

Page 5: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Rec-1 - Display[Partner Invitation Recommender]

ONE- Recommendation Service

Advice for Partner Invitation

OK

Looking at your reputation statements and at the webof trust of the ONE community the following contactshave been selected as reliable partners to attend thenegotiation you are setting up:- <name> <surname>, <company>- <name> <surname>, <company>- <name> <surname>, <company>

Page 6: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Rec-1 - Display

ONE- Recommendation Service

Advice for Partner Invitation

OK

Since there are not enough Information on contacts and related trust, the system is not in the positionto infer reputation on potential partner to be invitedto the current negotiation.

[Partner Invitation Recommender]

Page 7: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Rec-2 - Invocation

ParticipateParticipateInfoInfo Create Sub NegotiationCreate Sub NegotiationAdviceAdvice

ParticipateParticipateInfoInfo Create Sub NegotiationCreate Sub NegotiationAdviceAdvice

ParticipateParticipateInfoInfo Create Sub NegotiationCreate Sub NegotiationAdviceAdvice

ParticipateParticipateInfoInfo Create Sub NegotiationCreate Sub NegotiationAdviceAdvice

Invoke the JOIN NEGOTIATION

recommender

[Join Negotiation Recommender]

Page 8: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Rec-2 - Display[Join Negotiation Recommender]

ONE- Recommendation Service

Advice for Joining Negotiation

OK

Looking at the most similar past negotiations using the same negotiation model, the average rate of successfulagreement is expected to be around <value> %.

You may have a look at a record of past negotiationclosely related to the current one. It occurred on <date> and was labeled <name>. More details here: <link>.

Page 9: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

ONE- Recommendation Service

Advice for Joining Negotiation

OK

Since there are not enough Information on past useOf the current negotiation model, the system is not in the position to infer the average rate of successfulagreement.

Rec-2 - Display[Join Negotiation Recommender]

Page 10: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Rec-3 - Invocation

AdviceAdvice

[Create Offer Recommender]

Invoke the CREATE OFFERrecommender

Page 11: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Rec-3 - Display[Create Offer Recommender]

ONE- Recommendation Service

Advice for Creating an Offer

OK

Looking at the most similar past negotiations using the same negotiation model, the final values of agreementfor the current open issues were the following:

You may have a look at a record of past negotiationclosely related to the current one. It occurred on <date> and was labeled <name>. More details here: <link>.

Item: <item-name>Issue <issue-name>: <issue-value> <issue-name>: <issue-value>Issue <issue-name>: <issue-value>

Item: <item-name>Issue <issue-name>: <issue-value>Issue <issue-name>: <issue-value> <issue-name>: <issue-value>

Page 12: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Rec-3 - Display[Create Offer Recommender]

ONE- Recommendation Service

Advice for Creating an Offer

OK

Since there are not enough Information on past useof the current negotiation model, the system is not in the position to infer the expected final values for the open issues.

Page 13: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Rec-4 - Invocation

AdviceAdvice

[Offer Evaluation Recommender]

Invoke the OFFER EVALUATION

recommender

Page 14: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Rec-4 - Display[Offer Evaluation Recommender]

ONE- Recommendation Service

Advice for Offer Evaluation

OK

Looking at the most similar past negotiations, using the same negotiation model, the average number of stepsto achieve a successful agreement was <value>.Up to now you carried on <value> steps.

You may have a look at a record of past negotiationclosely related to the current one. It occurred on <date> and was labeled <name>. More details here: <link>.

Page 15: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Rec-4 - Display[Offer Evaluation Recommender]

ONE- Recommendation Service

Advice for Offer Evaluation

OK

Since there are not enough Information on past useof the current negotiation model, the system is not in the position to infer the expected number of stepsrequired to achieve an agreement.

Page 16: Recommender GUI Requirements for ONE Portal Technical Meeting San Gallen February 2009

Inspect WindowONE- Recommendation Service

OK

The previous panel provided the opportunity to browse the past instances of negotiation. This panel implements the notion of ‘inspect’ of the description of a past negotiation as stored in the case base of the ONE platform.