1 / 8

Game Competition Management System Overview

Learn what each role needs to provide to define and run competitions. Understand the protocols for refutation and strengthening outcomes. Get insights into the functions of basic objects used by all. Dive into the roles of GameProvider, Scholar, and Administrator in competition management.

vashon
Download Presentation

Game Competition Management System Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. SCG Domain Specification Karl

  2. Overview • What needs to be provided • What GameProvider needs to provide to define a competition. • What each Scholar needs to provide to participate in competitions. • What Administrator needs to provide to run a competition. • Each role adds to the functionality of the basic objects.

  3. Objects used by all • Game • Scholar • Problem • Solution • Niche • Hypothesis • RefutationProtocol • StrengtheningProtocol • RefutationOutcome = Refutation | Support. • StrengtheningOutcome = Hypothesis | Refutation.

  4. GameProvider • cd for Problem (+ DemeterF defined interface) • Boolean semanticCheck() • Boolean conforms(Hypothesis) • cd for Solution • Boolean correct(Problem) • cd for Niche • cd for Hypothesis • Boolean legal(Niche) • Boolean refuted(RefutationProtocol) • = <kind> Kind • Kind : EA | AE. • cd for RefutationProtocol(Hypothesis) = • <provided> Problem • <solved> Solution • cd for StrengtheningProtocol(Hypothesis)

  5. Scholar • Problem • Solution solve() • Niche • Hypothesis propose() • Hypothesis • Problem provide() • oppose • RefutationOutcome refute() • StrengtheningOutcome strengthen()

  6. Administrator • cd for Game • register(Scholar) • start() • delivers • reports violations of game rules • computes reputations and produces scholar ranking • records history • invokes methods provided by GameProvider and Scholars.

  7. game.cd • Hypothesis = ProposedHypothesis | OpposedHypothesis. • OpposedHypothesis = RefutedHypothesis | StrengthenedHypothesis <opposer> ScholarID.

  8. Extra slides

More Related