Thrll programming language
Download
1 / 20

THRLL: a language for simulating a theme park to predict its ROI - PowerPoint PPT Presentation


  • 323 Views
  • Uploaded on

THRLL Programming Language. Aimee Sanchez Neetha Sebastion Kapil Verma Hemanth Murthy Michael Seaman. INTRODUCTRION . The theme park industry generated $11.5 billion in the United States in 2006 1 Theme parks represent large investments for their owners Revenue is difficult to predict.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'THRLL: a language for simulating a theme park to predict its ROI' - PamelaLan


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Thrll programming language l.jpg

THRLL Programming Language

Aimee Sanchez

Neetha Sebastion

Kapil Verma

Hemanth Murthy

Michael Seaman


Introductrion l.jpg
INTRODUCTRION

  • The theme park industry generated $11.5 billion in the United States in 20061

  • Theme parks represent large investments for their owners

  • Revenue is difficult to predict

1 – IAAPA, http://www.iaapa.org/pressroom/Amusement_Park_Industry_Statistics.asp


Thrll programming language3 l.jpg
THRLL Programming Language

  • Easy-to-use, declarative language

  • Simulates a theme park to predict revenue

  • Tool for estimating the returns on investments in the park


Thrll programming language4 l.jpg
THRLL Programming Language

  • Hub and Spoke Layout


Thrll programming language5 l.jpg
THRLL Programming Language

  • Hub and Spoke Layout

  • Industry Standard Terminology

  • Requires only moderate programming experience


Structure of thrll language l.jpg
Structure of THRLL Language

  • Let’s start our THRLL experience with a sample program.

  • Two sections – object definitions and user code.

  • Easy to use constructs like Park, Crowd, Land etc.



System architecture l.jpg
System Architecture

Park

Land

Crowd

Input Program

Intermediate

Code

Lexer / Parser

Restaurant

Attraction

Store

Intermediate

Code

GUI

GUI

Position File

Position File


Front end architecture l.jpg
Front-End Architecture

SampleThrill.txt

thrill_lexer.flex

Jflex

THRLL Parser

ThrillProgram.java

BYACC

Intermediate Code

thrill_grammar.y


System architecture10 l.jpg
System Architecture

Park

Land

Crowd

Input Program

Intermediate

Code

Lexer / Parser

Restaurant

Attraction

Store

Intermediate

Code

GUI

GUI

Position File

Position File



Our park has l.jpg
Our Park has:

  • .

Park

Park

Attraction

Restaurant

Store

Land


Built in functions l.jpg
Built-In Functions

  • Calculate Revenue

    • Parameters: Crowd, Duration

      result = CalculateRevenue: MyCrowdOne, days;

    • Sum of expenses and income

  • Simulate

    • Simulate: MyCrowdOne;

    • Creates position file

    • Graphical representation of guests interactions


The gui l.jpg
The GUI

Park

Land

Crowd

Input Program

Intermediate

Code

Lexer / Parser

Restaurant

Attraction

Store

Intermediate

Code

GUI

GUI

Position File

Position File




Development tools l.jpg
Development Tools

  • Java API

  • Eclipse

  • BYACC

  • JFLEX

  • Google Code

  • SVN

  • Lots and lots of email!


Testing l.jpg
Testing

  • Incremental Testing

    • Unit testing

    • Working of grammar

    • Working of backend

    • Integration testing

  • Provide efficient error checking and error reporting


Conclusions l.jpg
Conclusions

  • What we learned

    • Great experience working in a team

    • Development tools

    • Making a language is hard

  • What worked well

    • Weekly Meetings

    • Update on the status of progress


Conclusions20 l.jpg
Conclusions

  • Why THRLL

    • Ease of Use

    • Ease in calculation of net revenue

    • Optimal theme park experience for both investors and guests


ad