1 / 11

CMPT371 – Team 1

Luminance. CMPT371 – Team 1. Project – Luminance. Puzzle game Basic mechanics: Guide a beam of light using a limited set of tools to certain goals avoiding obstacles along the way. Project – Luminance. Project – Luminance Current State. CMPT398 (CMPT306) project from 2008 XNA3.0 C#

doris
Download Presentation

CMPT371 – Team 1

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. Luminance CMPT371 – Team 1

  2. Project – Luminance • Puzzle game • Basic mechanics: • Guide a beam of light using a limited set of tools to certain goals avoiding obstacles along the way

  3. Project – Luminance

  4. Project – Luminance Current State • CMPT398 (CMPT306) project from 2008 • XNA3.0 • C# • Windows OS • It is currently in a fully playable state

  5. Project – Luminance Future Goals • Port to Android Phone • Rewrite C# to Java • XNA to OpenGL • Rewrite input interface for a touch device • New features: • Polish up the graphics • Add a high score server • More tools, obstaclesand levels

  6. Software Engineering Practices • Agile development process • One full group meeting every week (2-3 hours) • On demand micro meetings with the sub teams and the project lead • Weekly mini milestones • Test driven development • Need to stub out the project framework first

  7. Software Engineering – Continuous Integration • Build Master • Administers our build server • Perform daily builds • Run the full plethora of unit tests • Strict commit regiment • All developers will perform updates and commits in a timely fashion • Test Team • Develop a low fidelity smoke test to ensure basic functionality

  8. Software Engineering – Smoke Test • Automated build and test on every commit • What is our test process? • Clean and compile • Run the game • Automate navigation of the menus • Automate playing of the first level • How? • Ant build script with testing targets that will run directly on the PC • Testing hooks which can be compiled in to navigate the menu and play the first level

  9. Project Tools • Team City • Continuous Integration system • Google Code • Wiki • Issue Tracker • SVN Repo • Public homepage for the project • Eclipse + Android SDK • IDE • jUnit, jCoverage, Monkey, Robotium • Testing suite • Ant • Build scripts

  10. Project Plan – Milestones • Milestone 1 • Rewrite the game in an alpha state • Milestone 2 • Polish the game graphics • Milestone 3 • Outside the group user evaluation • Add new features • Milestone 4 • Add new levels • Milestone 5 • Code freeze • Prepare for release

  11. Questions? • Project Lead • Stephen Damm • Design Team • Zenja, Martina, Kai, Kum, Jonny, Stephen, Steven • Risk Officer • Chet • Build Master • Martina • Test Lead • Jeff • Test Team • Jia Jing, Kai, Amara • Triage • Jeff, Amara • Developers • Stephen, Zenja, Martina, Kai, Kum, Jonny, Steven, Chet

More Related