180 lines
6.2 KiB
Markdown
180 lines
6.2 KiB
Markdown
file:: [MLE23_paper_5_1691614582934_0.pdf](../assets/MLE23_paper_5_1691614582934_0.pdf)
|
||
file-path:: ../assets/MLE23_paper_5_1691614582934_0.pdf
|
||
|
||
- Gamification refers to the application of gaming concepts in non-playful contexts to encourage engagement with a product or service.
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64d40103-8628-4400-af63-34aca8e4e855
|
||
- hese systems are based on a set of rules defined by game designers, who specify the conditions that must be met to evolve the state of a game and the associated consequence
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64d40150-ffc7-48df-8129-7a32fb4023c4
|
||
- Gameful systems
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: purple
|
||
id:: 64d5e3f4-35e0-4643-8308-7b04ecac7bea
|
||
- certain limitations that can give rise to undesirable or unforeseen behaviors
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: yellow
|
||
id:: 64d5e497-5abc-4119-ab0b-024c2e696662
|
||
- entire rule lifecycle process
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64d5e4b7-ada6-4100-9485-f73f5f849c76
|
||
- asy-to-use
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: yellow
|
||
id:: 64d5e4c7-2804-4832-b1fe-a7825c3823d5
|
||
- simple
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: yellow
|
||
id:: 64d5e4de-f518-4dae-bef0-105f7abd9be9
|
||
- gamification can incentivize and motivate individuals to adopt more sustainable habits and lifestyles
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: green
|
||
id:: 64d5e501-3caa-44cf-bd44-fb5f206929f7
|
||
- enhance the sense of community and collective action towards sustainability
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: purple
|
||
id:: 64d5e50f-2ca1-4480-b590-17835cbf2d32
|
||
- Rules play a critical role in gamification as they define the boundaries, constraints, and objectives of the gam
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: purple
|
||
id:: 64d5e54f-f58f-4d50-aa73-eeb5633457d4
|
||
- ame designers can guide the players’ behavior, motivate them to take specific actions, and provide feedback on their performance
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: purple
|
||
id:: 64d5e559-a0e3-4206-8bba-0223c138d7c2
|
||
- gamification elements
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: blue
|
||
id:: 64d5e574-cf07-4a8c-bde5-f39810c05c5e
|
||
- Drools
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: purple
|
||
id:: 64d5e58c-c324-4f9a-b297-50b3947cc33d
|
||
- he Left Hand Side that describes the conditions to met for their execution and the Right Hand Side that corresponds to the actual consequences of the rules on the state of the game
|
||
ls-type:: annotation
|
||
hl-page:: 1
|
||
hl-color:: yellow
|
||
id:: 64d5e59c-ba5c-4d60-8833-e0314737bf63
|
||
- Applicant
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: yellow
|
||
id:: 64d5e5fb-fa4e-4ac0-bc5f-017bef20dbf9
|
||
- important gap between their domain’s knowledge and their coding skills
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: purple
|
||
id:: 64d5e633-b4cc-4792-8216-47b194184440
|
||
- Moreover, the rules definition is not followed by a well structured testing phase that allows a prior verification of their semantic correctness, this means that some rules don’t work as expected resulting in users dissatisfaction and complaints.
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: yellow
|
||
id:: 64d5e666-6da1-4fd2-a87b-2817552b270a
|
||
- Using a domain-specific language (DSL) to specify gamification rules can provide several advantages over using a more general-purpose languag
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: yellow
|
||
id:: 64d5e6c1-048e-4691-8e31-f39fb2859d10
|
||
- A welldesigned DSL can include built-in checks and constraints that ensure that the rules are consistent and coherent, and that they conform to best practices and industry standards
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: yellow
|
||
id:: 64d5e77a-2c20-46c1-abb4-3d68cbb41e74
|
||
- actual limitation
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: yellow
|
||
id:: 64d5e7b0-0c7d-4e09-9ccb-6401c2b3e8ed
|
||
- DSL4GaR
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: purple
|
||
id:: 64d5e7f4-7897-4a7d-88ed-e5556fe039ca
|
||
- a graph representing the evolution of the state of a gam
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: green
|
||
id:: 64d5e823-1f58-49e1-a3c8-0040998c470a
|
||
- erify the correctness of the defined rules
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: yellow
|
||
id:: 64d5e830-9c66-44df-85fb-050a973d9fdb
|
||
hl-stamp:: 1691740219127
|
||
- verify their possible interference
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: yellow
|
||
id:: 64d5e855-ebd7-47c2-aa54-3d0b5c82da59
|
||
- drawbacks
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: yellow
|
||
id:: 64d5e8b5-d50f-40d6-97a6-33b51b725dbf
|
||
- chained executions of the rules and their possible interference
|
||
ls-type:: annotation
|
||
hl-page:: 2
|
||
hl-color:: yellow
|
||
id:: 64d5e902-7d0b-4a66-87f9-7e12d1ebc223
|
||
- guiding the designers during the process to avoid error
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: green
|
||
id:: 64d5e951-47be-4451-be6c-310c80e1b7dd
|
||
- effective tool to permit rules simulation
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: green
|
||
id:: 64d5e957-b06b-4f65-8f67-eb90f8ff5dc5
|
||
- erify the actual changes
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: green
|
||
id:: 64d5e960-3b21-418f-af6f-7bb62f0c7bd0
|
||
- one or more rule are triggered, for example, by the same facts.
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: green
|
||
id:: 64d5e971-4a29-43ec-af1a-b7b8c7df659d
|
||
- asy-to-use APIs
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: green
|
||
id:: 64d5e9a5-e475-4f3e-aff0-3fec7edc16d9
|
||
- test the rules and verify their outcomes;
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: yellow
|
||
id:: 64d5ea49-20a0-4e4d-9004-247bdb0a38d3
|
||
hl-stamp:: 1691740808747
|
||
- easily
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: yellow
|
||
id:: 64d5ea50-f4bb-4c32-acf2-c2625f03f0e0
|
||
- During the simulation the designers can also define a list of assertions on the game’s state that are automatically verified during the process; if something unexpected happens, the graph reports the encountered errors and the relative unverified assertion
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: green
|
||
id:: 64d5eab5-3321-459c-83c3-3e929dd0e8d4
|
||
- Fig. 1: Game state transitions.
|
||
ls-type:: annotation
|
||
hl-page:: 3
|
||
hl-color:: yellow
|
||
id:: 64d5eaf2-76c3-4075-bbd0-97c589b96f80 |