Difference between revisions of "Template:SimSYS REU2015"

From REU@MU
Jump to: navigation, search
Line 2: Line 2:
 
We are working on SimSYS, software intended to one day be able to generate educational games on any topic, at any level, and with any set of learning objectives.  The program, written in Java, loads information from an XML document (which can be specifications for anything from a senior level software engineering game or a 4th grade level geometry game) and uses it to create games with characters, music, and a good deal of interactivity and customization.  This summer, we are primarily working on SimSYS's preview tool, which allows educators (experts in the game's content but not in the game's code) to preview the game and make any adjustments they need before the game is generated.
 
We are working on SimSYS, software intended to one day be able to generate educational games on any topic, at any level, and with any set of learning objectives.  The program, written in Java, loads information from an XML document (which can be specifications for anything from a senior level software engineering game or a 4th grade level geometry game) and uses it to create games with characters, music, and a good deal of interactivity and customization.  This summer, we are primarily working on SimSYS's preview tool, which allows educators (experts in the game's content but not in the game's code) to preview the game and make any adjustments they need before the game is generated.
  
== Research Objectives, Weekly Log, Weekly Progress Report ==
+
== Week1 ==  
  
=== Week 1 ===
+
=== Goals and Milestones ===
 
+
==== Goals and Milestones ====
+
 
'''Goals'''
 
'''Goals'''
 
*Become familiar with SimSYS
 
*Become familiar with SimSYS
Line 16: Line 14:
 
*Exchanged communication information necessary with all members of the team
 
*Exchanged communication information necessary with all members of the team
  
==== Weekly Log ====
+
=== Weekly Log ===
  
 
(This was an abbreviated work week due to program orientation, etc.)  Our main task was evaluating the preview tool and attempting to refactor it to be compatible with the current code base, which had been updated.  The preview tool, which is meant to give the educators a look at the game (generated from the XML) before it goes through the game engine.  The June 2015 preview tool was in a state of disrepair and too disorganized to be able to build on it in the setup it had at the time.  We decided to go onto GitHub and pull the version of the preview tool from June 2014, the second commit that was put into Git.  This older version of the preview tool had considerably more functionality (the ability to resize and move elements, edit text, and place elements) and we felt that it provided a better starting point for refactoring the tool.
 
(This was an abbreviated work week due to program orientation, etc.)  Our main task was evaluating the preview tool and attempting to refactor it to be compatible with the current code base, which had been updated.  The preview tool, which is meant to give the educators a look at the game (generated from the XML) before it goes through the game engine.  The June 2015 preview tool was in a state of disrepair and too disorganized to be able to build on it in the setup it had at the time.  We decided to go onto GitHub and pull the version of the preview tool from June 2014, the second commit that was put into Git.  This older version of the preview tool had considerably more functionality (the ability to resize and move elements, edit text, and place elements) and we felt that it provided a better starting point for refactoring the tool.
  
==== Weekly Progress Report ====
+
=== Weekly Progress Report ===
 
*Tasks Completed
 
*Tasks Completed
 
**Pulled functioning June 2014 preview tool from GitHub
 
**Pulled functioning June 2014 preview tool from GitHub
Line 35: Line 33:
  
  
=== Week 2 ===
+
== Week 2 ==
  
==== Goals and Milestones ====
+
=== Goals and Milestones ===
 
'''Goals'''
 
'''Goals'''
 
*Become familiar with SimSYS
 
*Become familiar with SimSYS
Line 47: Line 45:
 
*Exchanged communication information necessary with all members of the team
 
*Exchanged communication information necessary with all members of the team
  
==== Weekly Log ====
+
=== Weekly Log ===
  
 
*'''Monday'''
 
*'''Monday'''
Line 74: Line 72:
 
**
 
**
  
==== Weekly Progress Report ====
+
=== Weekly Progress Report ===
  
 
*Tasks Completed
 
*Tasks Completed
Line 81: Line 79:
 
**
 
**
  
==== Weekly Progress Report ====
+
=== Weekly Progress Report ===
 
*Tasks Completed
 
*Tasks Completed
 
**
 
**

Revision as of 15:12, 12 June 2015

Summer Research Topic

We are working on SimSYS, software intended to one day be able to generate educational games on any topic, at any level, and with any set of learning objectives. The program, written in Java, loads information from an XML document (which can be specifications for anything from a senior level software engineering game or a 4th grade level geometry game) and uses it to create games with characters, music, and a good deal of interactivity and customization. This summer, we are primarily working on SimSYS's preview tool, which allows educators (experts in the game's content but not in the game's code) to preview the game and make any adjustments they need before the game is generated.

Week1

Goals and Milestones

Goals

  • Become familiar with SimSYS
  • Plan a refactor of the preview tool

Milestones

  • Read through relevant background material
  • Examined the code
  • Took ownership of the GitHub account
  • Exchanged communication information necessary with all members of the team

Weekly Log

(This was an abbreviated work week due to program orientation, etc.) Our main task was evaluating the preview tool and attempting to refactor it to be compatible with the current code base, which had been updated. The preview tool, which is meant to give the educators a look at the game (generated from the XML) before it goes through the game engine. The June 2015 preview tool was in a state of disrepair and too disorganized to be able to build on it in the setup it had at the time. We decided to go onto GitHub and pull the version of the preview tool from June 2014, the second commit that was put into Git. This older version of the preview tool had considerably more functionality (the ability to resize and move elements, edit text, and place elements) and we felt that it provided a better starting point for refactoring the tool.

Weekly Progress Report

  • Tasks Completed
    • Pulled functioning June 2014 preview tool from GitHub
    • Assessed of the current code base
    • Gained familiarity with SimSYS
    • Found multiple bugs, especially in the sandbox
  • Tasks for Next Week
    • Refactoring the preview tool to work with the current code base
    • Begin thinking about the usability study
  • Present Obstacles
    • The current code base is labyrinthine in some parts, and contains little useful documentation


Week 2

Goals and Milestones

Goals

  • Become familiar with SimSYS
  • Plan a refactor of the preview tool

Milestones

  • Read through relevant background material
  • Examined the code
  • Took ownership of the GitHub account
  • Exchanged communication information necessary with all members of the team

Weekly Log

  • Monday
  • Tuesday
  • Wednesday
  • Thursday
  • Friday

Weekly Progress Report

  • Tasks Completed

Weekly Progress Report

  • Tasks Completed
  • Tasks for Next Week
  • Present Obstacles