WP3 – Negotiation Framework

  • View
    25

  • Download
    5

Embed Size (px)

DESCRIPTION

WP3 – Negotiation Framework. Zohra Boudjemil & Claire Fahy. D3.1 – Languages, Models and Agreements Specifications (Task 3.1). Zohra Boudjemil email: zboudjemil@tssg.org. Content. ONE Objectives & Requirements Modelling Requirements Related Work The ONE MetaModelling Approach - PowerPoint PPT Presentation

Text of WP3 – Negotiation Framework

  • WP3 Negotiation FrameworkZohra Boudjemil & Claire Fahy

    ONE Technical Review, Brussels

  • D3.1 Languages, Models and Agreements Specifications(Task 3.1) Zohra Boudjemilemail: zboudjemil@tssg.org

    ONE Technical Review, Brussels

  • ContentONE Objectives & RequirementsModelling RequirementsRelated Work The ONE MetaModelling ApproachMetamodellingONE Modelling LayersONE Negotiation MetamodelInformation MetaModelProtocol MetaModelInstantiation Example English AuctionNegotiation MetaModel towards the ONE Framework Negotiation Model EditorTransformation

    ONE Technical Review, Brussels

  • ONE Objectives & RequirementsDefinition of a Negotiation MetaModel allowing the design of different types of business negotiation processes.Scope : E-business negotiations, Distributed environment, SMEs.Modelling Requirements based on business requirements defined by WP1.

    E-business NegotiationsSMEDistributed EnvironmentWP1 {D1.1,D1.2}Negotiation MetaModelBusiness Requirements

    ConceptsModelling Constraintsbuyerprocessrulesstrategyauction

    ONE Technical Review, Brussels

  • Related Work - (Meta)Modelling NegotiationDifferent negotiation (meta-)models developed to describe and manage the e-negotiation domainModelsAuction Models (Rolli and Eberhart, Wurman et al.)Focus on the auction mechanisms (rules, processes)Bargain Models (Chiu et al.)Focus on e-contract negotiation in a bargain situation, not open for competitive negotiations (auction)Generic Negotiation Protocol (Benyoucef and Rinderle)No support of the role conceptStandardsFIPA Negotiation Interaction Protocols (IP)Specify the interaction aspect without explicit definition of the negotiation rules.OMG Negotiation Facility (Bilateral Neg. Model, Multilateral Neg. Model)Specific models which do not support other types of negotiationDigital Product Modelling Language (DPML) doesnt support actions, conditions to allow the specification of negotiation rulesLimited roles (initiator, respondent)

    ONE Technical Review, Brussels

  • The ONE MetaModelling ApproachMetamodelling approach based on the MDA architectureA metamodel describes the rules and constraints of metatypes and meta-relationships.The meta-types and meta-relationships define semantics.

    ONE Technical Review, Brussels

  • Negotiation Metamodel ConceptsThe ONE MetaModel (Negotiation MetaModel) describes the constituencies of a negotiation model and their relationships by capturing their semantics from the e-business negotiation domain.is specified using UMLcovering two main aspectsInformation what?Protocol how?Core conceptsNegotiation defines what a negotiation is and how it is executed. They can be public or private.Actor represents a legal entity (person or SME) taking part in a negotiation process.

    ONE Technical Review, Brussels

  • Negotiation MetaModel Core concepts

    ONE Technical Review, Brussels

  • Information MetaModel

    Defines the what? of a negotiation, i.e. information

    Core conceptsItem represents the subject of the negotiation. It describes information about products/goods/services which are subject of the negotiation.Issue represents the matter involved parties dispute about.Criteria, specific type of rules representing link between information part and protocol part.

    ONE Technical Review, Brussels

  • Information MetaModel - Core Concepts

    ONE Technical Review, Brussels

  • Protocol MetaModel Defines the how? of negotiation representing the process.Allows for transparency of the negotiation process.Core conceptsNegotiationProtocol represents the abstraction of the negotiation process.NegotiationRole describes the types of actors.ProtocolBehaviour structures the dynamic aspect of the NegotiationProtocol specifying involvement of particular NegotiationRole during the negotiation. NegotiationRule governs the NegotiationProtocol.NegotiationMessage defines the communication between the involved parties.

    ONE Technical Review, Brussels

  • Protocol MetaModel - Core Concepts

    ONE Technical Review, Brussels

  • Protocol MetaModel - Core Concepts (cont.)Two NegotiationRoles:Owner - driving force: instantiates, configures, runs, terminates negotiation.Participant - involved in negotiation.ProtocolBehaviour describes the dynamic aspects of NegotiationRole in a stage model (statechart) based on three generic negotiation stages:Prenegotiation - all preceding activitiesAdmission - admission mechanisms of participant based on admission rules and negotiation visibility.Readiness - explicit status announcing readiness to begin negotiatingNegotiating - exchange of negotiation messages between parties following interaction and negotiation rules.Acceptance - agreement reached by accepted offer between two or more parties.

    ONE Technical Review, Brussels

  • Protocol MetaModel - Core Concepts (cont.)

    ONE Technical Review, Brussels

  • Protocol MetaModel - Core Concepts (cont.)NegotiationMessage specifies interaction part of NegotiationProtocol. RequestForProposal specifies subject and matter (item & issue), can include negotiation rules. Offer describes business proposal related to item and specifies values to issue.Response answers received message depending on its type.Reason explains response message.Agreement specifies the mutual arrangement between two or more parties, based on accepted offer.Notification specifies negotiation information other than the possible negotiation messages types.

    ONE Technical Review, Brussels

  • Protocol MetaModel - Core Concepts (cont.)

    ONE Technical Review, Brussels

  • Protocol MetaModel - Core Concepts (cont.)NegotiationRule

    Governs the negotiation protocol.

    Defined in correlation to information and protocol.

    Public to all parties

    Based on expressions that can be evaluated and executed.

    Two typesCriteria related to information part.ProtocolRule related to protocol part.

    ONE Technical Review, Brussels

  • Protocol MetaModel - Core Concepts (cont.)

    ONE Technical Review, Brussels

  • Instantiation Example - English Auction

    English Auction Properties vs. modelling conceptsOne seller => OwnerOne or more buyers => Participant

    Public negotiation => visibilityProduct/goods to sell => itemHighest bid designs the winner=> price as an issue

    Start price defined => criteriaStart time and end time => protocol rules

    ONE Technical Review, Brussels

  • Instantiation Example - English Auction Painting Information ModelItem: paintingIssue: priceCriteria (Defined in the Negotiation Model)StartPriceCriteria price must be higher than start priceCurrencyCriteria currency must be the same as defined currencyAuctionCriteria price must be higher than price of current accepted offer

    ONE Technical Review, Brussels

  • Instantiation Example - English Auction

    Negotiation Model

    2 protocol behavioursFor owner: OwnerProtoclBehaviourFor participant: ParticipantProtoclBehaviour

    3 protocol rulesAdmissionRuleNegotiatingStartTimeNegotiatingTimeOutRule

    ONE Technical Review, Brussels

  • ONE Technical Review, Brussels

  • Towards the ONE Framework

    Negotiation Model Editor Based on Ecore Negotiation MetaModel as DSLAutomatic Transformation of the UML Negotiation MetaModel (EA project) into the Ecore Negotiation MetaModel

    Runtime processesBased on the Engine Process Definition language (JPDL)Transform the protocol defined in Negotiation Models to JPDL processes

    ONE Technical Review, Brussels

  • Transformation MechanismsBased on Atlas Transformation ToolsSource MetaModel - Ecore Negotiation MMTarget MetaModel - Ecore JPDL MMTransformation rules conform to the transformation MMNegotiation MM(Source MM)(Engine) JPDL MetaModel(Target MM)TransformationRulesMaps fromMaps toNeg. ModelsNeg. ModelsNeg. ModelsEng. ModelsEng. ModelsEng. ModelsTransformation ToolsinputinputoutputOne Runtime EngineinputDKB RepositorystoredInstance ofInstance of

    ONE Technical Review, Brussels

  • ConclusionNegotiation MetaModel include the two aspects of negotiation in a separate way allowing to model different business context (Information) combined to different negotiation processes (Protocol).

    Addressing the ONE Modelling RequirementsDesign the different negotiation types based on the common negotiation concepts of the MetaModel

    Support distributed negotiations with the Role and ProtocolBehaviour concepts.

    Allowing the transparency of the negotiation rules defined as a public information in the negotiation model.

    Design of a formal negotiation process based on the negotiation protocol stage model (statechart).

    ONE Technical Review, Brussels

  • Tasks 3.2, 3.3 & 3.4 Claire Fahyemail: cfahy@tssg.org

    ONE Technical Review, Brussels

  • Task 3.2 Design ToolsTask Objectives:Development of an open source toolkit (or factory) that enables users to easily design/create their own negotiation.The models created in the Factory (layer M1) are model instances of the ONE metamodel (layer M2) .Users can drag and drop elements from the meta-model (Task 3.1).The models are persisted to the Distributed Knowledge Base which the factory will be connected to. In order to reuse models, the editor has to load and modify pre-existing models.The models are instantiated using the Set-Up procedure and then run on the ONE Engine.

    ONE Technical Review, Brussels

  • Task 3.2 Design ToolsProgress:The ONE factory is built as a rich client application based on the Eclipse framework.To increase re-usability of the models, they are divided into two types:Information Model