Battleplan

Contains the overal strategy that is used to achieve the goals set in the concept document. Contains a high level plan of the client developement up to version 1.0, and what general features should be implemented for each milestone. Contains a more detailed plan for the next few iterations. Updated whenever required features are implemented.

A battleplan defines the high level strategy for reaching the goals set in the concept document. It defines what functionality should be in every version up to 1.0, and can suggest some goals to pursue after that. It also defines a bit more specific goals for the next few iterations, and should be updated whenever those goals are met, to decide when the version number of the client can be increased. The Battleplan is laid out as a series of milestones. Each milestone usually increases the minor version number, and generates some deliverable.

Version History

Draft 2001-11-16 nikal Initial battle plan.
Draft 2001-11-16 zzorn Merged in comments from the Battleplan Discussion.
Reviewed 2001-11-16 zzorn Merged in comments from the Battleplan Review.
Reviewed 2002-01-19 nikal & zzorn Revised the first few iterations so there were clearer goals to work for.

Introduction

General notes about the battleplan, what is required of it, how is it affected by the battleplans or implementation state of other products, how is needed effort and estimated number of dedicated develpers balanced, any special deadlines we want to have something running for (trade shows, etc), and the overal goals and strategy used when creating this battleplan.

Milestone 1

Implements version 0.1

Version 0.1 should be able to connect to STAGE or Cyphesis, and do Out Of Game chat. It should also support lists of people present, emotes, etc. Should have working packages for the most popular linux distributions, some installer or easily installable package for windows, and preferably also a working binary for Mac or some other platform.

Version 0.0.1

The purpose of the first iteration is to set down the initial framework and build process, to serve as a starting point for subsequent work.

Version 0.0.2

The main goal of the second iteration is to create an usable framework API and documentation for it, to make it easy for new developers to implement new components and services.

Version 0.0.3

The main goal for this iteration is to create several services and components, to find problems and improvement ideas for the framework API.

Version 0.0.4

The main goal for this iteration is stable framework classes.

Version 0.0.5

The main goal for 0.0.5 is to be able to connect to a server, and log in. Focus is on network, communication with servers, and atlas.

Version 0.0.6

The main goal for 0.0.6 is to be able to participate in Out Of Game chat on a STAGE and/or cyphesis server.

Version 0.0.7

The main goal for 0.0.7 is to have a stable and usable client that can be used to participate in STAGE meetings, and for Out Of Game chat. Focus is on stability, usability, portability, and good packages.

Version 0.1.0

When the client has been tested for some time, it is promoted to 0.1 and released officially on freshmeat. Downloadable packages should be available on victor and other relevant places.

Version 0.1 should be able to connect to STAGE or Cyphesis, and do Out Of Game chat. It should also support lists of people present, emotes, etc. Should have working packages for the most popular linux distributions, some installer or easily installable package for windows, and preferably also a working binary for Mac or some other platform.

Milestone 2

Implements version 0.2

Acorn

Milestone 3

Integrate Yup as a 3D GameView

Milestone 4

Basic Mason support

Milestone 5

Full Mason support, information object editing, scripting (Python and/or Lua?).

Version 1.0

Requirements for the 1.0 version

Future Versions

Some ideas for where to steer the developement after an 1.0 version.
  • New features.
  • Stability.
  • Performance.
  • Security.
  • Maintenance.

Conclusion

General comments about the battleplan, summary of central ideas.