RandomCampaignGenerator

From The Battle for Wesnoth Wiki
Revision as of 16:37, 20 March 2008 by Kthakore (talk | contribs) (Development Model)

Me

irc: kthakore
gna: kthakore
forum: kthakore

My preferred email address is thakore.kartik@gmail.com.

I am a software engineering student at the University of Western Ontario. I would like to participate in the Google Summer of Code, because I have had this idea in my head ever since I first started playing Strategy Games and want to see it realized. I am just taking advance of GSoC to get my self to start working on this project.


Experience

Most of my work experience comprises of web application development with PHP/MySQL. Also I have experience working with C/C++. I have worked individually and within teams. Most of my web development projects were individual. I have experience working within ticket based system with SVN and Trac on a C/C++ code base where I created a version testing application. Moreover I spend some time hacking personal projects on my own. I am a self learner and learn technologies for requirement to finish my projects.

This is my first year in Google Summer of Code program.


Gaming Experience

I am an avid gamer and I play several genres of games. I play Wesnoth campaign wise when I have time. Otherwise, if I am busy I will play FPS games to unwind. I love games which have a well developed story in it. I believe that a good game plays as a good novel.

Overview

I propose to flesh out a procedural world generator (PWG) that consists of generated characters, stories, timelines, and maps. PWG first goal is to provide players with a world of characters and stories that they can use to improve their skills, get ideas for writing campaigns, and allow users to experience different units. Secondly PWG hopes, in the future, to provide players with a back drop world where then they can expand on to create new stories separate from the Wesnoth World.

Development Model

I believe the best development cycle with be iterative (spiral) model because it would ensure that the project will be well documented before design and development begin. Moreover it will reduce some of the time that would occur if the traditional waterfall model was used. Also I think a rigorous testing stage every iteration would be necessary to keep the project on track.

Basic Development Model:

- Design tests: this will ensure designs and code developed in this iteration are aimed and organized. The tests will also serve to refactor code by redesigning old tests.

- Develop to meet tests: This will keep development in scope and relevant

- Testing and update TODO lists