[csms-cvs] csms-core/src/documentation/content shortTermPlans.xml,NONE,1.1

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Update of /cvsroot/csms/csms-core/src/documentation/content
In directory sc8-pr-cvs1:/tmp/cvs-serv26031

Added Files:
	shortTermPlans.xml 
Log Message:
Moving documentation and adding support for Forrest 0.2

--- NEW FILE: shortTermPlans.xml ---
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "./dtd/document-v11.dtd">
<document>
  <header>
    <title>CSMS - Short Term Plans</title>

    <authors>
      <person id="rdg" name="Ross D. Gardler" email="ro...@sa..." />
    </authors>
  </header>

  <body>
    <section>
      <title>Introduction</title>

      <p>This document outlines the plans for the CSMS project in the
      forseeable future. There is a separate document detailing our 
      <link href="longTermPlans.html">Long Term Plans</link>

      .</p>
    </section>

    <section>
      <title>0.1 release</title>

      <dl>
        <dt>Additional Error Checking</dt>

        <dd>An extra step will be inserted into the events generation process
        in the Fantasy Sports Module, this will enable rules to be encoded to
        verify the generated scores, for example, total goals scored by a team
        should be equal to the number of goals identified in the result
        event.</dd>
      </dl>
    </section>

    <section>
      <title>0.2.x release</title>

      <dl>
        <dt>Move to a core/module architecture</dt>

        <dd>The core doesn't really exist yet. What we have is a fantasy
        sports module. This release will see the introduction of the core.
        Instead of the user selecting a game that they want to see the scores
        on the core will be aware of all the games due to have been played by
        that time and calculate them.</dd>
      </dl>
    </section>

    <section>
      <title>0.3.x release</title>

      <dl>
        <dt>Introduce team management</dt>

        <dd>Now that we have a core system and a sports module we can start
        thinking about teams and leagues. So in this release we will bring
        team management into play. We will support substitutions and transfers
        in this release.</dd>
      </dl>
    </section>

    <section>
      <title>0.4.x release</title>

      <dl>
        <dt>League Management Facilities</dt>

        <dd>Now that we have the concept of teams we can start to publish
        league placings.</dd>
      </dl>
    </section>

    <section>
      <title>0.5.x release</title>

      <dl>
        <dt>Move to a Cocoon Portal based system</dt>

        <dd>Move the user interface to a Cocoon web app. This will remove the
        need to install any software in order to use the system (although
        admittedly it will make it more difficult for people to install it for
        themselves should they want to hence the embedded jetty release after
        this one).</dd>

        <dt>Make available to Fanfoot.com players</dt>

        <dd>At this point the application will provide all major team
        management facilites. Testing at this point can be performed by the
        Fanfoot.com players.</dd>
      </dl>
    </section>

    <section>
      <title>0.6.x release</title>

      <dl>
        <dt>Allow unconfirmed/confirmed event status</dt>

        <dd>Events should have a status flag that enables them to be marked as
        official or unofficial. There also needs to be a flag to indicate when
        an event has been queried by someone. Initially all events are
        unofficial, however, they are used to calculate published (unofficial)
        results. On a given day and time, all events that have not been
        queried are converted to official. The queried flag is used to
        indicate that someone thinks the event may be an error. The league
        administrator is asked to verify these events before they become
        confirmed. This is to allow scores to be gathered from "unnoficial"
        sources which will sometimes be faster than the "official" sources
        whilst still</dd>

        <dt>Embed Jetty server</dt>

        <dd>By embedding the jetty server in one of the releases we will be
        able to build a distribution that will run in full client/server mode
        with only the need to install Java.</dd>
      </dl>
    </section>

    <section>
      <title>0.7.x release</title>

      <dl>
        <dt>Move to (Xindice?) database</dt>

        <dd>At present all data is stored in XML files, however they are being
        accesses through a URI. Therefore, we can no leverage Cocoons power to
        replace these files with a Xindice's XML database without the need to
        rewrite any code (theoretically at least)</dd>
      </dl>
    </section>

    <section>
      <title>0.8.x release</title>

      <dl>
        <dt>Refactoring</dt>

        <dd>No new features will be added but the design of the system will be
        improved.</dd>
      </dl>

      <p>This release will be the first one that sees an (almost) stable
      core/module structure and API. It is this releae that we will start to
      really push to other projects for collaboration. Once this core
      infrastructure is in place the possible additions to the system are
      immense and so opportunities for multiple developers start to
      emerge.</p>
    </section>

    <section>
      <title>And onwards...</title>

      <p>From here we will plan the featureset to include in the 1.0 release
      by revisiting both our 
      <link href="longTermPlans.html">long</link>

      and short term plans.</p>
    </section>
  </body>
</document>